[Ultramaroon]

Originally Posted by kinghurl

The tech bulletins indicate that it could take up to 5K miles to relearn fully. Most folks aren't willing to wait that long to have car back to full function. This suggests that it will eventually relearn. Dont know of anyone who's done it successfully. Hopefully someone here will chime in.

I believe that statement is the estimated time for a new ecu to tune its valve timing servo to that specific engine. In order for an iteration of the tuning algorithm to update the values in that table, it must receive an 'ok' value from the system startup diagnostic.

The values in that table are part of that init calculation. One thing that can be inferred is that it may have taken up to 5000 miles before ECU eventually pegged itself trying to compensate for the root fault.

The trick is to catch the fault before the ECU drives a value in the init table so far that, should the fault suddenly be corrected, the startup diagnostic still returns an acceptable value for the "ok" flag. This is why I was thrilled when OBDLink added the VVT params to their software.

Originally Posted by Ultramaroon

I recommend this $70 device and using its proprietary application that I demonstrated here. A $5 in-app purchase gets you the extended monitors. I'm not aware of any other real-time monitor but hope to eventually see it cracked for OpenPort II.

Watching the valve timing slew will give you peace of mind as you cross your fingers and wait for the ECU to re-learn whatever offset it needs. Maybe the offset is represented by one of the mystery values I am logging here. That would be cool.