Chapter 5: A Scanner Is Not a Mechanic

Comparison of what a scanner can help with, cannot prove and must not authorize a renter to do.

The approval email answered whether Katie could use the scanner. It did not answer whether she would understand what appeared on the screen.

She opened the app at home and found rows of abbreviations: DTC, MIL, ECT, STFT, LTFT, MAP, RPM and control-module voltage. Some values would be available on almost any modern gasoline vehicle. Others depended on the chassis, the app and the adapter. A few menu items described systems the Chevrolet motorhome might not expose to that setup at all.

The display looked authoritative because it contained numbers. Katie reminded herself that a number can be precise and still be misidentified, unsupported or irrelevant to the decision in front of her.

She built a smaller mental model.

What ordinary OBD-II is designed to do

US OBD requirements focus on emissions-related powertrain systems. The vehicle monitors specified components and operating conditions, stores diagnostic information when its criteria are met and can illuminate the malfunction indicator commonly called the check-engine light. A compliant scan tool can request standardised information such as diagnostic trouble codes, monitor status, selected live parameters and freeze-frame data. [8]

That is valuable, but narrower than the phrase "computerised vehicle" suggests.

A generic scanner may help Katie see:

Whether the malfunction indicator is commanded on.

Stored, pending and sometimes permanent powertrain codes.

Readiness-monitor status.

The snapshot of selected conditions captured when certain faults were stored.

Supported live parameters such as engine speed, coolant temperature, calculated load, fuel trims or control-module voltage.

Availability varies. The app must ask the vehicle what it supports rather than assume every item in its menu applies.

What "enhanced" can mean

Some adapters and apps advertise manufacturer-enhanced access. That may include additional modules, codes or parameters beyond generic emissions data. It does not create universal access to every system on every model year. Coverage can differ by vehicle, engine, network and software version.

Katie's rule was simple: enhanced access was a capability to verify, not a promise to repeat from advertising.

She had supplied the exact product information to the rental company. At pickup, she would allow the app to identify supported items while parked. If the app displayed an unfamiliar manufacturer-specific parameter, she would not make a travel decision from that value until the fleet mechanic confirmed its meaning.

The house behind the chassis

Boundary between chassis OBD-II data and RV coach or house systems.

The Coachmen motorhome contained systems that did not belong to Chevrolet's emissions-related OBD environment:

House batteries and their charging equipment.

Shore-power connection and power converter.

Inverter and solar equipment, where fitted.

Generator controls.

Refrigerator, furnace, roof air conditioner and water heater.

Fresh, grey and black water systems.

Tank-level sensors.

Awning, steps, slide-outs or levelling equipment, where fitted.

Some modern RV components communicate over RV-C, an RV-specific CAN-based network developed to improve interoperability among coach systems. RV-C is not the same as generic OBD-II. [9]

Katie wrote a sentence on the first page of her scan log:

The scanner is a chassis window, not an x-ray of the whole motorhome.

If the refrigerator stopped cooling, the OBD app was not the first place to look. If the engine's malfunction indicator illuminated, the house control panel was not a substitute for the chassis instructions.

A code describes a detected condition

Diagnostic chain from symptom and code through professional testing, repair and verification.

The most important technical lesson was also the shortest:

A code is not a parts order.

A code associated with an oxygen-sensor signal did not prove the sensor itself had failed. Wiring, connectors, exhaust leaks, mixture problems and other conditions could influence what the computer observed. A catalyst-efficiency code did not prove the catalytic converter was blocked. A random-misfire code did not prove the fuel was bad. A low-voltage code did not prove the alternator needed replacement.

The code told Katie where the vehicle's monitoring logic had detected a problem. Symptoms, related codes, freeze-frame data, tests and manufacturer procedures were needed to determine cause.

This is why the rental company's technician remained central. Katie could reduce ambiguity in the first report. She could not turn a phone description into authority to repair.

Stored, pending and permanent are different

Meaning of pending, confirmed or stored, and permanent diagnostic code status.

Katie practised distinguishing three categories.

Pending code: The monitor has detected a condition that may need to occur again before the malfunction indicator is commanded on. A pending code can disappear if the condition does not repeat, or mature into a stored code if it does.

Stored or confirmed code: The vehicle's criteria for recording the fault have been met. Depending on the fault and monitoring logic, the malfunction indicator may be illuminated.

Permanent code: Certain emissions-related codes remain available after clearing until the vehicle itself confirms through monitoring that the fault is no longer present. The point is to prevent erased evidence from masquerading as repair.

Katie did not need to memorise every rule behind these categories. She needed to preserve what the vehicle reported and avoid changing the record.

Why clearing a light could cost time

The expert notes Katie had first received called code clearing a quick fix. The more she learned, the more misleading that phrase became.

Clearing a code does not repair the condition. It can erase freeze-frame information and reset readiness monitors. An extinguished light after a reset can return when the vehicle reruns the monitor. For a renter, clearing also removes evidence the owner or technician may need.

The Chevrolet manual explains that critical emissions monitors may show incomplete after the battery has been disconnected, run down or recently serviced, and that routine driving may be required before the vehicle becomes ready for an emissions test. [10]

Katie therefore treated Clear as an owner-controlled function, not part of her routine.

The dashboard remains first

Warning-response priority: dashboard, safe stop, owner or roadside channel, then scanner evidence.

The scanner did not outrank red warning lights, gauges, messages, sounds, smells or vehicle behaviour.

If oil pressure disappeared, the engine overheated, the brake warning appeared, smoke developed, fuel was smelled, the vehicle shook severely or steering and braking changed, Katie's first task was not to improve the quality of her screenshot. It was to move to safety as conditions allowed, shut down when instructed and contact assistance.

The Chevrolet manual distinguishes a steady malfunction indicator from a flashing one. A flashing light can indicate a fault capable of damaging the emissions system; the manual instructs the driver to reduce speed, avoid hard acceleration and uphill grades, and stop safely if flashing continues. [11] Rental-company instructions could be more conservative.

No app interpretation could weaken that warning.

Where AI fits

AI remained useful. Katie could ask it to translate "Bank 1" into plain language, explain the difference between stored and pending, or help organise questions for the fleet mechanic. She could paste a code description and ask for categories of possible causes.

She would not ask AI to declare the vehicle safe to drive. AI could lack the exact service information, receive incomplete data or misunderstand a parameter. It also could not smell fuel, feel brake-pedal changes...

This curated preview is provided for personal reading. Copyright remains with Nobo Astoria.