Tried another thing today: PID 16A7 is IAT2 Volts

I created a custom PID with 2216A7 and just the equation “A” (because I got no equation) and got a display with a value jumping forth and back between 150 and 167.

Then I drove around and saw that one of the values stays at 167 and the other one went done to about 108 with the engignes heating up!

So I startet with 150 167 and ended up with 108 167.

Found a PDF, where IAT2 is explained at page 147:
http://www.motorcraftservice.com/vdirs/diagnostics/pdf/OBDSM1104.pdf

There is written, that if the values goes down, the temp goes up. So it seems that this values really COULD show the IAT2.

But there is still something wrong with the values jumping forth and back AND I don’t have the right equation for this.

Markus

I just signed on, since I’ve had the paid version of Torque for a while and this issue is important to me.

First this is a great app, I have an 03 Cobra (2.3 Whipple) and using my DroidX instead of a netbook to check values is a big advantage. I use the PLX KiWi blutooth.

I’ve followed this thread and the one on SVTperformance, since IAT2 is critical for monitoring heat after the intercooler. I don’t have any background in OBDII, but I have been an ME for well over a decade, and this is what I have found so far.

16A7 is for volts, and without an equation it should read between 0.0 and 5.0

16A8 is in degrees (F), and could be anywhere from 0 to 300, again you shouldn’t need an equation.

For Ford the header is 22, so the PID for IAT2 (2216A8) is correct (I haven’t found anything that says different).

I’ve tried both of the above, and Voltages (1155 and 1172) that are on the PID list, but all four only show me dashes. The PIDs are accessible, since my XCal2 can read and display the values.

If this is not an issue with Torque, another way might be to contact one of the tuner vendors and see what PIDs they use to access DOWNSTREAM_ACT.

Thanks to everyone for keeping this going, the popularity of this app would improve if it’s resolved and the Cobra/lightning community is made aware of it.

Note: Ian can you give us a Ford PID value you currently use, say RPM, and see if we can add it manually to check functionality?

Quote from Ricksterman on April 19, 2011

16A8 is in degrees (F), and could be anywhere from 0 to 300, again you shouldn’t need an equation.

Yes you do. The typical range for straight variables is 0 to 255, any higher then you use a combination of A and B eg: ((A*255)+B)

The equation parser in Torque requires the use of brackets to make sure the equation is parsed in the correct order.

RPM is a standard OBD PID.0x01 0x0C (010C in torque) with the equation ((A*256)+B)/4

Took a closer look at the symptoms this morning.
I want to know what the pure readings are for (A) and (B) and here is what I got:

– whether I use “alternate Header” or not, all Displays/Dial work as usual, so no changes with “alternate Header”

– When I use equation “(A)” with 2216A8 / IAT2 (°), readings are 168 and won’t change ever
– When I use equation “(B)” with 2216A8 / IAT2 (°), readings are 0.0 and won’t change ever

– When I use equation “(A)” with 2216A7 / IAT2(V), readings are 167 and won’t change ever

– When I use equation “(B)” with 2216A8 / IAT2 (°), readings start at 168 and goes down to about 110 when engine heats up

A friend of mine took a closer look at LiveLink and this is what he got:

Line 102239: iat2voltiat2_voltsenvironmentiat_sensor_2_(voltage)15371h1O*Volts=N/51765625r Series 8 – scaling of 0.25″gyg#Ai

Line 102240: iat2tempiat2_tempenvironmentiat_sensor_2_(temperature)15381h1O*deg C=N-40765625r Series 8 – scaling of 0.25″ff+Ui

Don’t know the meaning of this, but maybe it helps someone.

Hi

There is a bug (which happens to be fixed in the version running on my test phone) whereby if you have the 2 displays getting formulas from the *same* PID, then things will go a bit wrong in terms of getting the correct figures over.

If you are testing with changing the formula, then at the moment I would recommend only using one display visible on the screen at a time until I’ve finished testing and posted the fix (I thought this was going to take a while to fix, but managed to sort it out today, I just have to complete testing)

Hi,

just only info about scaling of IAT2_V:
simple scroll bits to right by 6 bits, so you could do:
((A*256)+B) * 0.015625
or more generally
((A*256)+B) / ( 2^6 )

OK, got a solution for this again: just put in the equation for calculating °C out of °F

Here is the extended PID for IAT2:

Mode and PID: 2216A8

Long name: Downstream ACT
Short name: IAT2
Minimum Value: 0.0
Maximum Value: 200 for °F OR 100 for °C
Scale factor: x1
Unit type: °F OR °C (both works)
Equation: (C-32)*5/9

Have fun!

Markus

Sorry – I forgot: Yes, “alternate Header” was turned on.
All the other PIDs work as usual – as far as I can see.
The same time I played around with the IAT2, i played also
with the O2 sensors and short term fuel trim. All of them worked.

I will try it tomorrow morning without the “alternate header”.
Was so happy that I forgot to check this 😉

Markus

I can get Ford specific PIDs to work when using the alternate header but then the normal out-of-box gauges will not work and vice-versa. Can there be a way to use both at the same time?

Whitesnake,

Great job, I may have to try your OBD adapter.

Nothing outside of the normal PIDs work for me, I only get dashes, including the Ford specific ones you can add in the software. Alternate header makes no difference. I should at least get a value, it looks like it’s not communicating correctly, I don’t see the green light blink.

I have a PLX Kiwi and a DroidX.

Ian anything I can try to help troubleshoot this?