Record what happened, when it happened and how the car behaved. Diagnostic equipment can supply evidence, but the repair decision may still need inspection and testing.
Describe the symptom
Note whether the car was cold or warm, moving or stationary, and whether weather, speed or load changed the symptom. Photos or a short recording may help when they can be captured safely.
Diagnostic evidence
Code reading can narrow the search, but wiring, sensors, supply voltage and mechanical conditions may produce related symptoms. A credible route leaves room for tests that confirm the cause.
Safety boundary
If steering, braking, visibility, overheating or control feels compromised, do not rely on an online description to decide whether the vehicle is safe. Stop and seek suitable professional or recovery help.
Repair decision
Once a likely cause is identified, the operator should explain what work is recommended, what remains uncertain and how success will be checked. That creates a clear boundary between diagnosis and repair.
Keep exploring
Questions
Not always. A code identifies a detected condition or system. Inspection and testing may still be needed before a repair is selected.
Avoid clearing it if possible because stored information may help. If you already cleared it, say when and why.
Record temperature, speed, journey stage, weather, load, warning messages and how long the symptom lasts.
A real operator can confirm capacity and parts availability, but diagnosis may reveal a different scope. Treat repair as a separate approval decision.
Stop driving and contact an appropriate garage, recovery provider or emergency service. This demo cannot assess roadworthiness remotely.
Next step
