anyone ever had this problem? I cannot connect to EcuFlash just fine, and was able to get my ECU image and mailed it off to Jestr tuning, but am not able to connect to EvoScan in order to datalog.
When i connect to EcuFlash, i see "OpenPort 2.0 connected to COM3" in the corner... but when trying to connect to EvoScan I get an error about "OpenPort2 cable not responding", and that I am supposed to unhook it and plug it back in or something.
I have tried many combinations of EcuFlash and EvoScan running together or before/after one another, and consistently I am able to connect with EcuFlash but not with EvoScan.
Is there a way to specify which COM port to have EvoScan use? maybe thats the issue? but I am unable to find that option.

edit - I have a Tactix 2.0 cable with the re-flash plug, both are connected. connector link: (http://www.tactrix.com/index.php?pag...mart&Itemid=53)

thanks all!
matt

 

What version of Evoscan are you using??

If V2.7.90 or 2.8 you must upgrade your ecuflash as Evoscan uses a new driver as a passthrough device and not a comm port.

Simply upgrade your ecu flash to latest beta 1.43 plug cable in and go to licence tab, it will update OP 2 driver and firmware

Hope this helps

 

nice, ill try this out! i am on EvoScan 2.8 and EcuFlash 1.42.

 

Let us know. Pretty sure this will solve your problem

 

why... why does this software feel like the most brittle thing ever?!

so when i first received my Tactrix cable, i ended up going back and forth with tech support trying to figure out why the drivers wouldn't install correctly for me (errors about my OpenPort2.0 J2534 Vehicle Interface did not install properly). I have no idea how i got it to finally work with EcuFlash, but it did.
so just now, i went to EvoScan's site and found a link to the 1.43 Beta of EcuFlash, and installed that. Seemed to go just fine, and I fired up EcuFlash and went to the licensing page. There was a text box for license entry, and some text that read "Unable to connect to OpenPort 2.0. Licensing information cannot be displayed".

I uninstalled the previous OpenPort 2.0 drivers from my driver manager, and both the openport 1.3 and 2.0 seemed to reinstall properly, but then i received the same error about the "J2534 Vehicle Interface did not install correctly" again. so now i feel like i'm back to square one.

Is there some magically sequence of installing the 2 softwares, and plugging in the cable at a specific step of the install which makes this all happily install? It feels like way too much work to install software.

but thank you for your help so far. ill keep trying to reinstall everything

 

Unistall both ecuflash and evoscan, delete all drivers to do with OP2/tactrix etc search the registry too!

Install ecuflash 1st, update device firmware under licencing.

Then install Evoscan 2.8

Try it in that sequence

 

spent many hours searching through registry, taking ownership and deleting old drivers from system32 folder, etc... but at the end of the night the beta EcuFlash driver still will not install properly, and now pretty much not at all. when the driver installer finishes, i get red X's instead of green check marks now. so i totally don't know where to begin to fix it. but i'll keep trying tonight and this weekend, and hopefully i will be able to have EcuFlash properly installed so that i can get those drivers updated.
thanks again for the help, at least i know where i need to go, now i just need to get there.

 

****ty deal man I'm waiting on my stuff in the mail hope I don't have to go through all this. Good luck OP hope u figure it put quickly!

 

ya, it sucks. the guys at Jestr were super quick and helpful in getting the flash done and back to me, but the damn software is the issue.

my plan is to wipe the computer back to factory settings, and install the beta EcuFlash this weekend. if that doesnt work, then ill just wipe it again, and install the version of EcuFlash which at least worked for reading the ECU, and try another logging product maybe

 

well, after rebuilding the laptop from scratch, the beta version of EcuFlash installed without any problems at all, and the update (from the licence tab) worked flawlessly. thanks for the info guys!!

so my only question now, is what are the correct settings for the EvoScan app? the only ones that seem to work are when things are set to ODBII, but it seems like the amount of data from that protocol is much less than the other ones. Anyone used EvoScan on an Evo IX that can point me in the right direction so i dont have to discover the best settings via trial and error?