Printable View
I'm running an openport 2.0 for datalogging and flashing.
I have an old ibm t42 running windows 7 32 bit and evoscan works like a charm.
I have a dell xps 15z running windows 7 64 bit and evoscan will not connect. It connects for a moment and says "No response from ecu". I can unplug the cable from the 15z and plug into the t42 and it connects fine.
I can read dtc's when using either computer and I can also flash with ecuflash.
I made sure I'm running the latest drivers? Any ideas?
Mine only connects maybe 1/5 tries, its really annoying, using windows 7 64. If I get it to log and then stop, its a crapshoot whether it connects again the next time I ask it to. Have to turn car off and restart.
Evoscan is up to v2.9 now. I've tested it with a 32bit Win7 netbook but never on a 64bit machine. Try running in compatibility mode. If that doesn't work then you can load Windows Virtual PC: Home Page if you have Win7 Professional or Ultimate. This lets you run a virtual 32 bit Windows XP OS.
alright fellas, this turned out to be something really simple. I installed the software on my wife's identical laptop and it worked perfectly. So, then I tried evoscan on my machine again. It would not connect, so I installed 2.9 on it and it worked fine. So I pulled up both machines side by side and looked at the 2.6's settings. There is a drop down list that says "Select ECU" and for some reason on my machine it was set to OBDII, even though the other settings were for mutIII. So, I set it to EFI and now everything works great.
I'm not sure how that setting got set, it isn't even in the drop down now unless I select OBD2 from the other options, but oh well, it is fixed.
I've been running EvoScan on Win 7 Pro 64 since 2.5, and never had a problem. You definitely have to pay attention to the settings though.
Yes, MUTIII.
does anyone have a better graphing program for these? I like HHH's graphs a TON better.