Subject:
|
LEGO remote and LNP (legOS 0.2.4)
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Mon, 23 Oct 2000 11:04:28 GMT
|
Viewed:
|
1428 times
|
| |
|
|
Hi
I've just got the LEGO remote control (from the Ultimate Accessory Kit), and
of cause it dosen't work with legos. So I tried to see, if anyone had done
some kind of driver to it, but I couldn't find any, and began hacking in the
legOS kernel (kernel/lnp.c), to see, if I could alter the LNP driver to accept
messages from the remote. It nearly works, but strangly enough, a couble of
bytes is missing. I receive the following bytes for "message 1": (out of my
memory)
55 ff 00 2d d2 00 ff 2d d2
55 ff 00 2d d2 00 ff 2d d2
55 ff 00 2d d2 00 ff 2d d2
55 ff 00 2d d2 00 ff 00 ff 2d d2
But if I use a program on my Linuxbox, which receives the signal from the ir-
tower, I get:
55 ff 00 2d d2 00 ff 01 fe 2d d2
55 ff 00 2d d2 00 ff 01 fe 2d d2
55 ff 00 2d d2 00 ff 01 fe 2d d2
55 ff 00 2d d2 00 ff 00 ff 2d d2
So the question is: Why are the 01 fe bytes missing???
My hack just sits in the function that waits for a LNP header, and
if it dont, my program takes the byte instead (and sets the state machine
to wait for more bytes, my hack receives)
Help anyone?
(sorry if the description isen't too good, but I don't have the program in
front of me)
Rasmus Kjelsen
|
|
Message has 1 Reply:
 | | Re: LEGO remote and LNP (legOS 0.2.4)
|
| (...) The remote control sends with parity odd, but the rcx is programmed to no parity. If the parity bit has the same value as a undriven line (I think it is logical 1), the byte is received, but otherwise the byte gets thrown away by the serial (...) (24 years ago, 23-Oct-00, to lugnet.robotics.rcx.legos)
|
11 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
