|
|
 | | Re: RCX to Spy messages thru IR communications route
|
| (...) Boy, this RCX to Spy IR comm thing is sure going the right way! The SPYBOTICS are a little known and hidden LEGO gem. Gramps Eddie & Grandson CJ (21 years ago, 26-Mar-04, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: RCX to Spy messages thru IR communications route
|
| (...) I presume that somewhere that data is being dropped. It isn't showing up as data the tower reports to the operating system. I haven't actually tried the function I posted the other day so it is entirely possible that a Spybot will not (...) (21 years ago, 26-Mar-04, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: RCX to Spy messages thru IR communications route
|
| 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. (...) (21 years ago, 25-Mar-04, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | 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, (...) (21 years ago, 25-Mar-04, to lugnet.robotics.spybotics, lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | RCX to Spybot communication
|
| This is a reposting of a message I posted yesterday in just the Spybotics newsgroup. I forgot to add .rcx and .rcx.nqc so I thought it was worth the double post. My apologies. (...) Okay, after banging my head against this for WAY too long I think I (...) (21 years ago, 24-Mar-04, to lugnet.robotics, lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
