Subject:
|
Re: RCX to RCX NQC
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Tue, 13 Sep 2005 03:56:52 GMT
|
Viewed:
|
3956 times
|
| |
|
|
On Mon, September 12, 2005 8:03 pm, Brian Davis wrote:
...
> But if I try something different, like PlaySystemSound (0x51) or SetWatch
> (0x22), it seems again to work only the first time the slave "sees" it, and the
> slave can only be reset to a receptive state by accepting a command from the
> "real" LEGO remote (even turning the slave off & on doesn't "reset" it) or using
> the "remote 0" command.
> First actual question: is this the case, or am I missing something about
> bytecodes in immediate mode?
...
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 should be able to use command 0x22 and/or 0x2a
That's exactly what I had to do for my battery tester.
Steve
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | 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 (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
8 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
