| |
I'm a little surprised that the Spybot doesn't need to see the packet header
byte - the byte containing the range/orientation bits preceding the 0x8n Ping
byte. The header is deliberately generated with the stop bit cleared to force a
framing error. I thought it was a convenient (or necessary??) method for the
Spybot to detect a start of packet.
Does your IR monitoring see this byte - or does it get gobbled up due to the
framing error?
--Jay
|
|
Message has 2 Replies:
Message is in Reply To:
 | | Re: RCX to Spy messages thru IR communications route
|
| (...) Yes, that is what another person told me via email yesterday. So a ping simulation function for an RCX running the RCX2 firmware could be: // nLinkID = 0-7, where 0 = no link, 7 = pc link, 1-6 = controller link // nMyID = 8-255 (minBotID = 8, (...) (20 years ago, 25-Mar-04, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
10 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
|
|
|
|
