Diagnostic Input Types

MechIQ diagnoses from several kinds of input. The more you give it, the better the answer. Where each one lives:

Input On a job (browser) On a job (native app) Standalone Diagnostics
Fault codes Diagnose → Fault Codes + → Diagnose Yes
Symptoms Diagnose → Symptoms + → Diagnose (type or dictate) Yes
Scan PDF Diagnose → Upload PDF, or emailed in -- (email it in) Native app only
Photo / video Photo → Snap for AI + → Diagnose → photos and a clip Native app only
Customer's answers Feeds the briefing automatically Feeds the briefing automatically --

Fault codes

OBD-II or manufacturer codes, several at once. The AI analyses them together and finds what is related.

  • P0171 -- system too lean
  • P0300 P0301 P0304 -- random misfire plus cylinder-specific misfires
  • P0299 -- turbo underboost
  • B1234 C0561 -- body and chassis codes from a manufacturer tool
  • U0100 -- lost communication with the ECM

Enter every stored code, not just the one you think is the main issue. Related codes share a root cause; the AI marks the cascade so you fix one thing, not five.

Symptoms

Plain words. Say when it happens, under what conditions, and what you have already ruled out.

  • "Engine warning light on, rough idle when cold, slight misfire under load"
  • "Pulls to the left under braking, new pads and discs fitted last month"
  • "Intermittent no-start, turns over but won't fire, first thing in the morning"
  • "Loss of power above 3000 rpm, boost gauge normal, no warning lights"

"Car is slow" gets a vague answer; the last example gets a useful one. On the native app you can dictate.

Scan PDF

A report from your diagnostic tool (Snap-on, Autel, Launch and so on), up to 20 MB. The AI extracts every code, the freeze-frame data and the live readings and analyses them together -- more than typed codes alone, because freeze frame (rpm, coolant temperature, fuel trim when the code set) narrows things fast. There is no preview step; the file goes straight to analysis and the briefing regenerates in the background.

Scans can also be emailed to your garage's diagnostic-scan address; MechIQ matches the PDF to the car and runs the diagnosis on the job. See Job Assets and Scans.

Photo or video

Wear patterns, leaks, damage, corrosion, wiring -- things a picture shows better than words. Add a short description; the AI uses both.

  • Brake disc + "uneven wear on front left"
  • Engine bay + "coolant leak near thermostat housing"
  • Connector + "intermittent fault, found this corroded"
  • Belt + "squealing on cold start, is this belt gone?"

See Snap for AI.

The customer's answers

On a diagnostic job the customer may have filled a short symptom questionnaire from their tracking link, or the desk filled it with them, or the answers came from the diagnostic enquiry form sent before the booking. Those answers feed the briefing and the first diagnosis automatically. See Customer Symptoms.

Combining inputs

Standalone Diagnostics takes one input type at a time. A job accumulates them: the booking symptoms, the customer's answers, a scan you upload, codes you enter, photos you snap -- each Diagnose run works from the job as a whole. Enter all the codes, add the symptom description, and upload the full scan if you have it.