Chevy 1 ton mask id

[n01tk]

Loaded the BMKN bin file from the moates site. Ran nicely with the $0E xdf and adx files. Gauges worked great, parameter tree opened and was able to look at data in different locations. Was surprised to see mask id coming up as 31 under the heading $0E parameters? Decided to run the bin using the $31 xdf and adx files. Doesn't run as smoothly. The gauge package won't open etc. Am I missing something. Is this mask id being retrieved from the ECU or is in a template and I have yet to access the actual ecm memory locations?


[/img]

[Six_Shooter]

BNKM is $31 (I assume you meant BNKM, not BMKN). I just downloaded it and checked for myself.

I don't see how loading a different XDF can effect the way the vehicle runs, unless you tried to adjust something with the wrong XDF.

BTW, BNKM is for a 1995 5.7L, Auto (4L80E).

[n01tk]

No I wasn't referring to the truck running smoothly, it was the operation of the program. Sorry for the confusion. I loaded the tunerpro 5 adf and adx for $31 and it appears to be the right match. All the tunerpro functions are active and respond quickly. Still getting alot of connection errors? Six Shooter can I be sure that the 31 that appears in the mask ID location has actually been retrieve from my ECU ?

[EagleMark]

I played with TunerPro for ya and I found that if I open bnkm BCC with $OD it tells me the mask is $31. Since it's the wrong mask I was surprised it was not jarkeled information.

When I opened bnkm with $31 all the information looked accurate...

But the TunerPro def page still says Heavy Duty is $0E ?

[Six_Shooter]

$0D, $0E and $31 all use the same location for mask ID.

I don't know what you mean by the program not running well.

Loading or not loading an XDF does not have an effect on the datastream (ADX) through TP RT.

What do you mean by this:

Six Shooter can I be sure that the 31 that appears in the mask ID location has actually been retrieve from my ECU ?

[n01tk]

Thanks for the help guys. I am now confident I am running the $31 mask.
Tunerpro r/t appears to run well using the proper version 5 $31 xdf and adx files. I can now move on to troubleshooting why I am not going into closed loop.