The header was indeed blank. I’ve typed Auto in the header field now and will see if it helps. Thanks for the advice!

Another question about the AFR PID…

PID: ff1249 gives me pretty accurate data from the narrowband but the data is in 14.7:X format which is the inverse of what most of us are used to looking at.

Tried to create a custom PID using ff1249 and I get no data..

even tried the equation A+B+C+D to check if any of the variables came back with a reply but still nothing… did I input the mode wrong? tried 221249 but no go also. what header should I use?

May I also know the standard equation being used?

Thanks,

Ian

Quote from admin on June 2, 2011
ff1249 isn’t a PID. It’s an internal value inside Torque which isn’t generally accessible other than using an AIDL request (read: writing a plugin).

I’ll have a look at AFR tonight and sort the units out.

Good to hear.. at least puts my mind at ease

Would like to report that YelloEye’s PID:01 34 and the accompanying equation works on my 2007 Subaru Forester XT. Will still be checking accuracy by comparing it to RomRaider logs.

Side question: Is it possible to do Custom PIDs that use data from 2 or more PIDs in the equation?
ex. (PID:0110 * 60)/PID:01Oc or (MAF*60)/Engine Speed

Isn’t there a way that the AFR can be calculated by other working parameters? It’s not working on my car probably due to the car’s ECU/compatibility, but still curious.

Considering a wideband sensor with a physical gauge for accurate AFR. Too bad I cannot connect that to Torque (AFAIK). Already have a oil temp gauge (not supported on my car) and boost gauge (much faster response than by OBD).

I have a good adapter and fast smartphone and also the setting is on “fast communication”, but I have 7 or 8 PIDs/sec. Not slow, but there’s definitely a delay of a second or so (maybe due to the bluetooth connection?). What should be normal?

Not sure about how to find/create a custom PID. I’ll have to do some more research on how that works then

edit: I saw this topic http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=797.0 which states that >15 should be normal. So, maybe it’s my ECU (2003) that is not delivering data fast enough…

Those are PIDs for the O2 sensors, which should work fine

It’ll be interesting if you could provide a debug with those PIDs on screen – start the app, let it connect, go to the realtime info scree with those sensors visible, wait a short while. Then press ‘menu->more…->send debugging info’, make sure you write something in the description like ‘camaro afr test’ so I know who it’s from (and what its about)

I’ll be able to see if your vehicle supports O2 sensor readings (which it should do)

Debugg sent.

A buddy of mine with HPTuners said that pid.6160 (wb lambda b1) or pid.6161 (wb lambda b2) might work? I dont have a wideband tho…

That might work as(assuming it’s a mode 22 PID) :

PID: 226160
Equation: 14.7 / (1 / A ) (this is a guess)

nextnme:

Got the debugs, thanks!

Have had a look – the response from the ECU indicates that you don’t have any monitorable O2 sensors (which is what the AFR measured is based on), so it’s impossible to work out the AFR using the standard OBD2 PIDs (which explains why it’s not working in your case)

This means that we’ll need to find the extended Mode 21, or Mode 22 PID for AFR (which the above *might* work)

Once I’ve got the track recorder export done, I’ll be spending some time on the TorqueScan app making it a *lot* more user friendly and usable (it’s a little bit techie oriented at the moment)

That’ll help people who want to find PIDs out.

Hi!

If you have the sensor voltages, then it will already be working for you in the app, if not *please* send me a debug so I can have a look (though I have tested this a lot and it’s working here!)

In the case of the other posters debug, his ECU capabilities were:
7E8 06 4100 BFFFB993
7E8 06 4120 8007E019
7E8 06 4140 FED00000

Which do not include the O2 sensor equiv, so in that posters instance, it’s not going to work as the sensors simply aren’t available, specifically, if you look at the sensor block for 0x20 for his vehicle, as reported by the ECU, these are the supported sensors (which exclude the O2 sensors):

01 21 2 Distance traveled with malfunction indicator lamp (MIL) on 0 65,535 km (A*256)+B
01 2E 1 Commanded evaporative purge 0 100 % 100*A/255
01 2F 1 Fuel Level Input 0 100 % 100*A/255
01 30 1 # of warm-ups since codes cleared 0 255 N/A A
01 31 2 Distance traveled since codes cleared 0 65,535 km (A*256)+B
01 32 2 Evap. System Vapor Pressure -8,192 8,192 Pa ((A*256)+B)/4 - 8,192
01 33 1 Barometric pressure 0 255 kPa (Absolute) A
01 3C 2 Catalyst TemperatureBank 1, Sensor 1 -40 6,513.5 °C ((A*256)+B)/10 -40
01 3D 2 Catalyst TemperatureBank 2, Sensor 1 -40 6,513.5 °C ((A*256)+B)/10 -40
01 40 4 PIDs supported 41-60 (?) Bit encoded [A7..D0] == [PID 0x41..PID 0x60] (?)

Unfortunately O2 voltages from 0x01 14 can’t be used as they will be different between types of sensor (as well as oscillating)