Datastreams

Discuss General Motors (GMC, Chevy, Pontiac, Hummer, Cadillac, etc) tuning topics here. Request definitions, discuss parameters, etc.

Moderators: robertisaar, dex

Post Reply
J Ludwig
Posts: 14
Joined: Wed Aug 24, 2011 3:18 pm

Datastreams

Post by J Ludwig »

I have a motorhome on a 1993 P30 chassis. ECU 16147060 BAMS (what is the signifance of BAMS?), mask $85, 7.4L, 4L80E trans. I can connect and display data with TunerPro RT V5 using either 138 ADX or 177 ADX, 138 is mostly engine data, 177 seems to contain transmission data. Both were imported and converted from ADS files using TP5. I noticed in the Mode 1 request in 138.ADX the last character is different than the request in 177.ADX, i.e., $F4 $57 $01 $00 $B3 vs. $F4 $57 $01 $00 $B4.

I also noticed there is a diffence in parameter locations in the return, i.e., word 19 in 138.ADX is Oxygen Sensor variable and word 19 in 177.ADX is Engine Coolant Temperature.

My question is: Does the ECU return different messages depending on the request? After the ECU returns its message, do you have to give it a Mode 0 request or do you have to give it another Mode 1 request to keep the data coming? Or does it simply keep sending data?

Another question: There are two .XDF files that seem to work. One is titled 85.XDF and the other 16147060.XDF. Both seem to work but the latter is a much bigger file and has a later date. Is there an advantage of one over the other?

You are probably wondering why I care. My end goal is to build a dedicated monitor using a microcontroller that will display values on the old analog TV set that's taking up space in my dash. I also want to use that data to calculate fuel flow/fuel totalizer for that display.
Post Reply