Noob in need... 94 Fleetwood LT1 95 K2500 Truck Transplant

[ReidB]

Hey guys,
This is my first attempt at a EFI swap. I'm a gearhead & electrical engineer but I am as noob as it gets with this stuff.
I've built a 2-transistor ALDL cable with a Prolific PL2303RA chipset. It checks good. I've downloaded TunerPro, #EE mask, and a LT1 bin file.
I can't get it to communicate. Pretty sure the problem is the driver, it won't allow 8192 baud. Apparently 9600 isn't close enough.
The motor fires, but VATS kills the moment. I don't have a VATS module to bypass, and I really don't want one, so I need to reset the flag.

A little more about my setup...
Its a 94 LT1 out of a Fleetwood. Supposedly has a Vette cam installed.
Everything on the motor is still there except EGR, air pump. Running truck logs into true duals. Only a single O2 installed at the moment.
Running the LT1 ECM for motor only. Running the truck ECM for trans functions. (Because the LT1 ECM won't accommodate shifts in 4low without mods.) Trans is a 95 4L60E.

I've read a sh!% ton of posts on this. I'm beyond frustrated. I have LOTS more questions, but I'll start here.
Thank you in advance!

[dave w]

If you post your .bin file, I will disable VATS.

dave w

[ReidB]

Thanks Dave. I appreciate any help I can get.
This may be a stupid question but why does tunerpro require uploading a bin before connecting? Seems like the safest way would be downloading the factory bin from the ecm. Or am I missing something?

[dave w]

TunerPro RT does not need the .bin loaded to connect.

TunerPro RT needs the com ports correctly configured.
TunerRro RT needs the correct .adx file loaded.
I also set the file associations to .bin / .xdl / .adx (this might not be needed?)

dave w

[steveo]

that chipset is weird, man. get an ftdi one and itll do weird baud rates. try my eehack software and eex definition in my sig. im sure it'll work. no transistors or anything with an ftdi chip, just tie rx and tx together. hard wire and build 'er into your dash so your truck has usb instead of an aldl port

tunerpro does not download or upload bins for your flash based ecm. only edits. you need tunercat, winflash, or eehack for that.

[ReidB]

Thanks Steveo,
I've ordered a 6 pin ftdi ft232 to ttl rs232 Arduino cable off ebay. Hope it works. It cost a whopping 7.50. An awesome deal if it works.

[steveo]

yep, i have several of them, they work fine.

[ReidB]

Great to hear. I built my cable to save time.
I hope it all makes more sense once I get access.
Thanks for your input!

[ReidB]

well, got the cable. I cant get it to communicate. The driver loads and says the cable is good. Baud of the com port is 9600.
I can't get TP or EE hack to connect. Rx, Tx and Serial Data tied together. Ground of cable and PCM tied together. Does it matter which ground pin on the PCM? Tried with and without a 10K resistor between ground and service enable. The fuel pump runs with the resistor. Any insight? TY!

[steveo]

Does it matter which ground pin on the PCM? Tried with and without a 10K resistor between ground and service enable. The fuel pump runs with the resistor.

service enable isn't what you want. this ecm doesn't work like that. you need to use a common chassis ground for the aldl, don't use a filtered sensor ground

Baud of the com port is 9600.

nah, that's just the default baud rate. the software still gets to choose its own. it requires 8192 baud.

can you post a section of verbose debug log from eehack trying to connect?

[ReidB]

Loading Definition DEVICE=0xF4 MSG=0x0Loading Definition DEVICE=0xF4 MSG=0x1
Loading Definition DEVICE=0xF4 MSG=0x2
Loading Definition DEVICE=0xF4 MSG=0x3
Loading Definition DEVICE=0xF4 MSG=0x4
Loading Definition DEVICE=0xF4 MSG=0x5
Loading Definition DEVICE=0xF4 MSG=0x6
Loading Definition DEVICE=0xE4 MSG=0x0
Loaded 1014 elements into 8 definitions.
Using monotonic reference clock.
EEHack Version 4.60
Current OS : Windows 10
Built with THROTTLE_MS=2
Opened serial port COM3 Description USB Serial Port MFR FTDI
START SILENCE ROUTINE
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
WRITE ERROR write could not be completed!
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f4
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
SHUTUP DEVICE f9
[SERIAL WRITE]*F95608A9
WRITE ERROR write could not be completed!
DATASTREAM: Send MODE8 keepalive*F95608A9
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f1
[SERIAL WRITE]*F15608B1
WRITE ERROR write could not be completed!
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f4
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
SHUTUP DEVICE f9
[SERIAL WRITE]*F95608A9
WRITE ERROR write could not be completed!
DATASTREAM: Send MODE8 keepalive*F95608A9
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f1
[SERIAL WRITE]*F15608B1
WRITE ERROR write could not be completed!
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f4
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
SHUTUP DEVICE f9
[SERIAL WRITE]*F95608A9
WRITE ERROR write could not be completed!
DATASTREAM: Send MODE8 keepalive*F95608A9
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f1
[SERIAL WRITE]*F15608B1
WRITE ERROR write could not be completed!
Listening 2000ms for broadcast heartbeat...
Timeout waiting for heartbeat after: 2000ms
SHUTUP DEVICE f4
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
SHUTUP DEVICE f9
[SERIAL WRITE]*F95608A9
WRITE ERROR write could not be completed!
DATASTREAM: Send MODE8 keepalive*F95608A9
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
[SERIAL WRITE]*F45608AE
WRITE ERROR write could not be completed!
START SILENCE ROUTINE
Listening 2000ms for broadcast heartbeat...

[ReidB]

just pasted and sent verbose debug...

[steveo]

"WRITE ERROR write could not be completed!"

a rare error. bad usb cable, bad driver, wrong serial port selected, defective interface.

[ReidB]

Rare error... just my luck. Can vats block communications with the ECM? I just disconnected the battery, reset the ECM and finally got TunerPro to connect the ALDL. Fired up EEhack and no such luck. Different errors this time. Ran out of time, hopefully better luck tomorrow.

[steveo]

Can vats block communications with the ECM?

not in my experience