|
|
 | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) inside the RCX *directly*, not running programs layered on top of the standard firmware. And if you want to use NQC, you have to work within the limits of the standard firmware (OK, ignoring Dick Swan's firmware, which I've still not been able (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) Hi Brian, Thanks for your response. (...) I'm not sure if I get this, because of C code examples I've seen, which I'll discuss again below. (...) I've tried this already, and as you say, it works, but the sensitivity goes waay down. For a (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | Re: RCX to RCX NQC
|
| On Mon, September 12, 2005 8:03 pm, Brian Davis wrote: ... (...) ... Somewhere in there, it tells you the RCX will not accept the same command twice in a row. Each command has two op codes that are 8 digits apart. So (I think) for SetWatch you (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
| | | | | Re: direct manipulation of bits in RCX registers using NQC
|
| (...) Perhaps - but the standard firmware implements a "virtual machine", and so you don't generally have access to physical registers. But... (...) You can configure the input port that the light sensor is connected to as a "passive" sensor (so (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
| | | | | RCX to RCX NQC
|
| In a semi-followup to Steve's earlier "remote battery tester"... While the standard firmware provides almost no way to get bytes into the RCX (other than "Message()", one byte at a time), it can certainly export them ("SendSerial"). And it occured (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
|
