FFileTiny

AI VEHICLE FAULT TRIAGE

AI fault triageAssess the risk first.Then decide whether to keep driving.

Abnormal noise, vibration, leakage or other abnormalities can be directly described without a fault code. AI will combine the vehicle model, power type, mileage, fault occurrence conditions and recent maintenance records to first classify risks and then sort out the key points for inspection and maintenance communication.

One important principle

A trouble code identifies an abnormal condition detected by the vehicle. It does not prove that a specific part has failed. OBD data is diagnostic evidence, not a final diagnosis.

✓ Works without a trouble code✓ Stop-driving warnings come first✓ Causes are ranked, not overstated
Model and powerCurrent mileageFault light/OBD code Abnormal noise/vibration/liquid leakageoccurrence conditionsRecent maintenance
AI

AI fault triage

Risk assessment · Follow-up questions supported

Free
No vehicle profile loadedOptional: model, mileage, and maintenance history make the triage more reliable.

You do not need a trouble code to start. Describe what feels wrong—for example, “I sometimes hear a noise when releasing the brake.”

If you have a warning light or OBD code, include it along with when the symptom occurs, the current mileage, and recent repairs. It is fine to say “I don’t know.”

Please do not fill in your mobile phone number, license plate, or VIN; even if you fill it in, it will be automatically hidden before sending.

WHAT YOU GET

A preliminary screening to sort out six key pieces of information

01

Urgency

Make it clear to stop immediately, inspect as soon as possible or observe; safety related signals always take priority.

02

Possible cause sequence

Use "more likely, possible, need to be eliminated" to express the relative order and do not falsify the precise probability.

03

Car owner safety self-examination

Only observation items that do not require disassembly, contact with high temperatures, high voltage electricity and leaking liquids are listed.

04

Maintenance shop key inspections

Organize communication checklists such as freeze frames, live data, electrical, pressure or mechanical inspections.

05

Approximate cost range

Estimates are based on preset maintenance project intervals, and AI guesses are not regarded as quotations.

06

Must be professionally confirmed

Make it clear which conclusions must be confirmed by manufacturer's information, professional equipment and actual testing.

COMMON OBD CODES

Common OBD trouble codes

If there is a code, you can check it first to determine the meaning; if there is no code, just describe the symptoms above.

BEFORE CLEARING CODES

Before clearing the code, save the diagnostic evidence first

  1. Save all code reportsInclude the current code, the pending code and the permanent code. Don’t just record the first one.
  2. Save freeze frameRecord the rotation speed, load, water temperature, vehicle speed and fuel correction when reporting the code.
  3. Record fault light statusSteady light and flashing represent different risks, while recording jitter, abnormal noise, odor and power changes.

OBD FAQ

OBD trouble code frequently asked questions

Can a trouble code identify a failed part?

No. A code identifies an abnormal system, monitoring condition, or signal relationship. A diagnosis also needs related codes, freeze-frame data, live data, and physical testing.

Can I still drive it if the engine check light is on?

Stop the vehicle when the fault light flashes or is accompanied by severe shaking, sudden power drop, excessive water temperature, smoke or strong odor. When it is always on and running smoothly, it is only recommended to be cautious and take a short trip for inspection.

Why is it not recommended to clear the code immediately?

Clearing the code or powering off may clear the frozen frame and part of the self-learning information at the same time, making intermittent faults more difficult to reproduce. Diagnostic information should be saved completely first.