Subject:
|
Reliable PC<->RCX Comms
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sat, 1 May 1999 21:38:37 GMT
|
Original-From:
|
Laurentino Martins <lau@mail.telepac[AvoidSpam].pt>
|
Viewed:
|
794 times
|
| |
|
|
I'm developing a Spirit.ocx (VC++) program that cooperates with a NQC program to accomplish some tasks, but I'm having some problems creating a reliable method for maintaining contact with the RCX.
I wonder if any of you have found good ways for detecting the following situations, and how to successfully recover from them:
After the PC program successfully initializes and uses the RCX,
(1) Somebody turns off the unit and the PC "crashes" waiting for a unit that will never respond.
(2) The program the PC needs to work with in the RCX, was never downloaded.
(3) Somebody un-pressed the Run button of the unit and stopped the program while the PC program is waiting for some results from that program.
(4) For some reason the RCX looses most of the contact with the PC (batteries, out of range, etc) and the PC doesn't seem to understand that.
(5) After these situations occur, reestablish the communications (after some user intervention) and proceed.
I would prefer some *pure* Spirit.ocx solutions that can be made to work in any NQC program and without modifying them.
How do LEGO make their programs fool proof using ony the Spirit.ocx?
Anyone wants to share it's expertise on this?
Laurentino Martins
[mailto:lau@mail.telepac.pt]
[http://www.terravista.pt/Enseada/2808/]
--
Did you check the web site first?: http://www.crynwr.com/lego-robotics
|
|
Message has 1 Reply:
 | | Re: Reliable PC<->RCX Comms
|
| At 22:38 01/05/99 Saturday , you wrote: [...] (...) [...] Oh yeah, and there's another one: (6) While both programs running, someone turned the unit off and back on again, and pressed the Run button once again. I think the communications should not (...) (25 years ago, 2-May-99, to lugnet.robotics)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
