|
|
 | | 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)
| | | | | Spybot Hardware Hacking
|
| Hi All, April's Circuit Cellar magazine has an article I wrote on one method of hacking the Spybot. I emulated the I2C EEPROM with a PIC. I then mapped the upper 128 bytes of the EEPROM variable space (locations 0x80 through 0xFF) for use as an I/O (...) (20 years ago, 25-Mar-04, to lugnet.robotics.spybotics)
| | | | | Re: RCX to Spy messages thru IR communications route
|
| (...) Hi John, I think the low nibble of the first byte contains the Link ID of the Spybot. It is zero if the Spybot is not linked to a controller. 1 if it is linked to controller 1, 2 if controller 2, etc. This should be easy to double check with (...) (20 years ago, 25-Mar-04, to lugnet.robotics.spybotics)
| | | | | Re: RCX to Spy messages thru IR communications route
|
| (...) Okay, after banging my head against this for WAY too long I think I have finally figured out (somewhat) a few things that were previously completely lost to my understanding. If you want an RCX (running RCX2 firmware) to simulate a Spybot Ping (...) (20 years ago, 24-Mar-04, to lugnet.robotics.spybotics)
| | | | | Re: RCX to Spy messages thru IR communications route
|
| (...) very astute info. You folks, and you J.H. are 'right-on' once again! Yes it works, but SPY seems to react only to very specific code strings (message A: byte 0=0x92, byte1=0x23; message B: byte 0=0x92, byte1=0xab; ... etc.), and immediately (...) (20 years ago, 19-Mar-04, to lugnet.robotics.spybotics)
|
|
