Subject:
|
Re: Duplex Comms with RCX
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 27 Apr 2000 22:22:36 GMT
|
Original-From:
|
Pink Tail <pinkmice@borg.comNOSPAM>
|
Viewed:
|
651 times
|
| |
|
|
I applaud the thoroughness of your proposal. There's clearly
a lot of thought gone into the idea. I have two questions;
1.
Is the three second timeout reasonably accurate or is it, as I
suspect, just some inaccurate RC time constant in the tower?
In which case, you would have to choose a value like 2.5 secs
to guarantee to stay within it.
2.
Assuming that RCXs with something to transmit are ready and
waiting, why not assign one of the PCs as the master and have
it poll each RCX "address". A smallish population of RCXs wouldn't
take too long to cycle through. The tower would be busy almost
all the time and packet size would not enter into the equation, except
that one RCX could easily hog the "medium" everytime it got its
turn. I assume here, obviously, that because the RCXs are "ready"
a really short no-response timeout could be used for RCXs with
nothing to transmit.
JB
|
|
Message has 1 Reply:
 | | Re: Duplex Comms with RCX
|
| (...) Thanks. Early in my carreer, I had the benefit of actually implementing a simple-yet-robust serial communication protocol, so I've had a lot of exposure to the issues involved here. (...) Three seconds is an approximation. The actual time (...) (25 years ago, 27-Apr-00, to lugnet.robotics)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
