RomRaider

in a SSM-III user manual dated of 2007.12.14, the following error is listed:

4103

Rewrite time exceeds the limit. If exceeded the limit of the number
of ECM reprogramming.

Replace ECM.

uhm...

Mart

Just rewrite reflash counter and use again...

Humm, something got my attention after reading this thread. I got a Openport with the intent of using it for logging purpose only on the stock tune. I know it's a bit unusual but I want to understand logging so that if I decide to get it tuned after my warranty is over, I know how to keep an eye on my engine.


I was also thinking about grabbing a copy of my rom just to take a look a it under romraider just for kicks.

I am concerned with one poster that said he got flagged by Subaru just for retrieving a Rom image ... Any additional information on this ? Do they keep track of the # of accesses ? Would logging void my warranty ?

Anyway, I know nobody can answer this for sure but Just in case someone has a bit more experience with this would like to shine in that would be great

Thanks

I strongly doubt they could actually detect that. Even if they could, reading the ROM should not have any affect on your warranty. It has no effect on how the car runs.

But I don't doubt that someone at a dealership would say something like that, as there seem to be a lot of people in the car industry who believe strange things, and/or make up strange things whenever they feel like it.

I said they almost denied my claim because they noticed the ECU checksum was different. I did get my car covered under warranty after I proved to them nothing had been done and that nothing I had done to the car would have caused the motor to go the way it did. The guy was just spouting BS so the dealership wouldn't have to do the work for free (he also told me the short block alone was $9k if I had to do it myself...right). What my post was supposed to convey was that whether you are reading / writing the ECU image on the car there is some counter being incremented and that the dealerships can tell even if you are just pulling the rom down.

It's good to know thanks. I'll stick to data logging only for now then.

Does anybody know if Subaru "blackbox" any other information on the engine ? Did anybody ever gain access to it ?

I have highlighted the important part.

Reading the ROM does not change the checksum. The part about the counter was almost certainly just more BS.

+1 on BS.

Subaru is required by law to allow 3rd parties (car shops) to flash cars for TSB's, updates, etc. So unless you have a thousand flashes in the supposed 'flash counter', its bunk. Although, it's certainly possible that if a flash counter exists, the SSM3 allows it to be reset when flashing an OEM update.

Checksum on the other hand, is understandable.. However, it will change for an updated OEM rom, so it's also possible that they're just BSing.

The best advice I have found is to find a friendly dealer with good reviews from other enthusiasts. If you go to the wrong place they will claim that you voided your entire warranty on BRAKES because it LOOKS LIKE you unbolted the TMIC, and therefore MUST have had an aftermarket turbo, fmic, exhaust, and standalone. They'll refuse to warranty anything unless you get SOA/lawyers involved.

Mhh, I know this funktions from Bosch Diesel ECUs with Tuning protection...
They count flashes and even reads of the ecu...

But more interessed to me:

in witch way to you read the falshcounter ?
Is it readable via SSM oder OBD2 ?

In Diesel-dump I know only one flashcounter, with is only incremented by the original station flash tool AFAIK..

One other piont:
For checking stock software on ECU, europa dealer read the checksum of this file via OBD2 interface .
Anyone work with this ?
How can I read and check this CS ?
Is is calculated by ECU or a constand value in dump ?
Does anyome know the algoryment of it ?
Is it possible to use unused areas to bent the file checksume is the same then stock after chancing so maps ?

You can read CVN via ODBII.
Mode 0×09 PID 0×06: Calibration Verification Number
It's calculated in code and may be or may not be equal to the ROM checksum value. It depends on the implementation in code.

Ahh, good to know

Are there any suggestion for a free OBD-II Scanner Software witch works with Tractrix OP2.0 Interface ?