I was basing the change on the second
screenshot boost min. A slightly positve
boost would give the full display for
scaling purposes.

The EBP equation in Torque is in psia from
6.0L users.

Baro, MAP and EBP should agree within +/-
0.5 at KOEO.

There is a baro from phone display that you
can add to your dashboard if your phone
supports it. (Not sure what units are displayed
mbar?).

221127 is a pid for Baro and
0111 throttle position listed in wiki. I
also found a reference to 221442 as a
possible baro pid as well.

cap77 quote:

Are you operating both devices at the same time using
the obdii splitter?
I wondered if this was possible if the adapter tester
address was changed using elm AT PP or AT TA
command. (Assuming both devices are using
standard F1 address).

Endquote

I ordered a Y cable and it should be here this week. Have not used yet. I plan on hooking my usb adapter from AE to one and the elm bt for Torque on the other leg. On the device side, they should connect to those 2 fine… On the PCM side… We will have to see.

Not sure if the ECU will let 2 devices connect to it at the same time yet. Otherwise, I’ll just have to watch separately and record “something else” along side them so I have comparisons for cross-reference values.

Mine? Not getting BARO data for the ECU. My phone does not have internal BARO (no pressure sensor in HTC Vivid). Set the value for mine from 0.0 to 14.7 psi. I’m less than 1000 feet, almost at sea level. But I read it with AE, so I know that the PCM see’s that sensor.

What is the PID number and equation for BARO? The one in Torque (at present) is not an extended PID so I can’t just see the values from the extended PID editor. And I haven’t found the file name or location of the default PID’s yet… to see what is there…

There is a big difference of pre-’03 7.3’s and later-than ’03 6.0’s on BARO. On 7.3’s, it uses and external BARO sensor. 6.0’s use a built-in, internal to PCM BARO sensor.

I’m thinking if I can work out BARO and populate the variable BARO(), then Boost will fall into play better.

I’m behind the ball on this. Starting with Torque for only a week so far. But a mechanical and a programming background. Want to catch up on this soon. Just now trying to figure out the author’s logic and how things are laid out.

Maf:

Have you tested pids 221127 or 221442
as possible baro pids. Since 7.3’s have been
known to have problems with certain diagnostic
commands… I suggest testing with KOEO for
safety.

How are the given pids working for you? Are
they giving reasonable readings from your
sensors as they were based on mj’s?

C410F1 if Auto or blank do not
return a response. (physical
addressing).

Mode 1 might be 616AF1 (functional
addressing)

Edit:

Your IAT temp registered 11.1 °F. Were
your actual temps that low?

Baro
Header: C410F1
Mode/Pid: 221127
Equation: A*0.1
Units: psia

Baro
Header: C410F1
Mode/Pid: 221442
Equation: ((A*256)+B)/27.67985874
Units: psia

Baro
Header: C410F1
Mode/Pid: 221442
Equation: ((A*256)+B)/4.01463133
Units: kPa

Baro
Header: C410F1
Mode/Pid: 221442
Equation: (A*256)+B
Units: inH2O

I can’t test “running” until later this week. Now, in the middle of pulling my turbo off. Long story. (Was going to just change wheels, then found it wasn’t stock and someone before me had “glued” it back together!!!) Waiting on a rebuild kit to show up Wednesday).

But I’ll test it (just static) when I get back from getting a 15mm swivel socket to get the last 2 exhaust nuts off… Have to hurry, as it’s pouring outside and 60 mph gusts… but supposed to be worse here tomorrow.

Edit– Back. That parts store didn’t have swivel sockets and the wind direction changed. Free to work on this now. Inputting new PID’s.

the one that got me is boost hitting 35 and it didnt freak out, twice today I crossed the line exceeding MAP allowed

I tried logging but only data I got was gps and rpm even though I had a looong list of PIDs entered. must have to do something else to get it to work
a log of it hitting MAP overload would be fun.
I found a very steep longish hill not too far away for testing, so I will probably fly off the side looking at gauges

on the EBP I cannot ‘floor it’ until I get the ‘map fooler’ done so we wont know how high that will go for a bit. wonder what it will do as I exceed its range. I think I can use a zener diode like the super duty guys use on their MAP sensor to limit what the PCM sees from it

If data logging was enabled while
you were adding pids to log you
would need to stop and restart logging
for the new pids to be included.

Cant remember if Torque does this
for you automatically.

There is a toggle in trip settings that
may need setting.

Dont forget Track Recorder dash cam
plugin if you dont have it.

Pressure can be expressed in many
forms kPa, psia, psig, inHg, inH2O, atm,
hPa and Pa to name a few.

psia is expressed in absolute form (zero
is anchored).

psig is relative to atmospheric pressure and
is subject to atmospheric change.

psi is more generic term for psig.

hex data for a pid can be read by testing
the pid from the pid editor while connected
to your vehicles ecu.

You can set your preferred units in settings.
If torque recognizes the units it will convert
them based upon your preferences.
Example: converting a °C temp to °F. A number
of the predefined pids are in °C.

For units not recognized by Torque the value will
match the equation. Say you wanted to display
your speed in km/h but your preferences were set
to mph so Torque would try to convert… just use
units not recognized by Torque to leave the value
as is.