Prepare an OBD workshop record without clearing codes

01

Aim for a clear record, not a diagnosis by guesswork

Use OBD Studio to prepare information for a workshop while leaving the fault memory unchanged. This guide concerns documentation, not a decision about roadworthiness or a replacement part. Operate the screen only while parked and follow the vehicle handbook. NHTSA's distracted-driving guidance, checked on 22 October 2026, explains why screen tasks should not compete with driving. If warning lamps require action, use the vehicle-specific instructions rather than this generic record-keeping workflow.

02

Separate the demo from the vehicle session

“Try the demo car” is useful for locating the controls without an adapter. Its sample values are not observations of your car. Before saving a real report, verify that the session is connected to the intended adapter and vehicle. A selectable adapter and an answering vehicle are separate things. Keep the displayed connection message with your notes if a scan fails; do not convert a missing reading into zero.

03

Preserve the code and the displayed status

The “Fault codes” view separates stored, pending and permanent groups. Record each complete identifier together with its group. A shortened description can lose information that the technician needs. “Copy codes” copies identifiers and explanations into a combined list, so do not assume the copied text preserves the group labels. Use the diagnosis report or add the status manually beside each code before forwarding the record.

04

Keep context that a code cannot supply

Write down what you noticed, when it happened and what was changed before the scan. Separate your own observation from a theory about its cause. Available freeze-frame data can be noted separately, but the current printable report does not include that view. Missing information should remain marked as unavailable. A workshop can ask for another observation; an invented value in a tidy report is harder to distinguish from vehicle data.

05

Use the report and review its scope

Under “Tools”, choose “Print or save as PDF”. The report contains vehicle details reported in the session, the fault-code groups, available readiness information and a live snapshot when present. It is not a complete recording of the incident or an official inspection certificate. Open the saved PDF, check the vehicle identity and make sure the code list is complete before sending it. Add your separate symptom note rather than expecting the PDF to reconstruct events.

06

Leave the clear operation alone for this task

Recording a result does not require “Clear codes”. Texas DPS guidance, consulted on 22 October 2026, explains that clearing diagnostic codes can reset readiness monitors. The US EPA's OBD guidance also identifies fault codes and associated freeze-frame information as useful diagnostic context. Do not apply Texas inspection acceptance limits in another location. The point here is to preserve information for the technician, not to make an inspection display appear ready.

07

Label successive observations instead of overwriting them

For an illustrative workshop handover, keep one file named with the vehicle reference and scan date, plus a note headed before workshop visit. If another scan is requested, save it as a later observation. Describe any repair or reset between the two rather than interpreting a changed code count alone. Those filenames and dates are examples of organisation, not a claim that a real vehicle was tested for this guide.

08

Share only the record the recipient needs

A report may include the VIN and other vehicle identifiers. Open it before sharing and decide whether the intended workshop needs the entire file. OBD Studio communicates with the adapter directly; the registry says vehicle data is not uploaded to the LoschaZ host. A short per-vehicle scan history remains in the browser until its data is cleared. Downloaded PDFs and CSV files are separate copies and should be handled deliberately.

09

Describe the observation without converting it into a diagnosis

A useful workshop note distinguishes what appeared on screen from what the driver remembers. For an illustrative structure, put the exact code and displayed category on one line, then the observed symptom in a separate sentence. Write that a warning appeared after starting if that is what happened; do not transform it into a claim that a named sensor failed. Keep approximate recollections labelled approximate. The technician can ask for more detail without first undoing a confident diagnosis that the scan never established.

If a second scan is made, keep its date distinct from the first record. A code missing on the second screen does not retrospectively change what the earlier report showed. Equally, an unavailable value should not be filled with a familiar number from a demo or another vehicle. Tell the workshop which information could not be read and whether the connection ended unexpectedly. Follow the vehicle handbook and the qualified assessment for decisions about vehicle use; this record-preparation method supplies no driving clearance. The report's purpose is to preserve evidence for a professional conversation. It should make the limits of that evidence visible, including whether a freeze-frame note was captured separately and whether any clearing operation had already occurred.