RomRaider

I posted this over on nasioc but it seems like more of this kind of discussion is shifting back here now that the forums are back up, so I figure it's worth a shot to ask her too.

I've been doing a lot of research on self-tuning by going through old threads here and other related forums. I came across this thread that mentions 05+ ECU's report the VIN, CalID and CVN when queried for it with a scan tool. Anyone know where this is stored? The thread mentioned you have to issue a $09 command. I downloaded a couple stock 2006 ROMs from osecuroms.org for comparison, but it doesn't seem to be a reference to a memory location in the ROM from what I could tell by looking quickly with a hex editor.

don't know but I have seen the VIN in a RAM dump on later model cars (something like 05+). For example, the 05 WRX.

I think the VIN is stored in the Body Integrated Unit.

Can the BIU be read by the OBDII?

A while back, I remembered reading about some etc files. How were they read?

An ETC ROM is part of the ETC subprocessor, which is another microprocessor on the ECU's motherboard. Colby read them using his BDM interface, which involves opening up the ECU.

The BIU needs to be initialized by the SSMIII whenever it's replaced. That's done via the OBD-II connector.

For the record, the VIN on '05+ is stored in the ECU for sure. I purchased a used ECU, hooked it up and used a generic OBD-2 logger to pull VIN, CIN, and CVN. Screenshot of the used ECU from obd-2.com software. This VIN is not the VIN of my car and it is the VIN of the car from where this ECU was pulled. Additionally, this information is NOT contained in the 1mb image that we are flashing. Directly after using the OBD-2 scan tool, I started up ECUFlash and flashed the used ECU.

http://www.bescaredracing.com/sti/ecu/used/used1.JPG

t

Interesting.

The main reason I was asking about this is I'm currently using the Cobb v1 AP that came with my car. I am thinking of ditching the AP but from what I've read Cobb "stock" isn't necessarily the right stock map for my car. I was planning to start with a true stock map, but I didn't want someone else's VIN showing up on my car if I flash their ROM onto my ECU. Sounds like that shouldn't be a problem then.

and somewhat on the subject, does anyone know how ecu swapping affects inspection?
when you go in for inspection does it look for VIN information and report anything back? i'm running a different ecu now (different engine) and am wondering if this is going to throw up a red flag at the DMV at all.

i know that on my 02 usdm wrx, using obd-2.com software (nasioc group buy years ago) i could see my vin as well....

dm

bump this back up-

i have an AF481 (2001 JDM ECU/motor) in a 2004 car. is there a way to get this combo to pass emissions? in MA, the VINs have to match.

Wow, they failed you for the VIN's not matching? We've done a bunch of V7 and V8 swaps with their respective JDM ECUs and they all pass MA inspection. No hookup special deal or anything, just plug 'n go. A lot of early OBDII ECUs don't even contain the VIN, surprising that they look for it at all.

That's good to know. I haven't tried getting it inspected yet, but it's due this month. Before going, I wanted to make sure everything was good. Looks like it shouldn't be a problem.

Thanks!
Mike

Use an OBDII scanner and check for readiness codes. You can have 2 that are not ready as long as no CEL is present. Otherwise it should be good to go.

The number of Not Ready monitors allowed depends on model year. I think, for his model, that only a single Not Ready monitor is allowed. On the other hand is JDM ECU might only support a single monitor.

This seems contradictory. But my question is it safe/anonymous to post your whole rom?