| |
In lugnet.robotics.rcx.legos, Andre Wiesner wrote:
> Hi.
>
> > AFAIK there is no way to receive Lego-Messages, except by editing lnp.c and adding
> > that by hand. The only Lego-Messages that brickos knows of, are those from the
> > remote control and the "send message" opcode (0xf7). It may be worthwhile to add
> > general LEGO-Message support to lnp.c together with an lnp_lego_handler...
>
> That would be a fun state machine to set up... ;-)
So, I finally sat down and figured out how the lnp state machine works in
BrickOS. Turns out it was pretty easy to add in a new set of states so it can
process a standard OpCode & store the parameters in variables.
At this point, I'm not verifying the message with the checksum, and I'm not sure
how that will work for messages with a different number of parameters. But I've
hacked up the kernal enough to do what I want.
Thanks
Steve
|
|
Message is in Reply To:
 | | Re: RCX to RCX LNP
|
| Hi. (...) That would be a fun state machine to set up... ;-) (...) It only does so when it receives opcodes between 0xf0 - 0xf7 or a standard firmware message (0x55). Of the first eight, only 0xf0 and 0xf1 currently require further action, with 0xf0 (...) (19 years ago, 17-Aug-05, to lugnet.robotics.rcx.legos)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
