I had a similar problem. I am almost positive evoscan was filling the can bus with error frames which make any communication between the ecu and engine almost non-existent. Whatever the case when I did have the problem, my computer and cable did the same thing on another IX. I reinstalled evoscan and all has been good. Weird thing was it was fine before and then it was fine after I reinstalled it. So who knows what happed but something did.

 

If your transmitting and recieving at the wrong baud rate, it will generate incorrect data both from the ECU and to it. So its definitely possible that instead of sending the proper bytes, they are interpretted as diagnostic triggers which are turning on and off different features (requestID's that perform a function that we don't have completely documented yet)

Also, if you have the openport 1.3u cable, a few more of the pins are wired, although I don't think it has any affect on anything, you could try a 1.3m cable, if it works fine and its not the baud rate, then at least you know its something related to the cable.

FWIW I have never had anything similar to what you guys are describing happen on my car or any other car I've logged with, using both Mitsulogger and Evoscan.

If you want to test the baud rate being the issue, write the correct baud rate down and save it somewhere, then set the baud rate that evoscan tried to use in mitsulogger. If its baud rate related, it should do the exact same thing.

The difference between mitsulogger and evoscan is mitsulogger never alters the baud rate unless you change it yourself. And you can set all of the settings back to default if needed.

 

i will try the baud rate thing... i already tried the uninstall reinstall thing and that was no help. Thanks for everyones input... you guys are being very helpful

 

I though of this as well, has the OP tried this?

 

Unless his "flashing" plug has gone bad this shouldn't be an issue either. I log with both of those plugged in.

 

When you uninstalled did you track down and delete all the EvoScan related folders on the machine? What happens if you take the same cable to another machine and clean install EvoScan on that...does it still happen then?

 

I though I remember Malibujack saying that removing the plug is a safer bet. I also use to log with the white plug in alll the time, but now log with it un pluged. Won't hurt to try with the white plug out.

MB

 

Sometimes yes sometimes no I've seen it cause problems once and not the next time on the same car.

 

^^ Fair enough I guess we will soon find out.