That's weird. It works fine with Evoscan but not with ECUflash.

 

The license is something to do with the cable flashing/reflashing will need to be done with evoscan.

 

I have searched around a bit but havent found answer I am looking for. I have 2005 Evo 8 MR and 1.3 cable and EvoScan 2.8. I cant get it to scan DTC codes. I get following error:
Info: CPU Timer Factor Applied: 0
Info: Initialization Complete...
Info: OBDII Sync Byte Received.
Info: Keybyte Response: 0x08 0x08
Info: OBDII Keyword CRC Received.
Info: Waiting for vehicle ecu...
Info: Arithmetic operation resulted in an overflow.
Info: Check DTCs Complete.

Any advice would be great.

 

bump?

 

I get the same thing. Mine always says "No response from vehicle ECU". +1 for any advice on fixing this

 

I sent request into helpdesk at EvoScan, not sure how prompt they are but given the lack of info or people experiencing same issue I didnt have any other choice. Was throwing P0138 after wideband install and couldnt get the douchers at autozone to reset, but at least they were able to read SES code. Just pulled battery cable and flashed O2 Heater patch. Well see, but all in all this is a great functionality that isnt working for me.

 

I had that code for the longest time until I finally got v7 and now I can't even log the car. Fix one problem get 2 more

 

it might not be a real problem. you might have forgot that Tephrav7 is 62500 baudrate.

 

I'm on the 62500 baudrate and it's still acting up

 

i downloaded hex from my ecu..what to do now? i cant see any maps, just rom info. I changed user level to developer and nothing change. do anyone got any links, tutorials or something? i just wonna play with those ecu and larn omething new. give me some clues guys please, where to go

 

http://www.youtube.com/view_play_lis...F5C03E946&hd=1

I would start here.

 

Hi,

I am new to the mitsu world and I am looking for documentation or source on the MUT protocol. There is a SSM.pdf document floating around for the subaru protocol. Is there an equivalent for the mitsu? I would to port my SSM hardware/software to MUT.

thanx

Mart

 

I have been trying to get my UEGO to log for 2 months now but it just won't work and it seems that people are having great succes with version 2.5

Could someone please send me a copy of evoscan 2.5? I would greatly appreciate it.

 

UeGO works with EvoScan v2.9 use that.

Also EvoScan v2.5 is available for download on this webpage: http://www.evoscan.com/evoscan-updates

 

Hamish,

I found a few errors in the MUTII EFI definitions:

- You have two coolant temp listings. The definition for the first one listed at MUT07 is wrong. The item you have listed as Coolant Temp Scaled at MUT10 is correct.
- Same situation for Air Temperature. The one at MUT3A is wrong and can be deleted. The one at MUT11 is correct.
- There is an item called "Airflow/Rev" at MUT1D. Its actually baro and airtemp-compensated 1-byte load (the ECU 1-byte load and not tephra's 1-byte load). Suggest renaming or deleting.
- There is an item called "Knock Sum 3E" that reads MUT3E. MUT3E is actually fuel level.
- There is an item called "Load Calculated" that estimates load based on IPW. I think it can be safely be deleted forever.
- There is an item called "Load11bit4". This is airtemp-compensated 1-byte ECU load. Probably a good idea to rename or delete.
- The item called "ECULoad" is uncompensated 1-byte ECU load. Probably can group all the 1-byte ECU loads together if you are going to keep them.
- There is an item called "EGR Temperature" that reads MUT12. MUT12 is actually an airtemp value that's not useful for anything. Would be good to delete this one.
- "Crank Signal", "Idle Position Switch", "Power Steering Switch", "Air Conditioning Switch", and "Inhibitor Switch" all read MUT4A. MUT4A is actually evap purge solenoid duty, so those items can be deleted unless you know the correct MUT address.