LoadMut 2-Byte doesn't fit with the Ignition (ROM)
Thread Starter
Newbie
Joined: Jan 2008
Posts: 25
Likes: 0
From: Switzerland
LoadMut 2-Byte doesn't fit with the Ignition (ROM)
My car:
Evo9 Stock, Tactrix Solenoid
ROM-ID originaly: EDM8840013 switched to
ROM-ID new: EDM8840016 (with no update by the Mitsu-Dealer, what is for me the only reason for that problem)
Problem:
When I log my car with Evoscan 1.35, the logged ignitions values (Map2) and the values for the the 2-Byte Load don't match with the Ignition Map2 values of the new ROM:
and
Is there anybody happened the same issue? The Load seems to be fine but the value for the ignition is around 1 column left, means the ECU takes for example not the value in column "240" but from Column "220". This is competely wear.
Need help.
Marcel
Evo9 Stock, Tactrix Solenoid
ROM-ID originaly: EDM8840013 switched to
ROM-ID new: EDM8840016 (with no update by the Mitsu-Dealer, what is for me the only reason for that problem)
Problem:
When I log my car with Evoscan 1.35, the logged ignitions values (Map2) and the values for the the 2-Byte Load don't match with the Ignition Map2 values of the new ROM:
and
Is there anybody happened the same issue? The Load seems to be fine but the value for the ignition is around 1 column left, means the ECU takes for example not the value in column "240" but from Column "220". This is competely wear.
Need help.
Marcel
Last edited by h101171; Aug 9, 2008 at 04:50 PM.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
