Greetings all
I am using TunerPro V5 and when trying to connect my laptop to the ECM to log I get several Data Error messages and TunerPro will not connect to ECM. I am using 1227730 ECM, $A1 mask and ASHH bin. I made sure that I am using the proper COM port and latency is set at 1 sec. Tested the ALDU1 cable using TunerPro and TP states that the cable is connected and is functioning properly. Even tried a second cable with same results. The car starts and runs great although it needs tuning as I recently changed the transmission to a 700R4. My engine is a 3.4L V6 with H260 cam and shorty headers, the rest is stock. A few weeks ago all was working well, tuning was in progress then I attempted to connect my wideband to allow logging. I was attempting to install a patch while the ECU was running code (key on engine off) when things went wrong. My copied Bin file got corrupted. Installed new Bin file and the car started and ran well but the data acquisition does not. Measured the voltage at the ALDL connector Pin A and M (gnd and data signal) and measure 0 volts. I suspect I may have to replace the ECM.
any suggestions are welcome.
Ray

 

If your laptop does not connet, you are on the wrong com port. If you have windows 10/11, connect the USB to your laptop and go to device manager. Under the LTP port device, look to see what windows says is available to use. Whatever that number is, put that number into the comm port in WUD and the screen should immediately come alive with key ON. As far as Tunerpro 5 goes, you do not connect your ECM to it. TunerPro is strickly for editing your tune, saving it and then uploading it to WUD and into your ECM. Also, be SURE you use the extension cable provided by Dynamic EFI or from me if you bought it from me. If you use other cables you can fry the EBL board. We just had a previous customer of Dynamic EFI with a bad EBL. He used the wrong cable and literally put a hole in both of the PICs and more. I hope this helps and sets you on your way. GL!

 

Not entirely true, TunerPro allows you to datalog as well. I believe he's using a regular '7730, not an EBL; not sure if the EBL interacts any differently with TunerPro vs the factory '7730.

 

It does, and my bad for assuming that he was using an EBL. GL

 

the only thing I can suggest is to get rid of all of your xdf and adx files, then download fresh copies and start over. Maybe a file(s) got corrupted or something.

 

Also, it might not be a bad idea to do a fresh reinstall of tuner pro and uninstall and reinstall the latest drivers for the aldl. Even though it was working properly before the incident, and tunerpro says it's talking to the aldl, it can't hurt and it's free to try.

 

Thanks for all your replies. I am not using the EBL system, I'm using a regular 7730 with Ostrich II and ALDU1 cable. I have tried fresh $A1 XDF, ADX with same results. I will try installing new Drivers even though my laptop states they are functioning correctly. Frustrating when tuning was going well but now stopped because of this. Don't really want to drive the car (except for tuning) until I get the my VE tables in better shape.
Ray

 

Does the car run and drive?

what I’d do:

eliminate the ostrich.

try an old bin.

Datalog the car: Turn on the ignition key on engine OFF and test your sensors with the car off.

if any of these give you better results the fix is in one of these scenarios.

only then try to completely recreate the bin from the last one that worked. And only then add the ostrich back in.

 

A little progress on the problem. The original problem was that a was getting multiple data errors at the bottom of the tunerpro page and therefore not able to acquire data. Traced the fault to loose A8 (data wire from ECM going to ALDL connector) pin connection at the ECM. Wiggled the wiring near the 24 pin connector at the ECM and Tunerpro would connect/disconnect. Repaired Pin A8. Now it connects when I select "acquire data" BUT the data is frozen on the screen (temperatures indicate -40) and don't change. Another observation is that even with the ALDL cable disconnected from the ALDL connector but still connected at my laptop, then select "acquire data" Tunerpro would indicate connected. That is not normal. Also just noticed that I may have accidently operated the "enable/disable data tracing" button which is next to the "acquire data" button. Very difficult to tell which state that button is in and not sure if that has anything to do with this. I also removed power to my Wideband to see if that was maybe causing some kind of electrical interference issue but same results.

The answers below are AFTER the repairs to Pin A8.
Does the car run and drive? YES

what I’d do:

eliminate the ostrich. DID THAT REMOVED G1 BOARD, REINSTALLED ORIGINAL MEMCAL (AZTY). TURNED KEY ON ENGINE OFF AND DATA STILL FROZEN. REINSTALLED G1 BOARD AND EMULATOR.

try an old bin.
Datalog the car: Turn on the ignition key on engine OFF and test your sensors with the car off. INSTALLED A PREVIOUS REVISION OF BIN THAT WAS USED PRIOR TO THIS PROBLEM STARTING. DATA STILL FROZEN.

if any of these give you better results the fix is in one of these scenarios.

only then try to completely recreate the bin from the last one that worked. And only then add the ostrich back in.

I will be away from home for the next 10 days so I will not be able to perform any troubleshooting that you may suggest until after my return. Please continue replying with your suggestions and I will follow up when I return.
thanks again
Ray

 

I’d try a new aldl cable and/or usb port.

 

purchased new ALDL cable from Moates and tried different USB port same results. I have tried everything except different ECM. Tried fresh XDF, ADX from TP website as well same result.
Ray

 

I haven’t seen you say you’ve COMPLETELY uninstalled tunerpro and reinstalled.

did you?

That “connected” when not connected is a problem. But is it THE problem? That would eliminate the ecu as THE problem. the car running also makes me not suspect the ecu.

edit: connected when not actually connected also explains the stagnant 0 values.

 

I did uninstall and reinstalled the latest version of Tunerpro (V5.10305) a few weeks ago from the Tunerpro website. Could the data tracing feature available in TP create problems? I am not familiar with this feature but it's enable button is next to the "enable data" button and perhaps I accidently enabled it. Very difficult to tell if it's on or off.
Ray
EDIT: I will also remove/reinstall the FTDI drivers from all 3 of my USB ports rather than just the the one USB port that I was using for datalogging.

 

Don’t know if you saw my edit above:
connected when not actually connected also explains the stagnant 0 values.

(-40 c temp is a zero value.)

I don’t use data tracing. No idea. Turn it all off. Sounds to me like you have a tunerpro problem.

 

If you can set up a second laptop for testing purposes that could help determine if it's a computer config issue.