No, there is no difference. They are both ground.

- Xander

Hello!

I've got a TPA81 heat sensor, and I've wired it to my NXT as described by Xander in the earlier comments of this thread. The problem now is using the sensory data in a useful way. I have virtually no understanding of how to deal with the data that are passed from the thermal array sensor to the NXT. That is to say, my ROBOTC experience, while pretty extensive, is limited to native and third party sensor that have drivers to deal with all of these raw data.

In my first (and admittedly ignorant) pass at this, I tried a very basic call to the sensor, printing the result to the screen:

nxtDisplayCenteredBigTextLine(6, "%d", SensorValue[S1]);

Not surprisingly this didn't do much. Given my vague understanding, the NXT has to ask the slave (in this case the heat sensor) to pass some information back to the brick. Any suggestions for how to get up to speed with this? Thanks in advance for your help!


-Brook

Hi Brook,

I am not sure if I will have time to do this today, but I'd be happy to see if I can come up with some code in the next few days. Send me a PM tomorrow to remind me!

- Xander

Here's a driver and a test program. I don't know for sure if it'll work since I don't have one of these.

pixeldata is an array with the following layout:


Let me know how it goes.

- Xander

I got two of these thermal sensors.

I found an interesting problem with one of them. Symptom:
- executing a test with heat sensor#2, data looks good
- terminating the program. Rerun. Data looks invalid.
- restart the controller, rerun the test. Data looks good again.

We went thru this sequence a few times with #1 and #2 indpendently, switching wires, etc. Same symptom happens with one of the wires. I'll have to wait until next week to play with the problematic wire. For the time being, I wonder if anyone may have an advice on this one!?

So, looks like something needs to be reset!?