 | | RE: NRLink reading RCX response w/ RobotC
|
|
There are three steps to reading an I2C message from a sensor. 1. Send a message to the I2C sensor to initiate the read. Look at the program "NXT HiTechnic Accelerometer" in the RobotC sample programs folder for an example that you can clone. (...) (17 years ago, 1-Aug-07, to lugnet.robotics.nxt)
|
| |
| | Re: NRLink reading RCX response w/ RobotC
|
|
(...) Searching for "robotc i2c" returns 3 message in the forums: "Interfacing with Lego Sensors" "Help with US sensor!!" "RobotC I2C Help" Only the third message describes "Test I2C Messaging". It's very specific to the message thread and in it you (...) (17 years ago, 2-Aug-07, to lugnet.robotics.nxt)
|
| |
| | RE: NRLink reading RCX response w/ RobotC
|
|
(...) I couldn't find it either, but its out there somewhere. (...) Agreed. It started as a internal debugging tool and was left visible for the small handful of power users who write their own I2C device drivers. (...) Agreed. I went back and (...) (17 years ago, 2-Aug-07, to lugnet.robotics.nxt)
|
| |
| | Re: NRLink reading RCX response w/ RobotC
|
|
(...) I downloaded the SDK from (URL) but can't find any reference to the message format. Perhaps this is the wrong SDK? I've looked in all the doc .pdf files and skimmed everything else. I sure am having a hard time locating things. (...) So what (...) (17 years ago, 3-Aug-07, to lugnet.robotics.nxt)
|
| |
| | RE: NRLink reading RCX response w/ RobotC
|
|
(...) Look at the file "RCX2 LASM Byte Codes" for a description of each of the available opcodes. Read (URL) coupled with the contents of my previous email. (...) No valid message starts with with 'opcode' byte of '00' or 'FF'. [Check out the above (...) (17 years ago, 3-Aug-07, to lugnet.robotics.nxt)
|
