Get the app
← MechaOBD

VEHICLE-SPECIFIC CONTEXT

A code is a clue.
Your car is the context.

Two cars can report the same code for different reasons. MechaOBD brings your vehicle’s details and captured data into the explanation—so your next step starts with the car you actually drive.

See that reasoning in a sample report
01 / CONTEXT

The car it is.

Year, make, model & engine

Your vehicle’s design gives the investigation its starting point. A useful explanation considers which engine and systems are actually in your car.

02 / CONTEXT

The life it has lived.

Mileage, symptoms & past scans

Mileage adds wear and service context. Symptoms and available past scans help put the current concern in perspective. That context helps frame what to investigate.

03 / CONTEXT

What it is doing now.

Codes & captured sensor readings

The Guided Health Check records how your vehicle responds through a sequence of steps. Reading those signals together helps connect a reported condition to a possible cause.

FOLLOW ONE CLUE

What does
P0171 tell you?

The code describes a lean condition: too much air relative to fuel. It doesn’t identify the failed part by itself.

ILLUSTRATIVE WALKTHROUGH · APP DEMO
  1. THE VEHICLE

    Start with the actual car.

    Our sample comes from a prerecorded 2015 Toyota RAV4 capture. Its identity anchors the explanation to a particular vehicle.

  2. THE OTHER CLUES

    Read the signals together.

    The capture also contains P0441 and P0455 fuel-vapor system codes, alongside fuel-trim readings. Together, those clues suggest investigating the purge circuit.

  3. THE NEXT STEP

    Test what the evidence suggests.

    The report explains why the purge circuit is a possible connection and what needs checking. Higher-RPM data was limited, so the suspected component still needs testing.

    Explore the complete example

SEE BEYOND THE WARNING LIGHT

Light off?
There may still be a story.

Some codes stay hidden from view on your dashboard. MechaOBD’s Quick Scan reads stored, pending, and permanent OBD-II codes where your vehicle supports them.

STORED

A recorded fault.

Codes the vehicle has stored after detecting a fault condition. They give you a place to begin investigating.

PENDING

A clue before the light.

A detected condition that may not yet meet the criteria for a confirmed fault. A pending code can appear before the check-engine light turns on.

PERMANENT

A record that can remain.

A code that can remain after the light turns off or a repair is made. The vehicle clears it after its own checks confirm the condition is resolved.

Reading a permanent code doesn’t mean the fault is still active, and an ordinary code-clear command won’t erase it. More about permanent codes ↗

USEFUL CONTEXT. CLEAR LIMITS.

A better question
for the next check.

MechaOBD uses the vehicle information and diagnostic data available to it. Coverage varies by vehicle and adapter, and a report should make missing evidence clear.

Vehicle-specific interpretation helps focus the investigation. It doesn’t guarantee access to every manufacturer-specific module or replace a physical inspection. The report gives you likely causes, supporting evidence, and practical next checks to discuss with a mechanic.

Check vehicle and adapter compatibility

Every car has a story. Understand yours.

Start in your driveway with MechaOBD for iPhone or iPad and a compatible adapter. No appointment needed.

Find your adapter
Get MechaOBD