OK had to make the title a bit unique. Most of my problems tend to be. I really do dislike posting this, as I know the "can't datalog" problem comes up a bunch.

Setup is 1227165 (or whatever the Delphi 1227165 replacement is, that's my spare) w/slightly modified APYP. Vehicle runs great. (well, great but not ideal, thus datalogging!)

Laptop is a Dell 600, running Win2K, minimal amount of programs installed.

Cable is one I got off an acquaintance online...two transistor, serial, circuit card is encased in some kind of clear silicone (it appears) as is the wiring going to the serial connector, if that helps narrow down the cable maker. It is powered from the serial port. I built an 8192 cable myself before, but had no luck getting that to work years previous...I was hoping to eliminate myself as the problem with this, as the price was right. FYI, he never could get it to work either, but was trying with TBI.

I fired everything up the first time, ecstatic that I was seeing 8192 data right off the bat. All numbers appeared correct...coolant temp, batt. voltage, TPS, etc.

Watching the time connected, around 880 seconds the time showing how long I was connected started to "miss" seconds...then more seconds...finally all data just stopped changing, including the seconds. Never said I lost connection or anything, just no more data. I had created a log file, and saved it, however on opening, it was empty other than the headings. I killed everything (rebooted, vehicle off, etc) tried to start over...no link with the ECM.

At this point I've tried essentially everything I could think of/find in researching. Even talked to a helpful member via PM, everything in the COM port settings appear normal.

What I've done: swapped ECM's. Swapped PROM's/bins (both stock and ones I've burned). Swapped PROM's between ECM's.

Engine runs fine at all times with above changes, except with the "AKFR" PROM I have, as the fan runs constantly. But since I didn't modify anything in the bin, I expect thats just a setting. No check engine light. (light does work)

Checked the ALDL ground pin to chassis. Good. Tried using pin E or M for data to ensure it wasn't an ALDL pin or wire issue. E/M are spliced together in my setup.

I tried datalogging at 160 baud, seemed to work (got data file, but it was all junk, what I expected).

I tried wiggling/putting pressure on the wire connections of the cable, but the laptop/cable wasn't moved while it was initially connected, other than normal vibration from the engine. (laptop was on the drivers seat)

I added the 32b .ecu (matches the AKFR bin) to Tunerpro, and tried datalogging at 160...even on the tunerpro dash the numbers bounced around creatively, obviously inaccurate. Trying to record I got the "error trying to create log file" but after more research it appears that's just because I didn't specify a log.

I've reinstalled tunerpro, and downloaded/tried a different 6E .ads.

I played around with the settings under COM1 (in device manager) but nothing changed my connect issue.

Some things I noticed:

When I was hooked up initially at 8192, I never pulled the resistor, and the vehicle went to "curb idle" at around 750RPM as it warmed up. (I didn't mess with the ALDL spark setting) I thought it should have stayed at 1000RPM? Also it doesn't go to/stay at 1000RPM with the (assuming) stock APYP off of tunerpro and the cable hooked up, with the resistor in place. Thought it should do that regardless of a link with the tuning program?

Under preferences in TPRT, I tried checking the cable. RARELY the cable will test good, but if it does, sometimes it's on COM1, sometimes on COM3. If I "apply/ok" after getting a good cable test, and try to connect, still nothing. Under device manager, COM ports 4-7 are in use if it matters. I have nothing external hooked up to the laptop, although the removable DVD player is a device I suppose.

Since it connected initially, then gradually "faded out", I can't figure out what would have changed. Even internal or external power I wouldn't *think* would make a difference, since it worked at first.(?) I really can't afford another cable, and this WAS supposed to save me time that I need to be working on other things (like electricity in the garage!), so I'd rather not try again to build another cable, unless experience tells you guys it's a cable issue. I have no idea how to check this cables components since the card is encased.

At this point I can go in and reinstall Win2K and TunerPro RT only, and see if that makes a difference. I'm not techie inclined, but the COM port changing seems a bit odd to me, only thing I can think of to eliminate any potential issues there is to remove anything that might be using them?

Any advice? Am I missing something blatantly obvious anyone? Thanks!

edit: sorry for the long post, hoping that if I put everything out at once that I can think of, there will be less people have to ask of me. Even if you are stumped I'd appreciate a response, let me know if I'm crazy or not.

 

Thanks for the detail. Some notes:

- If you're running 8192, use 8192. Don't worry about 160. Your cable can do both.

- Make sure you have the 10k in place between A & B on the ALDL port.

- The "error creating log file" is because you didn't specify a filename before hitting the record button.

- Older builds of TunerPro had problems with the test cable functionality. I believe I fixed that in the latest build that's up there.

- 1227165s are known for losing ALDL connectivity after anywhere from a few seconds to a few hours (to never). Perhaps you're suffering from that issue? Powering down the ECM (key off for 15 seconds or so) then powering up should get you going again. At least until it chokes up again. The reman that I use so far has not exhibited this problem at all. Knock on wood.

- Your cable requires a 12v power supply, doesn't it? Have you verified?

If all else fails, we can meet up and get it going. I'm about 15 minutes north of you.

 

Magnus, I appreciate everything!

OK, I'll stick with 8192...thought if I got SOMETHING on 160 it might give an indication of the cable.

10K resistor is there at all times, checked with my multimeter that it's good. (brand new pack of 5)

Error creating log file, got it. I think I can put that aside anyways, since I'm not getting any data that I see.

I'm using the latest build? 4.14.0381

Since the cable DOES test good sometimes(ok, very rarely), I think the cable function testing is working right. Does the cable need to be hooked up to the ECM with the ECM on, for the test to work? I didn't test many times with the cable connected to just the laptop, but it never worked that way when I did.

The 1227165 that is in the vehicle is the one I initially connected on. The Delphi replacement (it's got a long part number) won't give me data either. I've swapped back and forth multiple times, so I've probably got 40+ connect attempts on each ECM if that matters. It's gotten "cooldown" time between many of my connect attempts as I swap PROM's or go in the house to download something different, read up on the problem, etc.

This cable doesn't have provisions for external power...I was wondering about that. It's got four wires to the serial connector when it only needs three, so I would suspect thats what the additional one is for. I've read experiences that say power from the serial connector pins is not a given. I could cut what must be the "power" wire and provide external 12V if you think it's worth it. At this point I'm not averse to it, it's the only thing I "know" isn't a given with this cable setup.

 

If it's using four pins on the serial line, then it's getting power via the serial bus (Rx, Tx, Gnd, VCC). This is fine. TunerPro does set the power lines high as needed.

And you're sure the car's not in limp home mode? If it is, you won't get any ALDL data.

I'm not sure what else it could be.

-Mark

 

Check engine light comes on with key on, engine off, goes out once engine starts. Runs/drives fine, mileage is consistent and no better/worse than expected from the start. I think I've got my old autoxray around somewhere, I could dig it out, but I'm darn certain it's not in limp mode.

IIRC on 6E if it is, the fan comes on constantly as one indicator, mines not.

Should I rule out the computer, or just reformat and try again from scratch? It's not going to kill me to reinstall, if it's a possibility there is a COM port or OS issue.

 

Don't bother with a reformat. I don't suspect it's your computer. I'm more suspicious of your interface cable. Pull out the Autoxray and see if that works. That will rule out the ECM and the ALDL connector/wiring.

Worst case you and I could perhaps meet some place this weekend and get it working. (I'm in Bothell/Lynnwood).

 

Turned out to be his interface (2-transistor type). Unreliable/slow data. He's all set to go now.

 

I hope it didn't come across that I suspected TunerPro as being the potential issue! I suspected it had to be something on this users end.

Thank you for being so generous with your time, knowledge, and equipment. I am greatly appreciative that I can FINALLY start datalogging! I only wish I could adequately return the favor.

If anyone doubted it, Mark is a great person.

I'll get right on registering my copy of TunerPro!

 

I know you've got this sorted now but I've got a Dell 600 as well and it WILL NOT connect to the ALDL without being powered by the inverter. If i loose the inverter while driving the datarate slows to a minimal effort and then stops.

I would guess that this is to do with the power supply to the USB ports? might be another thing to just keep an eye on.

Dan

 

That's a more common issue. Some computers just don't supply enough power to the power on battery power. There are a couple of similar posts in this forum on that problem. You've pretty much found the solution, unfortunately.

 

My data loss happens when I am changing bin settings, I think. The last time this happened I believe I was changing L4D8A. However, I don't lose everything, I still have MAP volts, Batt volts, O2 volts. Tried a couple of reboot/PCM reset/procedures but can't identify which action brings all ALDL datastream back. Anyone ever seen anything like this? Thanks all