Turn your vehicle report into a useful AI conversation

Finding a fault code is the start. OBD CAN puts your readings and prepared questions together, so you can ask the AI you already use what to investigate next, add context and keep asking.

  1. Get a report
  2. Copy report + questions
  3. Paste into your AI
  4. Add context and follow up

From a reading to your first question

  1. Connect a compatible adapter and complete the relevant test. Open a result page that offers report copying, or a supported saved report.
  2. Open “More Options” (⋮) on the result page and choose “Copy AI Prompt Template”. The app copies that report and its preset questions together; you do not need to write a prompt from scratch.
  3. Open your usual AI app or website, paste the text and review it before sending. Add the vehicle model, year, engine, symptoms and recent work when relevant. Remove any VIN or other details you do not wish to share.
  4. Continue in the same AI conversation. Ask it to separate observations from possible causes, list missing evidence and explain the next checks. Bring the report and questions to a technician when needed.

The questions are fixed for each report type, rather than selected one by one in the app. OBD CAN prepares the text; you choose and open the external AI yourself. Test availability depends on the vehicle, adapter and your access to the corresponding OBD CAN feature.

Six situations you can follow

Illustrative scenarios, not actual customer repair records. Codes and readings below are example data in the app’s report format. The preset questions are the app’s current wording; replace the examples with your own report.

01 · A warning light and a fault code

The engine warning light has appeared and the result includes a pending P0301. You want to understand the code and what evidence to collect before deciding on a repair.

Use “OBD2 Diagnosis”. Its copied report groups codes as confirmed, pending and permanent, with a count for each. This example has one pending code.

Example report excerpt

# 🚗 OBD2 Vehicle Diagnostic Report

## Confirmed DTCs — 0
None

## Pending DTCs — 1
P0301

## Permanent DTCs — 0
None
See the questions the app includes

Based on the above OBD2 diagnostic report, please help me analyze:

  1. What does each fault code mean and what are the possible causes?
  2. Which faults are the most urgent and need immediate attention?
  3. Are there any relationships or correlations between these fault codes?
  4. What are the recommended repair solutions and estimated costs?
  5. Do these faults affect driving safety? Can I continue driving?

What to get from the conversation

Aim for a short list of possible causes, the evidence needed to distinguish them and questions for a technician. A code alone does not establish which part has failed; an AI answer cannot certify that the vehicle is safe to drive.

Open the test guide

02 · No fault code, but something still feels wrong

You notice intermittent rough idling. A full scan gives you several kinds of data, but some sections have no readings. You want to know what this snapshot can explain and what to record next.

Use “OBD2 Full Vehicle Scan”. Its copied text can include vehicle information, three DTC categories, oxygen sensor tests, system monitor tests and a live-data snapshot. The excerpt below shows only two sections; the actual copied report contains the other sections too.

Example report excerpt

## Oxygen Sensor Monitoring
No data detected

## Live Data Snapshot
- **Engine speed**: 780 rpm
- **Engine coolant temperature**: 88 °C
See the questions the app includes

Based on the above OBD2 full vehicle scan report, please provide a comprehensive analysis:

  1. Based on the test data, can this vehicle pass the annual emissions inspection?
  2. What do the detected fault codes mean? Which ones are most urgent?
  3. Are the oxygen sensor and system monitor readings normal? Any anomalies?
  4. Which live data parameters are outside the normal range? What do they indicate?
  5. Considering all test results, what is the overall health of this vehicle? What maintenance is needed?

What to get from the conversation

Aim for a plan to collect the missing evidence. A snapshot is not a recording of the whole event, and an empty or unsupported section does not establish that a system is healthy.

Open the test guide

03 · Starting feels slow: understand the voltage report

Starting has become less reliable. You complete a battery voltage test and want to understand which measurements matter and what further testing to request.

Use “Battery Test” and follow its engine-off and start instructions. The copied report includes static, minimum and recovery voltage, sample count, duration, a status summary and a sampled voltage timeline. This excerpt shows the three voltage readings only.

Example report excerpt

# Battery Cranking Voltage Test Report

## Current Voltage
- Static Voltage: 12.30 V
- Min Voltage: 9.50 V
- Recovery Voltage: 14.10 V
See the questions the app includes

Above is the battery cranking voltage test data. As a professional automotive technician, please analyze the battery health:

  1. Are the static voltage and minimum cranking voltage within normal range? What is the approximate State of Charge (SOC)?
  2. Is the voltage drop during cranking normal? Is the charging voltage after start sufficient?
  3. Based on this data, how much life does this battery likely have left? What further tests or maintenance are recommended?

What to get from the conversation

Aim for a useful test request, not a battery replacement verdict. Although the preset asks about remaining life, this voltage report cannot establish a precise lifespan or replace a professional battery test.

Open the test guide

04 · Other systems are warning: sort the results by module

A warning from another vehicle system needs investigation, and the standard OBD2 report does not provide enough context. On a supported vehicle configuration, a UDS scan returns a code from one module while another module cannot be read.

Use “UDS Diagnosis” with a supported vehicle configuration. The copied report can include brand and VIN, module read results, diagnostic notes, codes and their status. This excerpt uses two illustrative ECU labels to distinguish a returned code from a read failure; it does not identify a particular vehicle or failed part.

Example report excerpt

# 🚗 UDS Diagnostic Report

## Scan incomplete. Unread or failed modules cannot be considered fault-free.

## Diagnostic module 0x7E0 — Read complete
DTC status mask: 0xFF
- 123456  (Status: 0x09 | Test Failed | Confirmed DTC)

## Diagnostic module 0x7E1 — Request rejected by ECU
DTC status mask: 0xFF
See the questions the app includes

Based on the above UDS diagnostic report, please provide an analysis:

  1. What does each fault code mean and what are the possible causes?
  2. Which faults are the most urgent and need immediate attention?
  3. Are there any relationships or correlations between these fault codes?
  4. What are the recommended repair solutions and estimated costs?
  5. Do these faults affect driving safety? Can I continue driving?

What to get from the conversation

Aim for a clear list of module findings, gaps in coverage and questions for a technician. UDS coverage depends on the supported vehicle configuration and modules actually read. A read failure does not establish that a module has failed, and the scan does not cover every warning on every vehicle.

Open the test guide

05 · Before an inspection: why is a monitor still not ready?

You are preparing for an emissions inspection. The report shows the MIL is off and no fault codes were returned, but a supported monitor is still incomplete. You want to understand what remains unverified.

Use “OBD Inspection Precheck”. The copied report includes the app’s precheck result and rule summary, vehicle identifiers when available, MIL status, fault codes and required-monitor readiness. This excerpt shows status fields only, including one supported but incomplete monitor.

Example report excerpt

# 🚗 OBD Inspection Precheck Report

## MIL Status
🟢 Off

## DTC Count
0

## Required Monitors [✅ Pass]
- **Catalyst**: Not ready

- Required Incomplete Count: 1
See the questions the app includes

Based on the inspection precheck report above, please analyze:

  1. Based on this data, will this vehicle pass the annual emissions inspection? If not, why?
  2. What does the MIL status and DTCs mean? What needs to be done to pass?
  3. Will the incomplete monitoring items affect the inspection? How to make them ready?
  4. What do the detected DTCs mean? What is the repair priority?
  5. Overall, what repairs are needed to pass the inspection? Estimated costs?

What to get from the conversation

Aim to understand the readiness status and prepare the right checks before an inspection. No returned code does not mean every monitor has completed. The app’s precheck is a reference based on its stated rules, not an official inspection result; an AI response cannot guarantee acceptance.

Open the test guide

06 · Fuel use seems higher: check the context before the cause

You feel that fuel consumption has increased. Before attributing it to a fault, you want to understand the recorded fuel figures, engine readings and calculation settings together.

Use “Fuel Consumption Tracking”. The copied report includes instantaneous and available average fuel consumption, speed, fuel used and distance for the session, MAF, RPM, displacement and volumetric-efficiency settings. This excerpt shows an idle reading and selected inputs; a single session does not establish a long-term increase.

Example report excerpt

# 🚗 Fuel Consumption & Engine Data Report

## 瞬时油耗 / Instant Fuel
- 1.1 L/h

## 运行数据 / Engine Data
- 平均油耗 (Average Fuel): 8.4 L/100km
- Speed (Speed): 0 km/h
- 本次消耗 (Fuel Used): 2.16 L
- 本次里程 (Distance): 25.72 km
- 进气流量 (MAF): 3.2 g/s
- 发动机转速 (RPM): 780

## 配置参数 / Configuration
- 车辆排量 (Displacement): 2.0 L
- 容积效率 (Volumetric Eff.): 85.0 %
See the questions the app includes

Above is the real-time fuel consumption and engine data. Please act as a professional automotive engineer and analyze the current fuel efficiency and engine operating condition.

  1. Is the current idle/driving fuel consumption within a normal range?
  2. Based on MAF, RPM and Displacement, is the engine intake efficiency optimal?
  3. Any suggestions to improve fuel economy based on these metrics?

What to get from the conversation

Aim for a comparison plan and a focused list of questions. Fuel figures depend on available readings and configuration; they are not by themselves a fault diagnosis. Avoid universal normal-consumption thresholds or a parts-replacement recommendation based on one snapshot.

Open the test guide

Keep the conversation tied to evidence

Tell the AI what you checked and what changed. After any repair, take another relevant reading or report and compare it with the earlier one. Separate an explanation, a proposed check and a verified repair outcome.

Other reports can start the conversation too

Other supported report pages offer tailored questions for vehicle information, noise, acceleration, Mode 5, Mode 6, oxygen-sensor waveforms and monitor status. These can provide more detail for a specific investigation. Use the report that matches your question; data coverage varies by vehicle and test.

Know what the report and AI can answer

AI can help explain terms and organize troubleshooting questions. It can also be wrong. Preset questions about costs, driving safety, inspection eligibility or battery life are questions, not verified conclusions. Confirm important decisions with the vehicle’s service information and a qualified technician; an AI reply is not a safety clearance, quotation or inspection result.

Copying prepares text on your clipboard. Sending it to an external AI is a separate action you take under that provider’s terms. Review vehicle identifiers and other personal details before sending.