TunerPro/AutoProm on a Dell laptop running WinXP...

I just loaded XP onto this thing last week and I can't get the AutoProm to work right. It'll datalog $8D just fine, but won't log $88. It also won't emulate anything at all. I've tried $88, $8d, and $6E on their appropriate ECM's all with the same result. The bin uploads and verifies fine, and if I enable emulation I get the green light from TunerPro, but the ECM doesn't seem to see the emulator.....the car just cranks and runs in limp mode. It's the same situation on an '89 GTA, a '91 Lumina, and a '7727 sitting on a bench running off a desktop computer power supply (this one doesn't crank and run, due to lack of an enigine.....it just keeps the SES lit and refuses to respond to anything.) FWIW I've verified that the '7727 is good by burning the same bin (AUJP bone stock) to a chip and running off that....works and datalogs without a hitch.

I've read and searched and read some more....I've messed with port settings and AutoProm settings and un/reinstalled the USB drivers, all to no avail. I think at this point I need some help.

Anyone else had a similar problem? And hopefully resolved it???

 

I got mine to connect consistently after I did what I said here:

https://www.thirdgen.org/techbb2/showthread.php?s=&threadid=245619

 

Regarding emulation, did you verify that the bin you uploaded was correct (namely, that the checksum was correct or disabled)? Also, are you sure you have the header plugged into the adapter in the ECM correctly and the adapter is set up correctly (jumpers setup for 28 pin)?

 

Yes and Yes, Mark.

I've tried using the regular checksum and with "AA to disable." I know the checksum is good because if I burn the .bin to a 27SF512 and plug that into the adapter it works just fine. I've been using Craig's G1 memcal adapter with pin1 (red stripe) of the emulation header away from the knock board (same place I put the notch in the chip.) I also tried it the other way just on principle and got the same result.....limp home mode.

I really think the $88 logging issue is with the datastream definition. I had a '94 LT1 4.3 Caprice come into the shop today, so I took a couple of minutes to plug into the ALDL. It logged fine using the LT1 F-body .ads (although with some info obviously in the wrong place.) I thought about trying to emulate on it, but I don't have an LT1 ECU and the customer was waiting so I couldn't really pull the ECM out of the car anyway.

 

Hmm. If you're absolutely certain that what you're uploading to the emulator is known to be good and that your adapter is set up correctly (i.e., you can run the car off of a chip burned with the image you're attempting to emulate), then there may be an issue with the emulation output stage of the AutoProm. Contact Craig and he'll help you investigate this and ultilmately replace it for you (no charge, of course) if necessary.

Regarding ALDL datalogging, if you can log one application but not another, its likely the datastream definition, as you've surmised. Note that, currently, TunerPro doesn't do too well with 160 baud applications (soon to change). I know that $88 is 8192, so it may just take a tweak of the ads file. $88 is a V6 firebird, correct? I'm pretty sure there are others successfully datalogging with TunerPro for $88. Perhaps it requires the 10k between A & B?

 

The $88 mask xmits chatter, so it may be difficult to connect. Doesn't need the 10K.

RBob.

 

This is another problem I'd like to tackle in the 4.X series. I just need to think up a way to generalize a "request silence before attempting connection" routine that is user-configurable. 90 vette shut up command is different than $88, for instance.

 

I'll email Craig in a few and see what he thinks about the problem.

$88 is a '7730 SD V6 code, and I've tried it on a '91 Firebird, '92 Lumina, and a '91 Beretta ('7727 car) all with equal (read as: no) success. I'll try it again, and I'll be a little more stubborn about it this time. Last time I gave up on it connecting after about 10 tries.


I was looking at the info in the A148.ds (90-92 3.1 vin T) file I downloaded from Craig's ftp site, and it led me to a question about the .ads file format. In TunerPro, when editing the datastream definition, there is an entry labeled "payload offset." In the $88 def it's set to 4. Is this stating that the 4th byte of data is the first data byte, or that 4 bytes need to be skipped and the 5th byte is the first data byte? I doubt this will cause a connection issue (more likely just bad data) but it made me wonder so I thought I'd ask. Thanks guys,

:hail: :hail: :hail: :hail: :hail:

 

Then again, if the offset were wrong, and it skipped the first data byte altogether and counted the bytes starting with the 2nd, then it would see the checksum as a databyte and not see a checksum at all. Would this cause failure to connect or just packet errors?

I ask because the offset in the .ads is set to 4 and in the a148.ds it describes a 3-byte reply from the ECM and then 63 bytes of data starting with the 4th transmitted byte, followed by a checksum as the 67th byte.

 

Right. Offset is 1 based. 4 is the correct offset.

 

Good to know. Thanks.

 

Does anyone know if the A148.ds file actually worked? I have a 90 Beretta 3.1 that cannot connect.

 

I had to actually edit the "handshake" to something different in the definition file. The normal sequence was something like F4, 56, 01 and mine ended up being F0, 55, BB. Found this out after useing an earlier version of craigs datalogging software.

 

My problem ended up being a bad solder joint in the emulation output of the AutoProm itself. Craig fixed if for free, of course, but then I aquired a '91Z and quit fooling with the customer's V6's. So no, I never did verify the a148.ds.

 

Great, thanks for the input. I'll give er a shot tonight.

 

Well, I finally got it to work. FYI TunerPro.

F0,56,01
63 bytes
04 offset

Once I get all the data entered, I'll email the TunerPro ads file (A148) to Craig and Mark.