Retrieving and Recording Steering/Suspension Diagnostic Trouble Codes

The short version — Plug in the scan tool and pull every stored, pending, and freeze-frame code from all related modules before you clear anything or touch the battery, because a DTC only points at a circuit — it doesn't name the failed part.

What a DTC actually tells you

A DTC is an alphanumeric code stored by a control module — think EPS (electric power steering), a ride-height or air-suspension module, or an active-suspension module — when a monitored circuit or parameter reads outside its expected range. That code exists to aim your diagnosis at a system or component, not to hand you a finished answer.

This is the fact that trips people up on the test: a DTC indicates a symptom or circuit fault, not a specific failed part. Setting a code for a steering angle sensor doesn't mean the sensor is bad — it means the module saw something wrong on that circuit or with that reading. You still have to run the manufacturer-specified diagnostic steps (pinpoint tests) to confirm what actually failed. Skipping straight to parts-swapping off a code number is not the correct process and is exactly the kind of shortcut ASE questions are built to catch.

The correct retrieval sequence

Retrieving DTCs means accessing stored and pending codes electronically, normally with a scan tool plugged into the vehicle's diagnostic connector — the DLC/OBD-II style connector. This always happens before any physical diagnosis or disassembly. You don't start pulling components or wiggling connectors until you know what the modules are actually reporting.

The standard sequence:

• Connect the scan tool to the DLC.
• Select the correct module — steering, suspension, chassis, or body network, whichever applies to the complaint.
• Retrieve all stored, pending, and freeze-frame data — all of it, not just the first code that pops up.
• Only after that data is pulled and recorded do you consider clearing anything.

Order matters here. Freeze-frame and history data is only useful if it's still there when you look at it.

Recording what you find — and why freeze-frame matters

Freeze-frame or failure record data is a snapshot captured at the moment the code set — things like vehicle speed, steering angle, or ride height at that instant. This data should be recorded, because it's often the only clue you get for an intermittent fault that isn't misbehaving while you have the car in the bay.

Along with that snapshot, document three things for every code before you touch the clear button:

• The exact code number
• Its description
• Its status — active, stored, or pending

This documentation step matters because clearing codes erases this diagnostic history. Once it's gone, you can't get it back — so write it down (or save it in the scan tool session) before you clear.

Protecting the diagnostic history

Two situations will wipe out the very data you need, so both are sequencing traps to watch for:

• Retrieve codes before disconnecting battery power or disturbing wiring. Killing power to a module can clear stored codes and erase the diagnostic history you need for the repair — so battery disconnects and connector unplugging happen after you've pulled and recorded codes, never before.
• Clearing codes (part of the normal workflow) also erases history — that's why full recording always comes first, every time, no exceptions.

Scan every module on the network

On a vehicle where steering, suspension, and ABS/stability control share a network, a fault in one system can set related codes in another module. That means a single scan of "the suspension module" may give you an incomplete picture. All modules should be scanned for a complete diagnostic picture — otherwise you might chase a code in one system when the root cause is sitting in a different module entirely.

Check yourself

Question: A scan tool pulls a stored DTC on the EPS module. What does that code tell the technician, and what should happen next?

The code tells the technician a monitored circuit or parameter was out of expected range — it points at a system or component, not a specific failed part. The next step is to follow the manufacturer-specified diagnostic steps (pinpoint tests) to confirm the actual root cause before replacing anything.

Question: Technician A says you should retrieve and record all stored, pending, and freeze-frame codes before disconnecting the battery. Technician B says it's fine to disconnect the battery first since the scan tool will still read the codes afterward. Who is right?

Technician A is right. Disconnecting battery power (or disturbing wiring) before retrieving codes can clear stored codes and erase the diagnostic history needed for the repair. Codes must be pulled and recorded first.

Question: Why should a technician record freeze-frame data instead of just noting the code number?

Freeze-frame data captures conditions at the moment the code set — like vehicle speed, steering angle, or ride height — and that context is often essential for diagnosing intermittent faults that aren't present when the vehicle is on the lift.