I have attempted to use the .ads file for an 8747 to no avail. can anyone point me in the right direction?

 

moe info please what is exactly going on is this problems setting up your tunerpro or what?

 

The problem is that there is no 8746.ads on marks website, i figured since 8747 is identical except for an intake air temp sensor on winaldl that it should produce the proper data for every other field(I tested this to be true on winaldl) I get a connection using an 8747.ads file but the info is garbage.

 

Thats kinda crazy... I posted a reply a couple of days ago.

Yes Colt, it is a problem with setting up TP, there isn't a publicized 8746.ads that i am aware of, or have been able to find, I tried using an 8747.ads, I knew that the only differrence should be an IAT value and O2 X-counts, I input a simple hack for SA and no dice, So I treid it again without the hack thinking i screwed up, the same results. It communicates but not properly. Values such as rpm with engine off 6000, mph car in park 255, map fluctuates with throttle change, engine off. Surely some one has datalogged with this setup, I'm positive that I'm going to kick myself when I find out what is going on.

Well, thanks for your time
TTYL Ben

 

if you looking for a 1228746 ECM, check here,

http://www.moates.net/fileman/

then enter the user name & pass word from this page

http://www.moates.net/info_pages.php?pages_id=14

then find 4) Datastream Definitions

 

i found two definition files on moates.net both giving me the same results there has got to be something else going on here!, any ideas?

thanks denn

 

In fact, the 7747 ads file will work, hacked as you say. ( I'm doing it ) BUT......
Pretty much all versions of Tuner Pro prior to 4.14 have the problem bad.
It's still present in 4.14 but not so much.
Yesterday, I ran about an hour and a half log, of which about 10 minutes is the random
junk you are seeing. It seems to lose sync with the data stream at random, but most of the time, it does, in fact, log correctly, and may well re-sync and log good data even after you see the junk.
The give-a-way for valid data seems to be the battery voltage more than anything.
13-14 volts running = good data.
0.03 volts running ( or any number not reasonable for battery ) = random junk.
The 7747 in the same vehicle NEVER faults, so there is apparently "something" undocumented that is different in the data stream.
I've seen it on more than one vehicle now, yet Winaldl seems to work fine.
Hope this helps, some.