Chromed ECU: OBD2 Inspection Monitors Override Not Working

[brandon303]

Hi there,

I recently purchased a 99 3000GT VR-4 which has some basic bolt-ons and is running Chromed ECU.

I have been playing with the OBD2 Inspection Monitors following the documentation on the chromedecu website and have flashed my car with several different configurations, and no matter what I do, the items which I have forced to complete still show up as incomplete.

A few things to note:

- I disconnected the battery before I did these flashes to connect a battery tender harness to plug my battery tender into this car.
- I have driven 0 miles since disconnecting the battery
- To test this, after I flash the ECU, I turn the ignition off for 15 seconds, then turn it back on and check the monitors with EvoScan.
- I also tried firing up the engine for a bit and still have the same result.

I can figure how how to post the ROM I'm trying to flash if needed. Here is a screenshot of how those things are set:

ecuflash-obd-monitors.jpg

Here is the EvoScan logger output after flashing this config:

2016-03-28 19_12_48-EvoScan v2.9.0100 - CAN_OBDII_MUTII_MUTIII_OBD1_ALDL_SSMI_SSMII DataLogger -.jpg

Any ideas on why it's still not working?

[Greg E]

Flash hen start the car so the values get written to RAM. Should work after that.

[brandon303]

Flash hen start the car so the values get written to RAM. Should work after that.

Thanks for the reply Greg. I gave that a try and it didn't change anything unfortunately.

Just to be explicit-- the ignition key was on, I reflashed, then started the car. Same result in Evoscan. I then turned the car off, waited 15 seconds, then back to the on position without starting again, same result.

[brandon303]

Sorry, I just thought of one other thing I didn't think about mentioning until now. The way I've went about this was reading the previous owners ROM and just making the changes as seen above. As far as I know it was a Chromed v2.0 tune, but I'm sure it's probably a few minor revisions behind of the latest at least.

Is it possible I need to do something like copy the changed values from my current ROM to the latest version of Chromed? If so, is there a link anywhere for how to do that? I have been looking and haven't found anything.

[Greg E]

There's only been one revision and that was to fix the reversed active exhaust bit.

It looks like you're only having issues with the O2 sensor portion (remember you want the monitors to be 0 for complete not 1). can you post a screen shot of your peripheral setup?

[brandon303]

There's only been one revision and that was to fix the reversed active exhaust bit.

It looks like you're only having issues with the O2 sensor portion (remember you want the monitors to be 0 for complete not 1). can you post a screen shot of your peripheral setup?

The cat monitoring at the very bottom of that screenshot is also not completed. Those are the two I'm looking to be marked as completed.

Since my original post on this topic, I did flip the "ALL OBD2 DTC Lookups" to off as you will see in this screenshot, but it was set to on when I captured the above screenshots.

ecuflash-per01.jpgecuflash-per02.jpg

[Greg E]

I'm honestly at a lose here. When you set OBD force monitor 1 to 0x00, you are literally setting all of the monitors to complete as shown in the table. That byte is then the exact byte that gets read by EVOScan and any OBD2 scanner.

So for whatever reason, that value isn't getting transferred up into RAM from ROM.

[brandon303]

I'm honestly at a lose here. When you set OBD force monitor 1 to 0x00, you are literally setting all of the monitors to complete as shown in the table. That byte is then the exact byte that gets read by EVOScan and any OBD2 scanner.

So for whatever reason, that value isn't getting transferred up into RAM from ROM.

Thanks for the help.

Would it make sense to try and set something that is similar yet unrelated and see if the same thing is happening? If so, any suggestions?

What I'm getting at.. is it possible this could be a symptom of an ECU going bad?

[Greg E]

No the only way it would be "bad" would be if it bricked. The symptoms of a bricked ecu only show when you reach the area of the code in the bad sector. Usually the motor just doesn't start when that happens.

Unless you're not actually writing to the chip. Sometimes people confuse "test write" with "write" in ECUFlash and the new ROM isn't actually written to the chip.

[brandon303]

No the only way it would be "bad" would be if it bricked. The symptoms of a bricked ecu only show when you reach the area of the code in the bad sector. Usually the motor just doesn't start when that happens.

Unless you're not actually writing to the chip. Sometimes people confuse "test write" with "write" in ECUFlash and the new ROM isn't actually written to the chip.

Just as a last resort, I made a video detailing my setup and walk through reading from the current ROM, flashing a new one, etc. to see if there is something I'm doing wrong. Sorry for the long boring video but I'm hoping there is something I'm doing wrong.