CLASS: Getting MPSCAN to talk to the Chrylser ECU

[mratliff86]

Okay, so my swag came in today, the SCI cable, latchboard, and some chips. Thanks Rob, everything looks great. I am now ready to begin logging, I have connected to the car and everything appears okay. I am now at a point where I could use some help in actually logging and trying the different tests. I tried some of the sensor tests, and the outputs seemed good. I couldn't tell with the actuator tests. How exactly do I go about datalogging?

[wowzer]

couple things -

1) watch the videos posted in post #1 of the mpscan sticky http://www.turbo-mopar.com/forums/sh...l=1#post641180 and browse thru some of the comments there.
2) the sensor tests and actuator tests have never been tested by me on a car, only marginally using a simulator, so i cannot vouch for their accuracy/completeness. it was always the datalogging first and then "some day" i'll get to the sensor/actuator stuff.

[mratliff86]

couple things -

1) watch the videos posted in post #1 of the mpscan sticky http://www.turbo-mopar.com/forums/sh...l=1#post641180 and browse thru some of the comments there.
2) the sensor tests and actuator tests have never been tested by me on a car, only marginally using a simulator, so i cannot vouch for their accuracy/completeness. it was always the datalogging first and then "some day" i'll get to the sensor/actuator stuff.

Thanks, those videos are excellent. I got my dashboard all set up in MPScan last night and plan to begin doing some logging tonight.

[wowzer]

good job - have fun.

[mratliff86]

Success, everything was spot on with the videos. The cable setup on the wiki was great.

[ShelGame]

Is there a need (or desire) to convert the content in the how-to videos to a text+picture format for the wiki?

[spooling]

Shelgame- I think text+ pictures would be helpful for newcomers, my opinion.

So I'm using
Dell lattitude laptop with windows7
BoostButton cable.
I have Mptune and Mpscan downloaded.
I've tried connecting to my SBEC in Mpscan, no luck.

Is their a "connecting to ecu for dummies" that I missed?
This is all new for me, any help is appreciated.

[spooling]

ahh, I had to once again set up the cable as a COM port hmm. Anyway it finally works, but neighbors probably think i'm crazy toying with my car at 2am. Going to try to log tomorrow, all I did was actuator tests.

[ShelGame]

ahh, I had to once again set up the cable as a COM port hmm. Anyway it finally works, but neighbors probably think i'm crazy toying with my car at 2am. Going to try to log tomorrow, all I did was actuator tests.

Yes, that's in the wiki. I should add to the wiki that you'll have to do that for every PC you'll plug it into. Its a windows thing, not a cable thing.

[krut]

Is there videos or documentation to set up the wideband logging?

[ShelGame]

Is there videos or documentation to set up the wideband logging?

Not yet. That will probably be the first one of the 'Turbonator' features I document for the wiki. I just need time with my PC to write it and snap some screenshots. For now, I think you'll have to go thru the T/SMEC thread and find the posts where we talked about setting it up.

[krut]

Generally speaking, you set it up in turbonator, and feed the 0-5v uego value to the ECM, right? The cal will convert it to the narrowband values needed to go into closed loop, but MPScan will read the values of the wideband off of the o2 PID? (As long as you provide the scale for the sensor)

I'm trying to figure out how to get it to work without a car to test it on unfortunately. That's why I was hoping there was some documentation floating around out there so I know exactly what to do once I get the chance to test it out.

[ShelGame]

Generally speaking, you set it up in turbonator, and feed the 0-5v uego value to the ECM, right? The cal will convert it to the narrowband values needed to go into closed loop, but MPScan will read the values of the wideband off of the o2 PID? (As long as you provide the scale for the sensor)

I'm trying to figure out how to get it to work without a car to test it on unfortunately. That's why I was hoping there was some documentation floating around out there so I know exactly what to do once I get the chance to test it out.

Basically, yes. There's a transfer function in the cal; you need to make sure it matches your WB output. Its then used to convert to the NB signal.

[ShelGame]

It's been a while. Any feedback on the wiki? What needs to be updated next?

[1986GLH]

So I have used the Wiki to set up my laptop to recognize the FTDI cable and boost button SCI. MPScan says in the bottom left corner that it recognizes it, but when I plug the SCI in and start the car, the gauges on my dashboard don't do anything and it does not allow me to log. It says unable to open/setup port. Try turning key off and then back on. I went through the Wiki and followed the directions with FT_Prog and everything. I'm at a loss. Any help would be appreciated.

[wowzer]

post up the text of these two files: mpscanport.txt and mpt2coms.txt. if you are on win7 or later should be in the c:\users\"username"\appdata\roaming\mpscan directory. what ecu type are you trying to log?

[ShelGame]

So I have used the Wiki to set up my laptop to recognize the FTDI cable and boost button SCI. MPScan says in the bottom left corner that it recognizes it, but when I plug the SCI in and start the car, the gauges on my dashboard don't do anything and it does not allow me to log. It says unable to open/setup port. Try turning key off and then back on. I went through the Wiki and followed the directions with FT_Prog and everything. I'm at a loss. Any help would be appreciated.

MP Scan doesn't have a separate 'display' mode. It only shows data when it's recording. You're opening the 'profile' you setup for your car, right? and not just the logging screen?

[1986GLH]

post up the text of these two files: mpscanport.txt and mpt2coms.txt. if you are on win7 or later should be in the c:\users\"username"\appdata\roaming\mpscan directory. what ecu type are you trying to log?

The ecu that I'm trying to log is a T1 SMEC.

This is the text from mpscanport.txt:
mpscan ver - 2.0.2.4
Microsoft Windows 7 Home Premium - Win32NT
trying to open port COM10 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM10 -initport
COM10 is a legit port -initport
usb is available on COM10 -initport
usb ftdi serial number ALYWNOZ0 is available - initport
setting port baud rate to 7812
ftdi open successful on COM10 -usbportinit
using protocol SMEC T1:1
attempt to change ecu baud rate to 62500
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
usbsethibaud failed - usbportinit
ftdi open unsuccessful - usbportinit
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
can't open ftdi port - usbportinit
Unable to open/setup port. - ctlrecord_click

There wasn't a mpt2coms.txt file listed. Just MPUpdateLog1.txt

MP Scan doesn't have a separate 'display' mode. It only shows data when it's recording. You're opening the 'profile' you setup for your car, right? and not just the logging screen?

Yeah I opened the profile that I created. When I click on record, I get an error message that says to turn the car off and then back on.

[wowzer]

1) i'm surprised it shows ver 2.0.2.4. the current version is 2.0.2.8. is this computer not connected to the internet? post up the mpupdatelog1.txt file also.
2) once you get 2.0.2.8 installed then post up the mpt2coms.txt file.
3) did you make sure you inverted the tx/rx signals as well as make sure the "vcp" option is checked in the ftdi driver setup in windows?
4) if all else fails you could disconnect the ftdi cable from the ecu and jumper the ftdi tx/rx and try it again to see if any data (albeit nonsensical) comes back to confirm the cable works.

[1986GLH]

1) i'm surprised it shows ver 2.0.2.4. the current version is 2.0.2.8. is this computer not connected to the internet? post up the mpupdatelog1.txt file also.
2) once you get 2.0.2.8 installed then post up the mpt2coms.txt file.
3) did you make sure you inverted the tx/rx signals as well as make sure the "vcp" option is checked in the ftdi driver setup in windows?
4) if all else fails you could disconnect the ftdi cable from the ecu and jumper the ftdi tx/rx and try it again to see if any data (albeit nonsensical) comes back to confirm the cable works.

1) Yeah I don't typically connect my tuning computer to the internet, but I did and downloaded the update.
3) Yeah the tx/rx signals are inverted and the "vcp" option is checked.
4) How do I jumper the ftdi cable to see if data comes back?

Here is the MPScanPort.txt:
mpscan ver - 2.0.2.8
Microsoft Windows 7 Home Premium - Win32NT
trying to open port COM10 - ctlrecord_click
got a good port back - ctlrecord_click
try to open port COM10 -initport
COM10 is a legit port -initport
usb is available on COM10 -initport
usb ftdi serial number ALYWNOZ0 is available - initport
setting port baud rate to 7812
ftdi open successful on COM10 -usbportinit
using protocol SMEC T1:1
attempt to change ecu baud rate to 62500
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 18
Received byte 0
Read confirm byte failed (status:0 - count:0)
usbsethibaud failed - usbportinit
ftdi open unsuccessful - usbportinit
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
Sending byte 254
Received byte 0
Read confirm byte failed (status:0 - count:0)
can't open ftdi port - usbportinit
Unable to open/setup port. - ctlrecord_click

The mpt2coms.txt:
-Comport analysis for mpscan version 2.0.2.8
-Locating ports on computer-
name:USB Serial Port (COM10) deviceid:FTDIBUS\VID_0403+PID_6001+ALYWNOZ0A\0000
number of ftdi devices found - 1
ftdi port num:COM10 serial num:ALYWNOZ0
Inverted tx:True Inverted rx:True
Latency is set to:16
checking to see if usb port number COM10 is a moates device
Moates device not located on this port
default com port set to:COM10

The MPUpdateLog1.txt:
Update started at 7/8/2015 10:35:08 AM

Are there any FTDI cables that are recommended with the SCI chip? This is the one that I'm using https://www.sparkfun.com/products/9718