mrfred

iTrader: (50)

I have not tried my newest Data.xml file on an Evo 10. Try the next newest one. Its a few days older. Let me know if it works.

GTR2009

I have tried both, the older one and the 98KB one which is dated 06.15.2009 I think
My ECU is 52680017

mrfred

iTrader: (50)

Is this the one that you tried? If yes, then there is something wrong with your setup because I know this Data.xml works. The proper way to get EvoScan 2.6b14 installed is to install v2.5, then drop the 2.6b10 files on v2.5, and then drop the 2.6b14 files onto v2.6b10. Did you do that?

https://www.evolutionm.net/forums/ev...ml#post7176324

GTR2009

I have installed EvoScan 2.5 then unzipped the 2.6b11 over 2.5 and the unzipped the 2.6b14 files over. I don't have version 2.6b10
The same version works without problems on Subaru, but with the other cable Tactrix 1.3

mrfred

iTrader: (50)

I can't help any more than that. Sorry.

mrfred

iTrader: (50)

For the 526800XX:

- IATS is at 808858 and MAT is at 80865E. So try adding 0x6 to your IATS address.

- APP is at MUT_BC. You're going to have to pretty far down the MUT table. Sorry about that.

- TPS is at MUT_BB.

- MIVEC load: The easiest way to find it is to go to the header data for the MIVEC load axis. If you are just using ECUFlash to explore the ROM, then set up a 1D Hex16 lookup at the (MIVEC load axis address) - 0x4. You'll see a value that goes like "CXXX". The MIVEC load address will be 808XXX. Hope that makes sense.

- Timing load at low IAT: This one is pretty tough to figure out how to make it easy for you to find. Suggest its not really needed since its only used with IAT is below 25C, and this is rare on the Evo 10 because the IAT sensor is pretty far into the engine compartment.

SiC

iTrader: (1)

I'm using a hex editor & also use ECUFlash for the MUT table. Yes, it makes sense, I'll try them out later, thanks!

jason4656

Hi Sic, i noticed earlier you were talking to crcain about 52360016 same rom i have and you found the addresses due to it being different from 52360018

1st 7eedd
2nd 8a6f5
3rd 8a6fa


would i be correct in thinking that i change the above addresses into the following code before adding those lines to my xml

<table name="IFMode 0x05 -> 0x23 #1" category="Misc" type="1D" address="0x7f58d" scaling="Hex8"/>
<table name="IFMode 0x05 -> 0x23 #2" category="Misc" type="1D" address="0x8ada5" scaling="Hex8"/>
<table name="DoMode 0x42 -> 0x52" category="Misc" type="1D" address="0x8adaa" scaling="Hex16"/

so therefore i would change


0x7f58d -->0x7eedd
0x8ada5 -->0x8a6f5
0x8adaa -->0x8a6fa


then enter to xml then change values accordingly in ecuflash and then try??

thx

SiC

iTrader: (1)

That was for 52360016

The one for 52360018 is posted in the first post of this thread.

jason4656

yep thats my rom 52360016, so what i posted is correct sequence of events?

thanks

SiC

iTrader: (1)

Yes, that is correct. But I still recommend using 52360018 though.

Mellon Racing

iTrader: (38)

similar issue I think here:

I made a copy of my trusty 2.5 install, copied the new 2.6 b14 data.xml and evoscan.exe to overwrite the existing in their locations etc...

odd thing, I've got an EVOX coming this morning for some tune development work and I figured I'd try 2.6 b14 on my 8 with the 2.0 cable to make sure everything is working. In Evoscan I have Open port 2.0 checked and Mitsubishi Mut II (if that matters) and I'm getting an error "OpenPort2 USB Cable Not Responding". I opened Ecuflash 1.41 and it shows at the bottom "Openport 2.0 com 3" which is accurate according to device manager. I tried to read the ROM but get an error "j2534 error unable to open device", "unable to connect to vehicle interface".

My 1.3 cable works fine with Ecuflash 1.41 and Evoscan 2.5 and 2.6 b14 on my 8. Do I have a bum 2.0 cable? I've used it before on some 8's with 1.41 but it's been awhile.

I uninstalled the cable/driver in device manager, rebooted and reinstalled ecuflash 1.41 to get the drives back, I swapped out the usb cable portion of the tactrix 2.0 device and nothing is working. I can't log with evoscan and I can't read with ecuflash.

Hiboost

iTrader: (9)

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?

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.

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