tired adding mpscan to the firewall just in case that was the issues i got the same result, i changed from smec 1 to smec 2 same result, i updated the drivers manually as well.
i am at loss.......
tired adding mpscan to the firewall just in case that was the issues i got the same result, i changed from smec 1 to smec 2 same result, i updated the drivers manually as well.
i am at loss.......
where did you get the ftdi cable? you need to use the ftprog (from the ftdichip.com site) to invert the tx/rx lines in the chip and reflash its eprom. also need to confirm that the ftdi chip is not set to use the d2xx drivers only. did you also set up the ftdi usb driver to have the vcp drivers loaded in device manager? also, in my earlier post i mentioned where you should find the log files.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
I got my cable from boosted button, I'm not burning my own cal I just want to read from the fwdperformance stage 5.
I I have another laptop if I get the same issues tomorrow I'm going to scrap the entire idea because I am literally fed up.
You followed the instructions on the wiki (here) to setup the cable in Windows?
From your screenshot, I think the issue must be between the ECU and PC, not the PC itself. Maybe contact Cindy and ask her what calibration yours is based on.
I believe the T2 settings in MP Scan are correct. I just verified the baud rates in the code as 976 and 62500; which is what MP Scan uses.
However, I think the T2 (and maybe other early SMEC's) send the error codes out the SCI port when first keyed-on, but not started. Or, maybe even if it is started. So, you may have to wait 30 seconds(?) before trying to connect MP Scan to the ECU. Otherwise, those error codes will confuse MP Scan and keep it from connecting. Also, the ECU won't accept commands from MP Scan during this time.
This is information I read on the seriously old Yahoo ECU group that Gary D. Started in 2000(!!!). I need to fire up a T2 SMEC on my bench and confirm for myself that the codes come out the SCI port on key-on.
Okay using the same laptop I now got a message saying it cannot communicate with the port !
Tired the second laptop I got the same problem.
I don't think mpscan can access the fwd stage 5 smec
I waited over 30 seconds on both laptops
Last edited by 2POINT5TURBO; 09-03-2015 at 05:40 PM.
Maybe I am not doing something right is there a step by step process on how it's done
Here is what I am doing
plug button cable into smec diagnostic port, turn key on, plug USB into laptop, start mpscan, load profile, press record.
Then in I get the turn key on message.
Am am I doing something wrong here ?
I don't see any reason why that won't work. I do it similarly. My cable is always plugged in. I plug in the USB, start mp scan, open profile, start the car (this is the biggest difference), hit record. It always works.Originally Posted by 2POINT5TURBO
Have you tried it with the car running?
sorry wowzer i just read your message here are the files you requested
https://dl.dropboxusercontent.com/u/...MPScanPort.txt
https://dl.dropboxusercontent.com/u/...s/mpt2coms.txt
- - - Updated - - -
i will give that a shot tomorrow Rob.
there's a bit of a time spread between the two files so don't know if the files can be compared. in one file it found the ftdi cable and on the other it did not.
i really would like to see a screen shot running the ftprog and showing the status of the tx/rx settings as well as a screen shot of the "load d2xx drivers" and lastly a screen shot from the windows device manager / usb controllers / usb serial converter properties advanced tab to make sure the vcp drivers is checked.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
deleted the old ones these are from this morning
https://dl.dropboxusercontent.com/u/...MPScanPort.txt
https://dl.dropboxusercontent.com/u/...s/mpt2coms.txt
screen shots
i'm still workig on ftprog reading the user guide trying to figure out how to use it
okay i took some screenshots so far and i have not saved anything in ftprog
Last edited by 2POINT5TURBO; 09-04-2015 at 01:05 PM.
After you checked the 'load VCP' driver, you need to un-plug, and re-plug the USB connector to get it to recognize it as a COM port...
In FT Prog, the 'Flash ROM' tab is only used for the FTDI 'Vinculum' chips - which we don't use.
But, if the cable initially loads as a 'USB Serial converter' then the 'Load D2XX' driver must be checked FT Prog. The default is to only load the VCP driver.
how exactly do i go abouts finding where in ftprob to load the load d2xx driver ? i'm worried about messing something up.
It's one of the settings on the first tab in FT Prog.
http://www.boostbutton.com/turbonato...ual_ftdi_setup
let me go to the car and try this out, fingers crossed!!!
be careful on the "load d2xx" driver. i've also seen where it says load "ONLY" the d2xx drivers. so in one instance you want to make sure the load d2xx driver and load vcp driver boxes are both checked and the other you would NOT check the load ONLY d2xx option. post up the screen shot so we can see which option you have.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
is there something not checked off that should be ?? this is exactly how ftprog found the settings
also noticed in the log file you have it set to a T1. may need to try it as a t1 and a t2.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
i have tried with both t1 and t2 both give me the same prompt tern key on and off
Posting Permissions
Reply With Quote
