new $EE tuning thing!

[Casey96SS]

aldl interfaces run in a state of loopback. the recieving and sending line are the same wire. datamaster doesn't really care if the echoed data is corrupted. eehack does.

but none of this stuff is driver level

also i bet datamaster is giving you a bunch of bunk data

Hey Steve finally had a chance to get my car back together and do a little data logging yesterday with the wideband disconnected. The ABS Inop and Low Trac lights seems to be turning on occasionally while logging. If I look at the graphs in EEHack while this is happening there is a flat spot on any of the data and I cannot double click in the flat area. The lights do not come on if I do not have the laptop hooked up. Hope this makes sense. Any idea what is going on? Thanks!

[steveo]

Hey Steve finally had a chance to get my car back together and do a little data logging yesterday with the wideband disconnected. The ABS Inop and Low Trac lights seems to be turning on occasionally while logging. If I look at the graphs in EEHack while this is happening there is a flat spot on any of the data and I cannot double click in the flat area. The lights do not come on if I do not have the laptop hooked up. Hope this makes sense. Any idea what is going on? Thanks!

for your obd-i conversion, make sure only your ecm is connected to the aldl data wire.. sounds like your ABS module is hooked up there; it would be incompatible with the older data

[Casey96SS]

for your obd-i conversion, make sure only your ecm is connected to the aldl data wire.. sounds like your ABS module is hooked up there; it would be incompatible with the older data

It looks like my Red Devil River Cable is reading on Pin 9 which would be Serial Data (UART). (See Pic)

Car is a 1996 with the OBD-II ALDL connector. I converted over to an OBD-I with the correct knock module.

Should be reading off Pin 2 Serial Data (Class II)?

Does that sound right before I get the soldering iron out? Also do you see any issues with the resistor they have installed on there? Thanks!

[Casey96SS]

It looks like my Red Devil River Cable is reading on Pin 9 which would be Serial Data (UART). (See Pic)

Car is a 1996 with the OBD-II ALDL connector. I converted over to an OBD-I with the correct knock module.

Should be reading off Pin 2 Serial Data (Class II)?

Does that sound right before I get the soldering iron out? Also do you see any issues with the resistor they have installed on there? Thanks!

I got it figured out after searching the net and looking at the wiring diagrams in my FSM.

Swapped #2 and #9 wires on the ALDL connector

Swapped #7 and #30 wires on the blue PCM connector

This basically eliminated the EBCM wiring from the ALDL data wire.

It logs just fine now. I wish that would have help my wideband issue, but no luck there.

[steveo]

right on, glad you got it working

[Casey96SS]

I got it figured out after searching the net and looking at the wiring diagrams in my FSM.

Swapped #2 and #9 wires on the ALDL connector

Swapped #7 and #30 wires on the blue PCM connector

This basically eliminated the EBCM wiring from the ALDL data wire.

It logs just fine now. I wish that would have help my wideband issue, but no luck there.

It starting to look like my 96 F body with an OBDI PCM is wanting to be a real bastard to log and tune. I previously switched my tan and purple wires from my ALDL to PCM so that it would take the EBCM off the ALDL wire and stop creating dead spots in my logs and tripping the ABS light. This did the trick when logging.

I went to load a new bin file this weekend for some larger injectors and could not get the bin to load. I tried EEhack and Winflash and neither would work. I could read fine but not write. I switched my purple and tan wires back to the factory locations and both programs write just fine.

With the ALDL wires back in their factory locations, I tried switching off the setting for "Silence Extra Modules". This seemed to prevent the ABS light from coming on while logging, but is still looking like I was getting dead spots in the data stream.

Would there be any extra or different modules that need to be silenced on a 96 F body to stop them from interfering with the data stream? Would it be possible to just pull the fuse or relay for the EBCM while logging to avoid the interference? Just looking for ideas....

I think my only other option would be to swap the ALDL wires back so I can log correctly and then build a bench harness if possible to load bin files. This is definitely getting frustrating! It would be great to be able to use this awesome software to it's full potential on my car.

[steveo]

all that matters is PIN 9 at the ALDL connector (bottom left corner). your aldl cable only uses that one pin (and a ground).

ensure it is connected to D30 @ your ECM (blue 30), this is usually a tan wire. trace that tan wire and make sure nothing else is spliced into it.

i usually run a fresh wire for it to ensure data integrity.

disconnect D7 at the ECM (purple wire), it's not needed, but that way you can still use OBD-II diagnostic tools to read codes from your ABS module and whatever else at your ALDL.

[Casey96SS]

all that matters is PIN 9 at the ALDL connector (bottom left corner). your aldl cable only uses that one pin (and a ground).

ensure it is connected to D30 @ your ECM (blue 30), this is usually a tan wire. trace that tan wire and make sure nothing else is spliced into it.

i usually run a fresh wire for it to ensure data integrity.

disconnect D7 at the ECM (purple wire), it's not needed, but that way you can still use OBD-II diagnostic tools to read codes from your ABS module and whatever else at your ALDL.

Cool! I will run a new wire directly from ALDL Pin 9 to ECM D30. I did not think of that. I know the EBCM is wired into the tan wire on my car based on the wiring diagram in the FSM. I believe that is what is causing my logging issues.

Do you happen to know if the pins on the ALDL and ECM side are something you can easily buy? I have been trying to avoid cutting into my factory wiring. It would be nice to just throw new pins on the new wire and plug them into their correct places.

Also, would leaving the purple D7 pin hooked up to the ECM cause any problems? That's the way it came from the factory on my car. Thanks for the help!

[Casey96SS]

all that matters is PIN 9 at the ALDL connector (bottom left corner). your aldl cable only uses that one pin (and a ground).

ensure it is connected to D30 @ your ECM (blue 30), this is usually a tan wire. trace that tan wire and make sure nothing else is spliced into it.

i usually run a fresh wire for it to ensure data integrity.

disconnect D7 at the ECM (purple wire), it's not needed, but that way you can still use OBD-II diagnostic tools to read codes from your ABS module and whatever else at your ALDL.

So I ran a new 20-ga TXL wire from my ALDL pin 9 directly to my ECM pin D30. I crimped and soldered a new pin and terminal to the ends of the wire. EFI Connection is a great place for these things! I also disconnected D7 from the ECM. I believe I should have a good ALDL connection to the ECM.

Unfortunately I am still getting random dead spots in my logs and am not able to flash. EEhack makes it to about step 4 or 5 of the programming stability test and then fails. The really weird thing is that I was able to flash when I had the factory tan ALDL wire in place. Maybe that was a fluke? I am able to read the bin with Winflash but did not try writing anything out of fear of bricking the ECM.

Could this be related to the cable? I am using this one from Red Devil River. http://www.reddevilriver.com/aldl.html I took the adapter end apart and there is a resistor in the wiring in there. Would this have something to do with why I can flash when the factory tan ALDL wire is in place?

Is there a better cable I should be using? I have tried two different laptops with no difference.

Thanks for any help! I am stumped!