we have tried several sensors in our FTC trek- IRSeeker, Compass, Gyro, TETRIX motor encoders etc and have made them work. It is useful to see the global variables change, but now I am interested in getting the kids to actually store those global variables in a with time stamps associated, so we can see what our sensors are telling the microcontroller. This question actually came out of trying to use two VEX ultrasonic sensors and getting erratic results (mostly poor) - it appears that we were getting some cross talk or something. Anyway, this prompts the bigger question of how to store the global variables so we can review them later - both VEX and NxT (FTC). THANKS

Hi Chuckmerja,

Robot C has a nice data logging feature for the NXT, it lets you save information to a text file on the nxt to be uploaded and reviewed later. Here is some code data logging code I made a looooong time ago, it should still work. Let me know if this is what you were looking for.

Also when using more than one sonar sensor at the same time, a ping that one sensor sends out may be read by the other sonar sensor and cause bad readings like you were exsperiencing. You may want to look into pinging one sensor at a time and reading the result before pinging the next sensor B-)

Good luck! hope this helps B-)