ECUflash Evoscan in a '95

[Aphix]

I've been messin with Evoscan for about three days now and combing through the threads but I cant come up with anything to resolve this. This comes up whenever I try to activate the radiator fans. When I try to log it will do something similar but will say Auto ReconnectRetry#1,2,3, etc. after initialization and get stuck in a loop.

I'm also using the ebay FTDI cable. Baud rate 15625. Hybrid protocol. I installed OpenEcu on my computer as well to make sure I had the FTDI drivers. My computer is telling me the drivers were installed when I plug my cable in.

Info: Initialize Vehicle ECU...
Info: DSM Initialize...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Error: No Response from Vehicle ECU
Info: Actuator Complete.



Does anybody know what could fix this?

 

[steve-o_95_GST]

Unless Im mistaken, it only works on the 98\99 ecus

 

[Aphix]

It states on the site that it supports the 95 ecu, but it doesn't give full support. I should still be able to link up with it

 

[Aphix]

These guys over at 3si.com have been doing some SERIOUS work on 95 ecu's working with evoscan. Like 65 page thread work.. Starting Here After about 20 pages of sifting I came up on this solution to the 3gt guys problems Logging 95 with EvoScan - SUCCESS!! - 3000GT/Stealth International Message Center Basically the data pin for a 1995 (Pin #1) is in a different location on the data cables evoscan uses (Pin #15). Here is a link to a cable that a guy has came up with that seems to be a fix to the issue Anyone up for a $7 "hybrid" logging cable? - 3000GT/Stealth International Message Center If the 1995 3gt ecu setup is identical to this, which seems logical, it might be a fix.

Wouldn't you be able to skip over that whole adapter by switching the Pin #1 into Pin 15 on the connector mounted under the car?

 

[the_mork]

Unless Im mistaken, it only works on the 98\99 ecus

You are mistaken.

It certainly works with 97 ecus but 95/96 ecus tend to be a bit shakier. I wouldn't count on the 3/s ecus to be the same but if they switched to obd2 in 95 like DSMs then that is a pretty good indicator IMO that it might work.

 

[Ceddy]

I've been messin with Evoscan for about three days now and combing through the threads but I cant come up with anything to resolve this. This comes up whenever I try to activate the radiator fans. When I try to log it will do something similar but will say Auto ReconnectRetry#1,2,3, etc. after initialization and get stuck in a loop.

I'm also using the ebay FTDI cable. Baud rate 15625. Hybrid protocol. I installed OpenEcu on my computer as well to make sure I had the FTDI drivers. My computer is telling me the drivers were installed when I plug my cable in.

Info: Initialize Vehicle ECU...
Info: DSM Initialize...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Error: No Response from Vehicle ECU
Info: Actuator Complete.



Does anybody know what could fix this?

Looks like you might have clicked one of the Actuator buttons.
Not all the Actuators work with the 95.

Select just one Item to log the click Start Logging.

 

[Aphix]

Yeah I know it was an actuator. That is just an example of what happens when I attempt to communicate with the ECU. If I try to datalog something like timing or an O2 sensor etc the Event Log will show it connect to the DSM and then as soon as that happens it will go into a Auto Reconnectretry#1,2,3,.. and get stuck in a loop.

Heres a link to a picture of the difference in the cables (((Mitsubishi MUT-II/MUT-III Datalogger))) - Page 59 - 3000GT/Stealth International Message Center . I'm gonna try to swap pin 1 into the pin 15 slot and see what happens. Here's a post in the thread to an event log of the same issue I'm having (((Mitsubishi MUT-II/MUT-III Datalogger))) - Page 47 - 3000GT/Stealth International Message Center