Hey guys, got an issue here.

My 2005 Evo logs and hooks up fine to EcuFlash and EvoScan 2.5, 2.6, and 2.7. The ROM id is 96940011. My friend has a 2005 RS with the same ROM ID and EcuFlash works fine, but EvoScan just will not connect in any version.

Any ideas on what to try? I've read through forums and seen solutions in the OS and such but haven't seen anything on this issue specifically. EvoScan even will read his ROM fine, it just will not log, any ideas? I've read some of Hamish's posts re: what could cause this but none seem to apply.

Thanks!
Matt

 

Bump for help

Have tried multiple 1.3 and 2.0 cables, two laptops, and older versions of ECUFlash also.

 

Which version of ecuflash are you running

 

EcuFlash...? 1.42.2595 but that works fine, as does reading the ECU in EvoScan which is what's puzzling to me

 

any chance his baud rate has been changed in his tune?

edit: in evoscan, try changing the baud rate at the top to 62500, then see if it logs.

Or if that map is defined in ecuflash, just change it to stock, if it isnt already stock.

 

What do you mean change it to stock? You can change an ECU ROM baud rate so that EvoScan has to match it? Is what you're saying?

 

Just tossing out ideas. But I was wondering if someone may have changed the MUT baud rate in your friend's tune. Higher baud rate = faster logging. If it doesnt match, Im pretty sure it wont log.

Here is the thread Bez started when he found it.

https://www.evolutionm.net/forums/ec...00-tested.html

If the table isnt in ECUFlash, the easiest way to test it is probably to change the baudrate in evoscan to 62500 and see if it logs.

 

Thanks for the info, I checked into that and it appears as though his ROM doesn't have that MISC section but I'm going to try to change the baud rate just to be sure.

 

Charlie you are the MAN! That fixed it! It wasn't in his ROM so I just changed it and viola! Thanks a ton for the info!

 

Was just gonna suggest that... glad you got it figured out!

 

no problem. Glad I could help!