FTDI cable setup

Following is a summary of steps needed to get the FTDI 232R chip to work with mpscan/mptune.


-download and install the latest appropriate VCP drivers for your windows pc from ftdichip.com

http://www.turbo-mopar.com/forums/at...id=64553&stc=1

-download and install ft_prog from ftdichip.com

http://www.turbo-mopar.com/forums/at...id=64541&stc=1
-start program and click the magnifying glass in menu bar
-vendor id should be 0x0403 and product id should be 0x6001
-expand usb config descriptor and make sure settings are correct

http://www.turbo-mopar.com/forums/at...id=64552&stc=1

-expand usb string descriptors and make sure settings are correct

http://www.turbo-mopar.com/forums/at...id=64551&stc=1

-expand hardware specific
-click on d2xx. under the property determine whether box should be checked or not. the VCP driver MUST be loaded so in this example the box is NOT checked.

http://www.turbo-mopar.com/forums/at...id=64550&stc=1

-expand the invert rs232 signals and make sure the invert txd and invert rxd boxes are checked.

http://www.turbo-mopar.com/forums/at...id=64549&stc=1

-expand the io controls and make sure settings are correct

http://www.turbo-mopar.com/forums/at...id=64548&stc=1

-click the lightning bolt in menu bar to program the device
-exit the program
-unplug the ftdi cable, wait a few seconds, and plug back in. your device should be recognized properly.

All done with FTDI device

-in windows start the device manager
-expand ports (Com & lpt1)

http://www.turbo-mopar.com/forums/at...id=64558&stc=1

-right click on the appropriate usb serial port that is the ftdi cable
-select properties and make sure ftdi shows up as manufacturer.

http://www.turbo-mopar.com/forums/at...id=64557&stc=1

-click port settings tab
-click advanced button
-set parameters as shown and click OK

http://www.turbo-mopar.com/forums/at...id=64556&stc=1


-expand Universal Serial Bus controllers
-look for the the USB Serial Converter and right click on it and select properties

http://www.turbo-mopar.com/forums/at...id=64555&stc=1

-make sure it shows FTDI as the manufacturer
-click Advanced tab
-check the Load VCP driver as show and click OK

http://www.turbo-mopar.com/forums/at...id=64554&stc=1

-close the device manager
-unplug the ftdi cable, wait a few seconds, and plug back in.

All done with windows setup.

Thanks Morris,
A great reference.

Thanks Morris.
I just had to address some of this when I went to flash with MPTune, my laptop did not recognize my previously programmed FTDI cable.

Sent from my ONEPLUS A6000 using Tapatalk

do you have to do this same setup when using the FTDI cable with MPscan on an android device?

only mpscan/mptune use the ftdi cable to connect to the sci connector. mpscandroid uses the mpscilink device which connects directly via its uart/ttl setup to the sci connector.

Gotcha. There are several different ways to interface with the ecu's on these cars, gets a bit confusing as to what works with what might not be a bad idea for someone to put together an application chart.

agree with the confusing stuff!!! and then throw in all the different types of flashing hardware (latch adapter, flash adapter for smec or sbec1 or sbec2, ostrich, burn2, etc) and it really gets confusing.

Quote:

---

Originally Posted by wowzer

agree with the confusing stuff!!! and then throw in all the different types of flashing hardware (latch adapter, flash adapter for smec or sbec1 or sbec2, ostrich, burn2, etc) and it really gets confusing.

---

You forgot the SBEC2-377,SBEC2-652 and SBEC2-910 to further complicate!!!

Quote:

---

Originally Posted by crusty shadow

do you have to do this same setup when using the FTDI cable with MPscan on an android device?

---

If you actually meant mpscandroid using a USB OTG adapter and the FTDI cable, then that never really worked well enough to consider viable.

Sent from my ONEPLUS A6000 using Tapatalk

Quote:

---

Originally Posted by wheming

If you actually meant mpscandroid using a USB OTG adapter and the FTDI cable, then that never really worked well enough to consider viable.

Sent from my ONEPLUS A6000 using Tapatalk

---

initially i used my phone and the ftdi cable via otg as wayne noted. however, the default latency in the ftdi cable as well as the way the android OS uses it's message queue made the logging speed unacceptable. i was always hoping ftdichip would come out with an easy to use library for android but never did and i didn't have time to try to port it myself.

ok cool, just wanted to make sure i didnt waste money on 15 of the wrong cables, lol

Hello...I have looked about and attempted different approaches to get my machine (Dell E6400, 2.4GHz Dual Core, 3GB RAM, Sonya 32Bit) to 'see' a USB to sequential link. It comes up as a CH340 USB/Serial link in "Associated Devices" by means of the settings in my old netbook running W10. I need to get the link to work a 'push to talk' (PTT) work in a Ham Radio program called Fldigi. I don't generally have the foggiest idea how to make it go. From what I have perused the driver should as of now be in Mint however I simply don't generally have the foggiest idea how to discover it and afterward get it to key up my radio to communicate the different datamodes sounds from Fldigi.

https://www.7pcb.com/

wrong forum?!

if doing this on a raspberry pi you need to disable the original o/s drivers so the ftdi drivers can be used. google it.