Yes, I have done that procedure. I did have change to signals to be inverted, as they were not checked, as well as the D2XX driver... everything is as shown on the manual FTDI setup
Yes, I have done that procedure. I did have change to signals to be inverted, as they were not checked, as well as the D2XX driver... everything is as shown on the manual FTDI setup
I know this sounds like I'm beating a dead horse, but you did hit 'program' from the drop-down menu after changing the settings in FT Prog? Otherwise, the changes don't save to the cable.Originally Posted by goodling
mpt2coms.txt file
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Correct, I did hit program to save the changes, I understand its a process of elimination to determine the cause, and I appreciate your help.
Here is the mpt2coms file...
-Comport analysis for mptune version 2.0.4.2
-Locating ports on computer-
name:USB Serial Port (COM7) deviceid:FTDIBUS\VID_0403+PID_6001+A5YOXR28A\0000
number of ftdi devices found - 1
ftdi port num:COM7 serial num:A5YOXR28
Inverted tx:True Inverted rx:True
Latency is set to:2
checking to see if usb port number COM7 is a moates device
Moates device not located on this port
default com port set to:COM7
thx. everything i see looks good. it finds the ftdi port on com7 and the tx/rx are inverted. should work!?!? the program sends the bytes, just nothing comes back! it's like the chip isn't receiving any data. wonder if the diagnostic connector data line is bad..
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Yeah, all looks right to me.
Maybe check continuity from the Rx and Tx at the SCI connector back to the SMEC? Check the ground, too. If its bad, it can affect the coms.
It's not downloading the boot program, so the communications link is broken somewhere.
you mentioned earlier that the snap on tool works so i assume you are using the same diag connector port for both. if so that would seem to indicate that the tx line on the ftdi cable isn't connected somehow (maybe..........)
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Yes, the snap on verus worked, same port yes.... However power and ground to power the tool is supplied from the battery via alligator clips, so the ground is a possibility.... I'll print a wiring diagram tomorrow and check the wires.. I have a labscope, is their a signal I could look for on the tx/rx lines, just to get a idea if their working? Usually a squarewave I see on newer stuff data lines.
rob L would be a better help on the scope side of things. when you apply boot power to the smec and then turn the key the ecu should transmit a null (0x00) back to the pc. then the pc will send the boot program down the receive line of the ecu, so you should see bytes being sent to the ecu which also echos the bytes back to the pc.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
It would be a square wave. If your scope has a logic analyzer function, you should be able to see the bytes sent and received.
Ok, Checked all the wires from the diag connector to the ecm, all wires are good, the ground wire is good, solid ground.
I back probed the diag connector with the labscope, the light green wire (ecm pin 31, data in) reads 2.5 volts, then when I try to read the chip, it goes to 5 volts in a super fast squarewave for apprx 330 ms, then back to 2.5
The pink wire (ecm pin 51 data out), reads 0 volts at all times, as does the ground signal.
Any ideas????
So, you can see the data transmitted by the PC over the USB-SCI cable. But, either the ECU is not able to transmit it back; or it never receives the data in the first place. My guess is the 2nd one.
My main concern is; the 'idle' voltage for both the Rx and Tx lines should be 0v. The 2.5v idle on the SCI-Tx line is a concern. It really should never read 2.5v.
On the USB connector; there should be a USB symbol on one side, and a voltage rating on the other. Does it say 5v or 3.3v? It should be 5v. Sometimes, my supplier sends me the wrong ones. I usually catch them, but you never know.
Yeah, it says 5 volts.
OK. Can you snap a pic of the SCI end of the cable? I want to see if I can tell which board version it's using.
Yeah pm me your email address, I'll send it right to you.
Is it possible this still used the 87 electronics and has a logic module and that's causing the connection issues?
Just throwing something out there that stuck in my head while reading this.
It's an 88 and it's smec its my old car.
Ok, figured I'd double check as it was made in the month that model years change.
any progress?
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
No, I was outa state for a few days doing some military training. Gonna get back on it. Sending cable pics to rob now..
Maybe try this whole set up on another laptop....
Still wondering about the 2.5 v that shouldn't be their, i'll check and see whats feeding it, the laptop or ecm
Any other suggestions?
Posting Permissions
Reply With Quote