|
|
 | | RE: RCX to RCX NQC
|
| The message "toggle" bit was a good concept that has very limited value in practical use. I guess the intent was to prevent unexpected behavior when a PC program attempts retransmission after a message failure. Suppose the failure condition was that (...) (19 years ago, 15-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: RCX to RCX NQC
|
| (...) I'm pretty sure, both the remote, and the send message commands only have one op-code, and are done differently from the rest. Steve (19 years ago, 14-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: RCX to RCX NQC
|
| (...) Ahh, now I understand why it is called a "toggle bit" - I somehow misinterpreted this to mean a new command had the toggle bit set (to 1), and if the sending unit doesn't recieve a reply it should re-transmit the command with the toggle bit (...) (19 years ago, 14-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: 1.0 brick not responding
|
| (...) Powerbook 5300 with MacNQC: After about 4 seconds "No response or bad response from RCX. Make sure the RCX's receiver is facing the IR device and the RCX is turned on." Palm 130 with PBrick Demo: play sound 1, play sound 2, and play sound 3 (...) (19 years ago, 14-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: 1.0 brick not responding
|
| (...) Generally, that means the IR tower is working. It's possible the tower has become broken, while it sat in a closet, but that's not very likely. So, knowing things worked before, you may be forgetting something. Make sure the memory is cleared. (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
|
