I was going to ask on Moates.net, as I just got this APU1, but I have a very hard time believing this problem has anything to do with his unit, so I thought it better to ask here. '165 running 6E.

I've read everything I could find, no luck.

One reason I purchased this was an issue I just started having, with an older APU1 I was given. It would only datalog when I got it. With that unit, it started out datalogging fine. Eventually datalogging started to "freeze" randomly, seemingly in shorter and shorter increments (last connect I was able to make was less than a minute) and finally got to the point where no connection to the ECM was possible. Two different ECM's, two different laptops/OS's (win2K and XP), two different EEPROM's, multiple tests with stock APYP and a modified APYP .bin. Using TunerPro RT. I figured with all that "testing", the problem was most likely the APU1. Vehicle runs/drives normally.

The new APU1 is exhibiting the same issue unfortunately...no ALDL connection can be made. However I am able to emulate, and make changes on the fly. While I can't SEE that the changes are working (because I can't datalog of course), increasing timing at idle does make a difference, so I am confident that it does work. Not sure how that would make a difference, but for lack of direction, I thought I'd include that.

Within Tunerpro when I boot it up, the cable settings are "good" (com3, max232) and the cable tests ok.

I tried following both the datalog only instructions, and the emulation/datalog instructions, but neither worked for me. Switching the 10K resistor (on both the old and new APU1) does affect the vehicle idle, so I know that much at least is working.

I saw this post: https://www.thirdgen.org/forums/diy-...-how-do-i.html where the issue turned out to be a bad ECM, but I followed the advice and focused on datalogging only, with no luck.

I did a continuity check on harness pin A8 of the ECM (data) to the ALDL, and it checked out. Both ends look like they are making contact with their respective pins.

Any ideas?

 

One thing i notice is you don't mention an ADS file. Are you using the correct ADS file in TP?

 

Sorry, yes to correct ADS. I've reinstalled TunerPro as well, just in case something was corrupted. Not likely I know, but after not finding an issue with the data wire to the ALDL connector, I can't think of much else that could be the problem.

 

im having the same problem with a brand new APU1. can connect but cant data log.

 

Did you follow Mark's (Mangus) instructions in the link I provided in my first post?

Just want to make sure we are actually having the same issue.

Wish I had a standalone cable to test with, but I have a very hard time believing two APU's that are far different in age, have the exact same issue.

 

yes as far as i can remember i followed the directions lol. i can however data log with WINALDL but not TP RT. sorry i forgot to mention that.

im going to go through everything with the directions in front of me and see what happens. maybe i missed something

 

Your cable also tests ok in TP?

I have not tried winALDL, again it seems odd I/we would have issues with Tunerpro with '165's that no one else appears to have had.

I went back to that thread because Mark specifically focused on connecting ALDL-only, and I wanted to make sure that I followed that to a T. I believe I have, yet still can't connect.

 

Here's a couple of things to check for reference:

1) Make sure, after your key has been of for 10+ seconds, that when you turn the key back on the SES light blinks once (on,off,on within 1 second). This indicates that the ECM is seeing a 'valid bin' at the socket (whether chip or emulation). If you don't see the blink, you have no hope to datalog.

2) For a 165 ECU, set the switch to the 10k position to allow communications via ALDL at 8192. If using an AutoProm, set both of the switches to the inside toward the USB port. Once communications are established, you can turn the 10k back to the open position if you like.

3) Check the settings in TunerPro under Tools/Preferences
- For V4, select "AutoProm" on the pulldown. If using passthrough mode or another cable type, select MAX232/2-Trans. You'll need to set your USB Serial Port settings (Windows Device Manager) and these settings to match COMx number. Not needed with APU1.
- For V5, same as above but select either AutoProm or TunerPro Data Acquisition Interface / Standard Serial. If you try and 'test cable', make sure it is disconnected from the ALDL port.

4) Check the ADS/ADX file selection and settings. Make sure you're using the correct mask ID for the bin you have loaded.

5) Key on, establish communication with hardware and try to 'Connect'.

These are some of the things people have run into in terms of confusion. If you need any one-on-one assistance, just get with me via email or phone and I can get you straight.

Hope this helps,
Craig

 

Craig, appreciate the reply!

I double checked what you posted, I had it all right apparently, and everything appeared to be working right. Left my ECM unplugged last night, plugged it back in, checked for the SES light blink, followed the same procedures, and I was emulating and datalogging with no problem. Tried only once as I didn't have much time, but as soon as I get another chance, I'll try a few times.

I somewhat suspect a loose or bad wire (since it's a retrofit) but I just hope it doesn't happen again.

 

Remember, too, that the 165 ECUs will often 'clam up' after a period of time (from 30 seconds to 30 minutes seemingly).

Turning the key off for 10 seconds will reset the condition and allow data to again flow freely.

There doesn't appear to be a 'fix' for this issue, but some 165 ECUs do it and some don't.

 

I've got a '165 service replacement that has another number, I also noticed that some of the chips on the board are different, while some are the same.

If I notice any differences in regard to ALDL with it vs. a "stock" '165, I'll post up.

Edit: No different with the Delphi service replacement. Still "clams up" at random times. Schucks. I will say that if I shut the vehicle down after a short test run/datalog analysis/PROM modification, I had no incidents of it locking up in 5-10 minutes of running, which I did with the original '165.