| | Re: Duplex Comms with RCX
|
|
(...) Dave had mentioned making a listen mode w/ keep-alive in a future version of nqc. But I don't think he's gotten around to that yet. (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
|
| | Re: Duplex Comms with RCX
|
|
(...) Yes. Note that it is only half-duplex. You probably expected that. (...) The biggest issue you might run into is the fact that the IR tower used by the PC times out if it doesn't transmit anything for a few seconds. Unless you have constant (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
|
| | Re: Duplex Comms with RCX
|
|
"James Hammond" <jsh@it-innovation.soton.ac.uk> wrote in message news:3906A2E6.6A40E0...n.ac.uk... (...) Yes it can. There is a standard RCX opcode for sending single byte messages, and you can always use multiple of these commands for more complex (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
|
| | Re: Duplex Comms with RCX
|
|
It appears Roblab 2.0 would also be an alternative for your project. Robolab has two different direct modes to control the RCX, one of which is using a remote connection like the Internet. Depending on your direct control requirements, you may want (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
|
| | RCX2 API
|
|
I've put together a NQC API file that allows you to use some of the RCX2 features. I don't no whether anyone else has already done this but here is mine. This is unofficial so is unsupported. All question should go to the group, not Dave or myself. (...) (25 years ago, 26-Apr-00, to lugnet.robotics.rcx.nqc)
|