Tonight I installed yet another 165 ECM (neither my ALDL1 nor my Auto X-Ray can reliably communicate with my other 2), and was actually able to get my Auto X-Ray to communicate with it on the 4th or 5th try, so I tried using the Moates ALDL1. I've been unable to get it to connect to my other 2 165 ECMs, but I bought this from a person who sucessfully datalogged with a TTS Datamaster. In any case, with the ALDL1 switch set to the 10k position, it will establish a connection, but then the "connected" bar at the bottom of Tunerpro RT starts flashing " data error" very quickly. The data on the dashboard continues to toggle back and forth between valid data and invalid data. This process continues indefinitely every time I connect.

Does anybody have any suggestions? I've verified the COM port number, and clicking on the "Test For Valid Interface Using Settings" button within the TunerPro preferences section verifies that it can communicate with the ALDL1.

Thanks

 

I understand, it is very frustrating. I have had the same "data error" with TP5. The only suggestion i have is to keep trying. Make sure your ALDL1 is plugged in when you start TP. Also, may have to restart the computer, and try it. Keep working the 10k switch and re-connect. There have been many posts on this issue with connecting with a 165 ECM.
Good luck.

 

This is a stupid question but have you tried deleting / reloading the ALDL driver on your computer? Tried using different programs like Tunerpro and what not? Tried assigning a new com port to the serial connector cable?
Are you able to datalog on your other car just fine? Sounds like its time to play the process of elimination game haha which you have done with your 165's.
Also another suggestion, make sure you hooked all your grounds back up after the engine work? I'm just spitting out ideas...

 

Grounds are something that keeps making me wonder. I did hook everything back up, but I'm going to do a resistance check between the ECM and the battery to see how it looks. I may run a wire directly from the ECM case to the battery to see if it makes a difference. This just reeks of a ground problem to me.

 

Some more food for thought. I bought a one wire altenator from summit racing and developed connection problems and random voltage spikes. While i had it removed to return to summit i decided to pull the altenator apart. I found the mounting bolts for the rectifier and voltage regulator were loose. Put everything back together and all was was fine.

 

any luck on finding the problem Jim?

 

Jim, I’ve had the same problem you’re experiencing. After a wiring harness re-do, I can’t get it to connect with the car running. However, it will connect with the key “on” and engine “off”. Have you tried doing this?

I was also told by Moates, it could be a grounding issue. I re-traced and re-connected all my ECM, chassis & engine grounds. I even did what you mentioned and isolated my ECM grounds straight to the battery negative, and it hasn’t made a difference. I also tried disconnecting my alternator output, to eliminate “engine noise”, it didn’t make a difference either.

However I did notice something interesting: When I locate my correct COM port and click “test for ALDL cable”, it finds the cable. However, when I click “connect” with the key “on” engine “off”, it connects. But when I go to the preferences to check the cable (while still connected) it can’t find the cable while it’s actually dataloging. I can’t seem to figure it out!!

See my thread here: https://www.thirdgen.org/forums/diy-...on-issues.html

I’m wondering if it’s my ECM or my Moates equipment. My wiring seems to be spot on.

I’ve read about your frustration, so let me know what you came up with. Thanks.

 

Have you condidered contacting Magnus directly?

 

Who's Magnus?

 

Inventor of TP-RT

 

Ahhh...is he Mark Mansur? I could really use his contact info!!

 

He is a member here or google tunerpro for contact info....

 

I just sent him an email about our problems. I linked this thread.....Thanks for your help.

 

Mark Mansur responded to my email, here's the response:

Hi Stacen,

I’m not sure what frustration it is you read about. There are well-known intermittent connection issues with ‘165’s, but that doesn’t sounds like the problem you’re experiencing. If it consistently will not hook up with the engine running, and you’re confident that your grounds are good, I’d start looking at your ignition system and related grounds. If it’s stock, it could be failing or arcing, and if it’s aftermarket, it could be noisy. The difference between engine running and not running is likely to come down to signal noise.

The test for ALDL cable issue is likely a red herring – when TunerPro already has the port open, you won’t be able to use the test button. Also, you should only use that button when the cable is disconnected from the vehicle, since 160-baud chatter may cause false negatives (the cable is present, but the test fails).

-Mark

 

I haven't even bothered trying the datalogging with the car running. Every one of my failures has been with the key on and engine off.

Unfortunately, I've made no progress on this. The car is out of the garage, stuffed in an unheated carport for the winter. I do still have access to the car though, so if I have some sort of epiphany, I can give something a try, but most likely I won't touch it until spring.

 

I hear ya, sounds good.