Subject:
|
QuiteC IR interfacing to lego firmware IR
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Tue, 3 Feb 2004 19:04:43 GMT
|
Viewed:
|
3010 times
|
| |
|
|
Hi,
QuiteC's IR facilities are rudimentary. They send and receive single bytes.
I need to be able to make it send and receive lego IR protocol messages for
opcode 0xf7.
I'm not having much luck.
When I send a 0xf7 opcode with a message of 0x03 (using brickOS as a known
good thing), it is supposed to send:
0x55,0xff,0x00,0xf7,0x08,0x03,0xfc,0xfa,0x05
I assume that brickOS is behaving correctly.
On the quiteC side I receive this:
0x5d,0xff,0x00,0x03,0xfc,0xfa,0x05
Two mysteries:
1. How did the 0x55 header byte get garbled to 0x5d?
2. Where in the heck did the opcode bytes (0xf7,0x08) go?
Any help with QuiteC IR would be greatly appreciated.
Kevin
|
|
Message has 2 Replies:
 | | RE: QuiteC IR interfacing to lego firmware IR
|
| (...) Not knowing EXACTLY what is going on with QuiteC, I can only offer some suggestions.... The 0x55 to 0x5D might just be IR warmup goofiness. As far as I know, the RCX really only looks for the FF 00 Not sure what happened to the F7 and 08, but (...) (21 years ago, 3-Feb-04, to lugnet.robotics.rcx)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
