|
|
 | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) Correct. A NQC command (say, "Wait(10);") is converted to one or more "bytecodes" (in this case, one bytecode, namely a string of 4 bytes (0x43 0x02 0x0a 0x00), the first of which is a command (0x43) while the following three are information (...) (20 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| Hey, Thanks for all the helpful responses, everyone. Brian: (...) I guess that "firmware" must be the code that tells RCX how to interpret user instructions (NQC, C, IC, opcodes, or whatever), and convert them to binary machine-specific code. Right? (...) (20 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: RCX to RCX NQC
|
| (...) And that explains why I was having so much trouble with my custom Tcl based uploader in high speed mode. I fixed it a while ago by adding a slight bit of extra time between messages, but never got to the root of the problem. Thanks Dick! (...) (20 years ago, 15-Sep-05, to lugnet.robotics.rcx)
| | | | | RCX to RCX NQC
|
| One last email on this topic. There's new opcodes in the Swan firmware to support many data bytes in a single "mailbox" message. The standard firmware supports "mailbox" messages with a single byte parm. I found this very restrictive in building RCX (...) (20 years ago, 15-Sep-05, to lugnet.robotics.rcx)
| | | | | RE: RCX to RCX NQC
|
| There's another little problem that you may need to program around. There's a bug in the ROM firmware that could end up requiring a 30-millisecond delay between when a RCX sends out a message and when you should start sending the first character of (...) (20 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
|
