Originally Posted by Hiboost

I tried on my friend's Evo 9 and had no luck either... I ended up going back to a restore point and reloading the software to get it working on my Evo X again. Also if you get a crash, you can remove the USB connection, wait a few seconds for the confirmation sound, then re-insert and launch EvoScan again and it will connect for me but I used to have to do a full reboot. If it crashes once it won't work again until you get the OpenPort 2.0 device to recognize properly in the OS.

I'm assuming that when you guys are connecting to older cars that you are using the little pigtail adapter that has a mini stereo jack looking connector in addition to the OBD2 style Tactrix cable?

Originally Posted by LaXGSR

I've have occasional issues where no matter what, it just stops reading. The first time I ended up uninstalling evoscan and ecuflash, then reinstalling ecuflash followed by evoscan. The second time, I just restarted my computer, and it magically started working again. Something seems a little flaky with the OpenPort 2.0 drivers at least on my winxp laptop.

Originally Posted by jason4656

thanks for that do you or does anyone have a clean version of 0018 and the xml ? i already mapped and dynod my car but i can copy the tables over

am i wrong in thinking that 0018 inherits from 0016 therefore the 3 lines of xml would still go into 0016 rom file? or is there a full separate xml for the 0018 rom?

thanks for your help

Originally Posted by evo4mad

21st June 2009: EvoScan v2.6 Beta15.zip (see post #1 for download details)
- You still need to install EvoScan v2.5 full registered version first. Available here.
- Updated US and JAP/EU EvoX Mode23 items in data.xml.
- Updated graphing scales in data.xml for EvoX logging.
- CAN logging speed increased.
- Dataitem Editor fixed and now enabled.
- Vista64bit checking, and automatic folder permission setting for Vista.

Work in Progress:
- EvoX CAN formulas work in progress for full release this week.
- EvoX Read DTC and ClearDTC - work in progress.
- EvoX Transmission datalogging - work in Progress.

Originally Posted by jrsimon27

has anybody in here whom has succesfully log there evos used the log in dataloglab?

Originally Posted by GST Motorsports

yes I was just going to make a post about this. I have DataLogLab and all the Mode23 stuff working great now.

I'm pretty happy with how everything is now.

Now we just need more items loggable, like grams/sec and/or lb/min, boost error, etc etc.

I'll post some screenshots of Evo 10 logs in DataLogLab tomorrow.

- Bryan

Originally Posted by SiC

^ Yes, it'll already work with the JDM 5236 & 5237 series without touching the Data.xml

Originally Posted by goofygrin

I had an instance where I closed EvoScan while logging and it killed the OP2.0 cable. I had to disconnect it from the car and the computer, reboot, restart the car and rehook everything back up in order to get it to communicate again. Even EcuFlash wouldn't talk with it.

I don't think it's an EvoScan thing... but when the program closes, it should free up all it's resources (cable, etc.) so that this works a little smoother.

Originally Posted by evo4mad

SiC do you have an xml for 5237 series? I tried your 5236 but that is far different.

Originally Posted by GST Motorsports

yes I was just going to make a post about this. I have DataLogLab and all the Mode23 stuff working great now.

I'm pretty happy with how everything is now.

Now we just need more items loggable, like grams/sec and/or lb/min, boost error, etc etc.

I'll post some screenshots of Evo 10 logs in DataLogLab tomorrow.

- Bryan