While working on a project I'm temporarily calling "7.3D" (I thought of calling it FTE 3D, but the subject is a bit exclusive), I need to make a PID list for AE, Torque, Dash Command, etc.... "3D" is indicative of "Diesel Data Depot", but that's a lot to type with your thumbs while searching on your phone.

This is a one-page version 1.0, and I'm sure many revisions will follow. If I make the font something like a 4-pitch, I can maybe squeeze a lot more onto the page. However, many of us need glasses just to see the dash - and microfiche on a screen or a printed page would just look like barcode.

In the countless times I have shared an old PID list I have "on file", the list is rarely followed by the owner of a shiny new AE. If one wants to experiment, that's fantastic. If one wants to submit a log to a reader that can find a problem with the truck... this list holds only the basics, but they are a flock of canaries - as long as they are together.

The PIDs are in alphabetical order per "section" (fueling, air, and speed), so this is not sorted by "importance". They are all important, but their interaction between each other is the what really tells the story.

You'll likely note that I have not yet included the red color - Temperature. I'll get to that. EOT is really the only "important" PID for reading an engine - and each time it's just to let me know the engine is up to operating temp. As it stands now, I can look at the ICP/IPR at idle and get a feel for the operating temperature. If you check a temperature PID on your powertrain, you'll likely already know if it's good or bad without the need to share your log.

OK... here comes the obvious question: What's with the colors, Tug? Graphing. If you are comparing custom-made graphs between two runs or two trucks - a red ICP line on one graph (with a blue speed line, a green MAP line, and a black temperature line) and a blue ICP line (with all the other lines shuffled as well) on another graph will get confusing. It's confusing just trying to read that last sentence. Compare two graphs where the PIDs are a consistent color code, and the reading gets real easy. As drivers, you guys won't need to worry about colors - just know that the data guys do.

Well... after all that fanfare... here it is:

 

Thanks!

Every time I get started on projects like this the world slams on it's brakes and tosses me into the Windshield.

Tom

 

Tugsly, In reference to FIPW Should I use your Scaling (3.5ms) instead of X1 in TP?

 

I'm not 100% clear on what you're asking, and I might not be 100% clear on the sheet - but some scan tools/gauges record in microseconds (max about 3000 on a stock tune), and some in ms (max about 3.0 on a stock tune). Whichever you choose in TP, just make sure your FIPW reads in the upper half of the gauge while idling.

Starting the truck will blow past the max I have set for this, but not while the engine is running. There is no harm done to a virtual gauge.

 

I don't know...I may be blowing smoke, I just remember you saying to set the scale on AE to 10 so that the trace will be more pronounced on a graph, while logging. You can see smaller changes more easily. But while setting up TP today, it looked like it was gauging pretty accurately, around 2.6ms, at least in Real time. I was just wondering......

 

Ah.... good memory. That set of instructions was for a specific version of AE that has the wrong multiplier on FIPW. Setting the scale value to 10 corrects the problem.

 

Again, great stuff Tug . I snapped a pic of this table, and saved it for "a day". That day was yesterday. With Torque Pro in hand, i somehow can not get "mg" for FIPW, so running in the "us" version, with 6000max, i'm seeing 2950-3000ish at WOT. Hows my truck doing . (icp 2830ish / ipr 37% ish, map 12.2, cant remember ebp but think its hovering around the 28ish mark)..thank you sir.

 

I don't remember if I put the conversion to ms somewhere in here: [LINK]

Your WOT numbers look good, but your MAP and EBP are in conflict with each other. You can set each PID to log, rather than trying to remember a snapshot of a "movie".