Diagnostics and trouble codes

Where to find it

Open your build, tap Edit Build, then Diagnostics. You need an adapter connected to the car. Set one up on the OBD2 page first.

Connect first

The top card shows your status: Not Connected, Connecting..., Bluetooth Connected, Adapter Ready, or Connected. Use Connect, Cancel, or Disconnect.

Scan for codes

1. Turn the ignition on and connect.
2. Tap Scan All Codes to run all three scans, or run them one at a time under INDIVIDUAL SCANS.

• Active Codes (Mode 03): what's behind your check engine light.
• Pending Codes (Mode 07): may trigger soon.
• Permanent Codes (Mode 0A): "Cannot be manually cleared".

Found codes show a banner like 2 Trouble Codes Found with counts, then each code with its description and reporting ECU. Nothing found shows All Clear and Scan Again.

Open a code

Tap a code to see its ECU, Description, and Recommendations. While you're connected, it also has Freeze Frame Data: a snapshot of sensor values from when the code was set.

1. Tap Load Freeze Frame Data.
2. PitStop checks common sensors: RPM, speed, coolant temp, intake air temp, throttle, engine load, MAF, and intake manifold pressure.
3. Tap one of the readings your car answers for to see its value under Raw Data.

If none respond, you'll see No freeze frame data available for this code.

Clear codes

When connected and codes are found, a red Clear Codes button appears next to Export. Confirm in Clear Trouble Codes? with Clear. PitStop then rescans Active and Pending codes.

If the car refuses, you get an Error alert, with Help when PitStop has fixes to suggest.

Export a report

Export opens the share sheet with a plain-text "OBD-II Diagnostic Report": time plus active, pending, and permanent codes.

O2 sensor tests

When connected, expand O2 Sensor Tests (Mode 05). Tap one of four sensors (Bank 1 or 2, Sensor 1 before the cat or Sensor 2 after) to send the test.

When something goes wrong

Tap Help on an error to open Error Help: what happened, why, and what to do. Common causes are Bluetooth off, the adapter losing power, or the engine not running.

Codes seen on a drive

On an OBD drive, PitStop checks for trouble codes about once a minute and records when they appear and clear. No manual scan needed.

Open a past drive and find Diagnostic Trouble Codes. A line under the title says how the check went, for example No codes were reported by the responding control units or Diagnostics were not checked for this drive.

Tap a code to see:

• Present at the end or Cleared during the drive.
• What PitStop observed: when it appeared and cleared.
• Around the first appearance: the closest readings. Context, not proof of cause.
• Build context from your build.