can't connect to ecuflash/evoscan, PLEASE HELP
 

everything worked properly and I was able to red/write ecu and log via evoscan but now I can't get any responce from ecu. ecuflash doesn't highlit WRITE button any more, after I turn the ignition on. it highlits only READ button but throws error code then, when I'm trying to read the ecu. as for evoscan, it says 'waiting for init responce'. the ABS light is blinking (as it used to do previously, while logging) and does nothing afterwards.

I have 1.3 cable. reflash connector is connected (it doesn't do anything for the logging though). tried another 2.0 cable, another laptop, fresh copy of Win7 but still the same

please help

http://s11.postimg.org/uepw0buqr/image.jpg

http://s11.postimg.org/5iwgcu82r/image.jpg

any suggestion ?

can it be car's OBD port malfunction ?

Is this with the car running and the battery effectively charged?

Have you tried all of the suggestions in the sticky on this problem at the top of the forum? https://www.evolutionm.net/forums/ec...tart-here.html

this happens to me sometimes and i cant figure out why either. but evoscan works for me, however ecuflash doesnt.
i noticed if i have the laptop plugged in the problem is less likely to happen.
so try that first. otherwise, hopefully someone else chimes in.

yes, the battery is fully charged
and was trying to log evoscan on running car as well

:confused:

thought it might be car's OBD plug issue
hotwired another OBD plug near ecu, right from the appropiate pins - still no luck

one last try - swapped my ecu in another evo and hey ! ecuflash read the rom instantly, then wrote again etc.

please help, where to look for problem in my car. what can cause this ? car runs and drives well, just doesn't read/write/log the ecu

When you hotwired the OBD plug near the ECU along the wiring harness, did you leave the rest of the associated wires attached to the vehicle? If you have a short on one of the lines it would still cause the MUT init to fail no matter where the OBD port is wired, unless you isolated that line.

Do you have access to an oscilloscope or know someone who might be able to watch the appropriate lines on the OBD port while Evoscan/Ecuflash are trying to do the init?

yes..
wonder if I've done it right ?

ecu pin79 - init(flash) line to logger cable white plug
ecu pin62 - (data link) to obd pin 7
ground to obd pins 4/5
+12v to obd pin 16

unfortunately no, I don't...

I have had issues too but usually with reflashing will just run a hard wire from reflash connector to pin #79.

However you arent logging at all so your issue lies within the reflash connector.

Try maybe 2.8 or 2.9 and a newer version of ecuflash

Open a rom then try reading.

I checked the voltage today

while engine running it shows 13.4-13.6 volts (with the rad fans on - for unknown reason they run constantly)
after shut off ~12.2 volts, dropping to ~12.1 after couple of seconds, on opened ignition

is that normal or can it be the reason ?

I just went through this issue and 12.1V is what I had as well with the key turned to on but not running. Your battery level is much too low to read/write without some type of external power source. I hooked jumper cables to my car from another vehicle which was running providing a nice 13.5V consistently. My problems disappeared after that. Those ECU's are very picky on voltage levels.

*EDIT*
Sorry just noticed you mentioned not being able to log the car with it running. The voltage you read with the car off is a little low to read/write but you should be able to log the car with it running.

When you put your ECU in to another Evo, did you use the exact same laptop and OpenPort cable connection to test it out?

I ask because the log lines in your Ecuflash post look very strange. The log goes from 'sending init seqeuence' to 'interface close' in roughly 200ms, but sending the init sequence alone takes 2 seconds (200ms per bit * 8+1+1 bits).

Having noticed that, I'd suggest looking in to your laptop and driver configuration. When my Openport cable broke (bad internal solder joint from the factory) Ecuflash would at least run through 3 different init sequences before giving up.

Seems like a bad laptop. Anyone in location to test and rule out the laptop or tactrix.

st I would try a completely different car with the same equipment same laptop same Tactrix.

Then I would try a different laptop same Tactrix. Then I would try different Tactrix and then same laptop.

Eliminate the possibilities

^yes !

laptop and cable works on other cars flawlessly

recently I've hooked another battery to my car's battery with jumpers, tried to log/read/flash but with no luck.

this is getting annoying !