The SST equipped mitsus will throw codes every time you read or write. It's the nature of the Can Bus losing connection and freaking out, tripping the codes.

Just clear them after your read/write and you are fine.

 

What about using the Cobb AP? Does this change the flash count at all?
(I thought the Cobb AP reflashes back to stock.)

 

Don't know - But I can give out some memory addresses to log if people are interested?

5268/5304: 0x8040B0
5360: 0x8040B4

 

It seems that once you rewrite Calibration ID i.e. Case ID it is reset back to 0.
@69EB8 in 53040010

 

Isn't the CaseID the mitsu part number?

 

Sub'd.

PM sent to tephra.

 

Yes, it is. Maybe it is only checked in that routine. Anyway it can be reset via Mode 31/SID E1 01 and some other conditions met.

 

Is here a programming Station ID value that's written when writing the ECU? If Yes, can we read and reset this value?

So the flash counter is updated on a read also - how about the Programming Station ID?

 

Tephra, not to get too far off topic, but are there "permanent" codes, like a p0219 engine overspeed , stored in the ECU?

 

yeah I think so.. havn't really looked into it properly thou..

 

Nice find!!

 

Well, Cobb said this back in 2008..

Dunno if that info still holds true today, though. Guess it depends on whether or not unmarrying the AP is writing back the last stored flash count along with the stock backup map.

I'd really like to know the answer to this as well, if anyone happens to find out for certain.

 

There is a reason that Cobb hired Tephra.


Trust the Australian. He will lead you to enlightenment.

 

as I said - I dont know if the AP restores the value... if someone had an AP they could log and find out

 

I don't think we can log evoscan style with an AP loaded ecu.