16147060 $85 Superceeded to $D8

[dave w]

Mark,
I think I've just encountered a 16147060 .bin that will not connect with either TunerPro or DataMaster. I think the attached .bin is from a motor home chassis. If you get a chance, maybe you can let me know if the attached .bin is $D8? The .bin will not connect to a scan tool!

Thanks,
dave w

I used the .adx posted by EagleMark, and it's working fine for me.

dave w

[Six_Shooter]

The ADX I use has connection commands.

The car I tune with it is wired exactly like an OEM vehicle as far as the ALDL side is concerned.

[EagleMark]

But it does not have other modules that a stock truck with that PCM would have tied into same data line... Something is differant, beleive me, I trust you and tested your adx again after I added commands from ALDL.ds file to another one.

[Six_Shooter]

What other modules would be on that line in a 1993 Chev full size truck?

[EagleMark]

ABS is the only thing I can think of? It's on my 90 Suburban (160 Baud pin E) but has it's own pin on ALDL port... beleive me I racked my brain on this that day because you said it works. I don't remember the specifics but had to make a command change for connection, you needed a connection which is what ALDL.ds file says.. I could not get yours to connect, the one above connected first shot each time, even after restarts. If I weren't so tired I'd look at the 2 to see what I had to do, probably loose sleep over it...

ROBERT!!! Can you look up what is on a pin M data line from 1993 Chevy truck with 4l80E trans?

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.

[RobertISaar]

93 diagrams don't seem be very complete.... and the parts that are there are quite a pain to look at and not much help at all for the data circuits.

i did take a look at the ABS stuff, but it was quite vague. i think it was implying that it was connected to pin H?

[chevmasta]

Update:

With SixShooters 85sort.xdf and EagleMarks $85-16147060-V5.adx‎ posted in the 7060 thread, I CANNOT connect to my PCM. It says "DA connecting" and it will never connect. In fact, I cannot connect with the other .adx posted in that thread or when I convert the .ads that's posted in that thread:
7060 _new.adx‎ (173.5 KB, 15 views) 16147060_4L80E_A138_A177.ads‎ (219.2 KB, 10 views)


I CAN use the 85sort.xdf and the A138.adx (adx downloaded from Tunerpro's website) and I can connect just fine and log just fine.

What's kinda weird (maybe not? I'm a noOB!) is when I log with this A138.adx I then can use $85-16147060-V5.adx‎ and it will playback my datalog just fine using the dashboards. (That .adx has some good dashboards).

Does this make sense?






I really need to find an .adx that will work with the 85sort.xdf. That .xdf is well organized and defined. However, I don't have an .adx with dashboards. Is there a way to import dashboards without creating them?

Remember too, I have a BANC.bin

Sorry, I'm an idiot like I've previously mentioned.

LOL, Ryan

[1BadAction]

Sooo... My $85 mask is now $D8 with the same XDF? I really need to start on this 7060 now that my suburban is together and cranked up, but it's been a year since I've had my head wrapped around TBI tuning the last time.

[EagleMark]

Yup, here's the latest files.

[1BadAction]

Thanks Mark. They are referring to PE as "WOT mode" correct? I need to make sure it's off before I start on this thing...

[EagleMark]

Right, PE is titled WOT in this mask, I don't know why, just what the original author started with. I think next time I work on it I'll change it to PE.

Turning off PE just gives you more opportunity to get more BLM cells filled in data logging.