Internal DME Faults

[TheMtrez]

Has the car been able to complete the monitor and set a CEL ? If so then you know at least it’s capable of completing the monitor.. my car has aftermarket cats , and they’re a pain in the ass to get to pass the cat monitor ..

[Slideways]

Read the DME the other day using karter16's new tool and the DME (HP) is showing shadow faults 89 (slave) and 99 (master) that will not clear. Any suggestions on permanently clearing these shadow codes?

Details
Fault number: 99 (0x63)
Fault: Master safety concept test fault
Frequency counter: 0
Logistics counter: 0
Error type interpretation:
- Fault type decoding: implausible / overtemperature - Measured value monitoring - Electrical output-stage diagnosis
- Fault sporadic - Fault was at least once temporarily absent

89 is for the Slave safety concept test fault

[karter16]

Read the DME the other day using karter16's new tool and the DME (HP) is showing shadow faults 89 (slave) and 99 (master) that will not clear. Any suggestions on permanently clearing these shadow codes?

Details
Fault number: 99 (0x63)
Fault: Master safety concept test fault
Frequency counter: 0
Logistics counter: 0
Error type interpretation:
- Fault type decoding: implausible / overtemperature - Measured value monitoring - Electrical output-stage diagnosis
- Fault sporadic - Fault was at least once temporarily absent

89 is for the Slave safety concept test fault

These two are test DTCs that are intentionally generated by the CPU as part of continuous testing of the critical functions that support the EGAS safety concept. They are generated as part of two test tasks on each CPU and are used to validate that the error reporting module is functioning correctly.

They will sit there with Frequency Counter: 0 and Logistics Counter: 0 and not much that you can do about it. If you like I can add a setting to allow the app to disregard and not list these two :-)

[Slideways]

These two are test DTCs that are intentionally generated by the CPU as part of continuous testing of the critical functions that support the EGAS safety concept. They are generated as part of two test tasks on each CPU and are used to validate that the error reporting module is functioning correctly.

They will sit there with Frequency Counter: 0 and Logistics Counter: 0 and not much that you can do about it. If you like I can add a setting to allow the app to disregard and not list these two :-)

Since it is only a shadow code, I don't mind scrolling past it. I was just wondering if terra or someone else had seen these errors and had a way to correct it maybe with a full flash or something.