Page 1 of 1

why isn't my oil temp acquisition correct?

Posted: Wed Apr 24, 2013 2:37 am
by GTIspirit
I have my oil temperature signal connected to pin 9 on the RaceCapturePro.

Image

I'm pretty sure that pin 9 should be Channel 6 of the Analog inputs.

Signal mapping is setup like pictured.

I read approximately 1.22V at pin 9 where the signal is connected. This is approximately 190degF.

So why does the logfile and the Runtime show 1125895796?

I have the wideband O2 connected to pin 8, which should be Analog Channel 7 and it reads correctly, except for the incorrect precision which I previously reported.

So why doesn't my oil temp signal calculate correctly?

Posted: Fri Apr 26, 2013 12:15 am
by GTIspirit
No one has any ideas? The sensor is correct, I'm thinking this might be some kind of bug which is why I placed it in the software forum. Maybe it's the configuration non-updating bug?

Posted: Fri Apr 26, 2013 5:06 am
by brentp
Sorry we missed this. So, what kind of values do you log when you switch the scaling to raw mode? Does it vary as expected?

Also, can you post your race capture configuration here in the thread? I'd like to check it out.

Thanks,

Posted: Sun Apr 28, 2013 8:05 pm
by GTIspirit
Crazy values when in the raw mode.... As in off the scale crazy, as in >1023, which shouldn't be possible..... The exact raw number was 1131610112, 1131741184, 1132199936, and thereabouts.

Posted: Sun Apr 28, 2013 8:25 pm
by brentp
Got it, thanks. Can you post your racecapture config here, or email it at brent (a) autosportlabs.com? I'll see if I can reproduce it.

What values do you see if you alternately connect the input to ground (0 volts) and the race capture vref (+5v) ?

Brent

Posted: Sun Apr 28, 2013 8:44 pm
by GTIspirit
When grounded I got two raw values, 1077936128 and 1073741824.

When connected to 5Vref I got a constant raw value of 1149222912.

Posted: Sun Apr 28, 2013 9:30 pm
by brentp
Ok, thank you. I'll get back on this ASAP with my findings - hopefully I can reproduce this tonight.

Posted: Tue May 28, 2013 2:54 pm
by brentp
Turns out the logging precsion of 0 caused this problem; it's now fixed in the latest firmware. Confirming you're seeing the correct values now?