new $EE tuning thing!

[steveo]

What would be the best way to troubleshoot the #4 and 5 grounds on the ALDL connector? Does the cable rely on both of those or just one of them? Would it be worth trying to run a temp ground wire from 4 or 5 or both to the ground stud under the hood? Sorry for my ignorance in all of this. Definitely learning a lot!

worth a shot

the cable only uses one of them but i forget which

[Casey96SS]

worth a shot

the cable only uses one of them but i forget which

Well running the new ground wires directly from ALDL pins 4 and 5 to the ground post on the inner fender changed nothing. I did find that the ground stud was loose where it bolts to the fender but even tightening that did not help.

I did some more research on the RDR cable I am using. Looks like I got one with a fake FT232RL chip. The letters on the chip appear to be printed on instead of laser etched. http://hackaday.com/2014/02/19/ft232rl-real-or-fake/

I went ahead and ordered a Moates cable. Hopefully that solves my problem.

I almost feels like it was easier removing and rebuilding the engine by myself than it has been to log and tune this damn car!

[Casey96SS]

Well running the new ground wires directly from ALDL pins 4 and 5 to the ground post on the inner fender changed nothing. I did find that the ground stud was loose where it bolts to the fender but even tightening that did not help.

I did some more research on the RDR cable I am using. Looks like I got one with a fake FT232RL chip. The letters on the chip appear to be printed on instead of laser etched. http://hackaday.com/2014/02/19/ft232rl-real-or-fake/

I went ahead and ordered a Moates cable. Hopefully that solves my problem.

I almost feels like it was easier removing and rebuilding the engine by myself than it has been to log and tune this damn car!

Major victory today! It looks like all of the issues I was having were due to the Red Devil River cable and the fake FT232RL chip. The Moates cable I ordered works perfectly. No dead spots while logging and no errors with the programming stability test. I did not try flashing anything yet, but I am assuming it should work without a problem. Best of all my AEM wideband now works with EEHack!

I sure spent a lot of time messing around with this just to find out an $80 cable was the problem. I guess at least I now have a nice clean wire for my ALDL data in my car and I also wired the wideband data directly to the ECM D27 pin while it was apart. Looking forward to working on the tune for this thing! (maybe)

[steveo]

i'm always hesitant to blame the cable in these cases (since if it ends up being my code's fault then i feel bad), and i do get a lot of them

... but it's always the cable

... 'cause my code is never bad

in reality, my software doesn't interact with the serial port directly, it uses QT's serial port abstraction layer, written by real programmers, not hacks like me. so there'd have to be a bug in that, or a bug in the usb/serial driver. otherwise every user would be affected.

this does help too, as the serial driver usually defaults to high latency, not so good for our purposes: http://fbodytech.com/ftdi-serial-lat...readed-eehack/

another aldl problem i've seen involves people powering their laptops from their car's cigarette lighter. you can end up with weird ground faults if your power supply sucks. try running off of battery power (so the only ground to your car is through the aldl port)

[Aroberson77]

Is anyone else having issues downloading Steve's programs?

[kur4o]

I finally managed to test the program on running engine and it is amazing.
The connection is really stable.
You can actually data log during cranking, just like the gm oem tool.

A big thanks to Steveo for all the hard work.

[steveo]

I finally managed to test the program on running engine and it is amazing.
The connection is really stable.
You can actually data log during cranking, just like the gm oem tool.

A big thanks to Steveo for all the hard work.

couldn't have done it without you