16147060 $85 Superceeded to $D8

[EagleMark]

I've used DataMaster TTS for $85, when when TunerPro RT $85 didn't work. DataMaster TTS is free for 20 data logs.
dave w

If the $85 EFI system is a conversion and rewired like Six Shooters then the ADX file will work. But in a stock truck or wired like a stock truck then it needs to have a connection command. The ALDL wire is dead and has other modules tied to the one wire so each module needs to be told what to do. Here is the note in ALDL file:

ECM OVERVIEW
------------
This ECM is a slave on a masterless ALDL. In other words, there is
no traffic on the ALDL, so when the tester is connected to
the ALDL it must initiate communications with the ECM rather than
waiting for the F0 poll.

I now have a TunerPro $85 adx file that will connect to a stock 16147060 truck.

If the cals were superseded, the data stream should be the same with both masks. The dealer scan tool (tech1) selects a data stream by year, make, and model entered by the tech. It knows nothing about the mask id and neither do techs operating it. Disassembling part of the car to get the ecm cover off and read the BCC takes too much time and since the only way to read the scan id is with the scan tool, scan id wouldn't be an option either.

In looking through the ALDL file list I could not find another option for this truck, not knowing if the list is complete I did not know if it was correct but after many hours of testing I would say you are absolutely correct. After getting the connection command working all data looks correct.

The attached $85 .bin file is from a 350 I used DataMaster TTS to tune with. Maybe this will help as a starter .bin?

dave w

I looked at your bin and it is a $D8. So far every BCC I have checked marked Axxx has been $85 and superseded to Bxxx which is $D8.

I spent over 14 hours yesterday on a 3 hour tune while I had this truck. Good news is we have a ADX file that connects every time for a stock truck. Because of the note above from ALDL file connection the truck must be running to connect. I did not do complete testing for all scenarios but if truck is running, click connect and data starts flowing within a second. I did try to connect then start truck and no data.

More good news is I can not find anything wrong with the $85 XDF I used yesterday while tuning a $D8 bin file. I have not checked every signal hex address from hack to XDF file but of the hundred or so including the most important I did they all match up. Using the XDF to tune truck was easy and reliable. Customer was thrilled that his truck finally ran better then it did stock when it ran worse after a rebuild with aftermarket cam and intake! The owner of truck was also ASE certified tech with his own shop and 20 years experience. May be the first vehicle I have ever tuned that did not have a mechanical issue to correct first!

I want to do some cleaning up of the ADX and XDF files and I will post them for anyone who wants to use them.