 | | Re: Transmitting a message from the RCX to the PC
|
|
I'm posting this on behalf of John Donaldson who is having a problem with his emails bouncing, so this is his text verbatim. Why can't a mode where a two byte sequence is sent. The first byte is the bot address and the second byte is the data code. (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) I am not sure if there is a way to disable the communications on the RCX when using the standard firmware. You could try putting an aluminum foil blinder around RCX No 2's IR transceiver, but I've found IR notoriously difficult to block since (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) I'm not the originator of this thread but I am interested in the same problem. I'm intending to use MS visual c++ V4 spirt.ocx RIS 2.0 firmware and NQC (...) I do want to use two RCX's though. My plan is to have RCX No 2 send data to RCX No 1. (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | Re: Transmitting a message from the RCX to the PC
|
|
(...) The one-byte messages supported by the RCX are not generally designed to go from the RCX to the PC. They are intended to go from the PC to the RCX, or from one RCX to another. One reason for this is that the original RS-232 IR tower would not (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx)
|
| |
| | BricxCC release 3.3.7.5
|
|
Version 3.3.7.5 fixes two bugs with the copy to clipboard function on the Analysis graph. It fixes the Clear Memory function so that it now clears all five program slots (it used to leave slot 1 untouched). It fixes form and component size issues (...) (22 years ago, 22-May-03, to lugnet.robotics.rcx.nqc, lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
