Hey guys,

I was trying to log with evoscan recently... and let me just tell you, what a pain in the *** it has been. I was on the dyno, attempting to log, and it wouldnt pull data. Then the following day, i was attempting to street tune and as soon as i'd hit the start button to log, my cel would come on, the car would get pissed and almost stall... i'd hit the stop button and the light would go off and the car was fine. Then, i checked this in someone elses evo and had the same result.

Im using .99 with vista. Do you guys have any idea what this could be ? or how to fix it ?

its killing me

 

Wow, I have never heard of this type of problem before. Is this the first time you have used EvoScan or did it work fine before?

 

ive had lots of issues... my version .97 or .98 whichever it was worked fine. then when .99 came out, i got a new laptop with vista. Evoscan requires an older version of software to work so i had to install that.... no big deal, im not an idiot. Then i have logged with it fine in the past few days no problem. Then one day all of a sudden its not working. I installed the 2 byte load mut for it because for some reason it didnt show up when i installed the software. So i copied the lines from a friend of mine. It seemed to work fine and now this. I know its not the car, because i use mitsulogger as well with no issues

 

Have you tried un-installing the software and drivers and installing them again? Maybe you messed up the XML doing the 2 byte load.

 

Try a different cable. Sounds like a cable went bad.

 

i could have, but who knows...that was my next option. I was just curious if anyone else has seen this. I'd actully prefer to just copy someone elses xml over mine and see if that works.

 

yes I had the CEL and almost stall when I had a bad cable. Anyone local have a cable u can try out?

 

What cable do you use?

 

Lose the small plug that should be used only during flashing.

 

fwiw I had an issue with evoscan taking over control of my car too. in my case it was on XP and I was trying to log a wideband. I must have fiddled with some of the settings.
after removing and reinstall and a more careful approach to logging wideband ,(not working yet) no issues.

 

I had the same issue after installing wideband logging. Car would develop a misfire, check engine light would come on, and Evoscan would not log properly (i.e. fuel trims were at 199). I reinstalled evoscan and have had no issues since. This is version .99 with XP pro.

 

https://www.evolutionm.net/forums/sh...d.php?t=278933

Maybe this is it...I hit the "de-bug serial button" up in the wideband selection drop down when trying to get my buddy's lc-1 working right.

 

What baud rate? When I DLed the new version, the baud rate is 19,200 as a default, and when I went to log the car would start to sputter a ton (always check at idle first). And yeah, it doesnt log any data

When I switched it back to 15, xxx, it was fine

 

So this has actually happened to me already. What seems to happen is that if you select that it changes the baud rate from 15,625 to 19,200 or something to that effect. When that happens the ECU does not like it at all and if you try to log the car starts to behave oddly (rpm starts going up, knocking etc. etc. etc.)

To the OP, check your baudrate! .

 

+1

I had the same problem as I stated using 19,200