I had an issue getting a win7 laptop talking to an ecm also. Mine was solved by hitting "F8" during boot up and selecting the option "disable driver signature enforcement" toward the bottom.
I had an issue getting a win7 laptop talking to an ecm also. Mine was solved by hitting "F8" during boot up and selecting the option "disable driver signature enforcement" toward the bottom.
that's strange, since the ftdi drivers are digitally signed and certified. i wonder if others have had this issue? my main computer at home uses win 7 with no issue. you may want to download the latest ftdi driver (http://www.ftdichip.com/Drivers/VCP.htm) setup executable and try reinstalling......
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Its an early win7 laptop with no internet connection. I couldn't do that "connect to the interwebs to check for updated drivers" thing. F8 thing seemed to get it working fine though whatever the cause.
ok - f8 is ususally just a temp fix until you reboot. there are ways to disable the driver checking but the best alternative would be to reinstall the certified drivers at some point.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Well we kinda figured out the problem. The plug was bad. Had one ordered and the laptop recognizes it. Still having issues talking to the car though.
do the items in post #16 and let me know.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
I talked to the tech. Here's what we did.
Verified that the FTDI cable is setup exactly like the BB cable that I have.
MpTune / MPScan do see the cable.
We tried to read the ECU and it does something odd after the prompt for the key dance.
It pops up a little box that says:
Test com:
baud:7812 Bytes1:0
the boot.txt file looks like this:
-bootserial routine-(called from)
Using Boot Program Modular Bootloader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 18:47:24.0575995
return byte 1: 0
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
sending boot program. length = 256
Boot send start time 18:47:26.0577139
Boot send finish time 18:47:26.2997277
Boot reread finish time 18:47:26.6277465
done sending boot program. bytes returned = 0
read timeout set to 328
bytes returned were:
------------------
Can't read chip because boot program is not running properly
------------------
SMEC or SBEC?
Did the fuel pump prime?
When are you applying the 12v to the boot wire?
When are you switching off the 12v to the boot wire?
You're following these instructions, right? - http://www.boostbutton.com/turbonato...to_flash_a_cal
post up the mpt2coms.txt file also please.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Wowzer,
I'm the guy working on this issue, thank you, and matt for your help, if you guys are ever in Pa, swing in and Ill give you free dyno pulls... lol
I was told its a smec, I didn't buy it or build it, it was dropped off from a customer who just purchased it, car was 90% completed, just needed a few small things to get it driveable including tuning.
Production date is 8/87,I talked to the guy who built it, he told me smec. Would it hurt to try the sbec method?
I added pin 11 to the ecm, fuel pump does not prime when applying power and turning key on.
Followed instructions to the T...
On a side note, I can read codes and see data with a snap on scan tool.
Email me at Goodlingmotorsports@gmail.com and I can give you a detailed message on everything, and send you those files.
This used to be my 88 shadow. I bought the flashable smec from rob and had a custom tune installed on it when I bought it. I never installed pin 11 to the smec and also never had it hooked up to a labtop also. Any questions about the build I'm more than willing to answer. The car is def a smec and I installed then charge air temp and such to get it to t2 before i bought the calibration.
the test com message is a poorly worded message! sorry. basically means that the boot program was attempted to be downloaded but failed. the file you posted shows that no bytes were echoed back. we'll see what the other text file says once you post it. it would be nice also to get a screen shot of what shows on your screen in the status bar on the lower left of the mptune window.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Loose wire is not hooked to anything,
lower left corner says FTDI USB Port settings:COM7, 62500 baud, 32k size
Which other file did you want to see?
OK, well it sounds to me that the setup and procedure are correct. I know the SMEC is OK (because it flashed the first time when I built it; and it runs the car). So, potentially the cable setup is not right.
If you haven't already, check the cable config - http://www.boostbutton.com/turbonato...ual_ftdi_setup