How clearing of Diagnostic Trouble Codes(DTC) or Fault Codes work in typical embedded systems ?

[jani12]

Let's say application is Third Row Power Folding Minivan seat. User presses a button. Seat starts moving. There is a obstruction which causes DC motor moving the seat to stop turning almost immediately. Embedded controller attached to seat detects a motor stall or block. It activates a fault code. What happens next?

Probably embedded software application won't allow seat to move because there is a fault. How does the DTC clear and what triggers the seat movement again? Usually fault codes are uploaded to CAN based tool. Service Technician sees active DTC. It removes the obstruction. Then, how does the fault code clear? What sequence of steps take place to restore movement of seat?

 

[KeepItSimpleStupid]

Go simpler. A power window. One would not work on a hot day. So, a thermal sensor obviously is used to prevent damage at overloads. Those sensors have to cool.

There is a "driver's down" which is a continuous down. I suspect, it would time out. It might reset on the next ignition try or button try.

Memory seats might have codes that set saying "no movement when commanded to move".
Let's say it hits a thermal. It could reset on the next ignition trial or timeout or both.

"removing power to the BCM" that control that function can "sometimes" clear the fault.

Ordinarily "all faults", but history faults, are cleared through the OBD bus.