Analyzes cylinder-individual crankshaft acceleration drops, ionization metrics, and Mode test IDs to distinguish ignition breakdown from injector clogging.
05 / 07 — DiagAIAvailable
AI vehicle diagnostics software.
Ask your measurements a question; agents answer from your own data.
Eliminate endless troubleshooting trees. Route vehicle DTCs, freeze frames, and live CAN telemetry through 8 specialized diagnostic agents covering ISO 14229 UDS, OBD-II, J1939, CAN and LIN — deployable fully on-premise, with no data leaving your network.
In pilot with Tier-1 powertrain teams
- freeze frame · 3 480 rpm
- run_07.mf4 · 1 ms raster
- lambda bank 1 lean
Next: swap coils 2↔3, re-run misfire counter
- Protocols
- ISO 14229 (UDS), OBD-II, SAE J1939, CAN, LIN
- Agents
- 8 specialized diagnostic agents
- Local inference
- LM Studio / Ollama-compatible (e.g. DeepSeek)
- Isolation
- Per-OEM RAG index, offline-first
Capabilities
What DiagAI does.
- E1
Multi-Agent Collaborative Reasoning
Misfire, Fuel, Thermal, Combustion, and Bus Integrity agents cross-examine telemetry to pinpoint subtle intermittent faults.
- E2
Protocol-Native Context
Deep understanding of UDS Service $19 (ReadDTC), $22 (ReadDataByIdentifier), snapshot records, and extended freeze frames.
- E3
Signal Intelligence & Alias Matching
Automatically maps proprietary OEM signal names to standardized diagnostic physical channels across legacy DBCs.
- E4
Per-OEM RAG Isolation
Runs on your local workstation or private data center via LM Studio or Ollama-compatible models. Each organization's data and documentation stays in a separate local index.
8-AGENT SPECIALIZED NEURAL REASONING MATRIX
Domain-expert agents running concurrently over ISO 14229 UDS and SAE J1939.
Multi-Agent Diagnostic Specialist Swarm
Rather than relying on a generic LLM, DiagAI routes vehicle telemetry through 8 domain-specialized agents that collaborate in parallel:
Tracks high-pressure fuel rail transients, STFT/LTFT adaptations, and pump duty cycle to isolate pressure regulator wear and fuel delivery anomalies.
Evaluates driving cycle telemetry against WLTP and Real Driving Emissions (RDE) boundaries to flag cycle drift and catalyst light-off delays.
Traverses Diagnostic Fault Code dependency trees, debouncing counters, and ECU healing criteria to separate primary faults from secondary cascade codes.
Audits In-Use Performance Ratios across catalyst, evaporative system, and secondary air monitors for OBD-II regulatory compliance.
Performs acoustic knock sensor window analysis and cylinder ignition retard decay inspection to detect super-knock and pre-ignition risks.
Monitors coolant circuit temperature gradients, electric water pump flow rates, and charge-air cooler effectiveness across ambient extremes.
Inspects upstream/downstream NOx sensor correlation, SCR urea dosing models, and DPF differential pressure soot loading curves.
ISO 14229 (UDS) Protocol Diagnostic Routing
DiagAI interfaces natively with Unified Diagnostic Services over CAN, CAN-FD, and DoIP (ISO 13400):
| Service ID (SID) | Service Name | Standard Function | DiagAI Autonomous Operation |
|---|---|---|---|
0x19 |
ReadDTCInformation | Sub-func 0x02 (ByMask), 0x04 (SnapshotRecord) |
Extracts DTC freeze frames and environmental freeze-frame data tables |
0x22 |
ReadDataByIdentifier | Dynamic DID polling (0x0100 – 0xFFFF) |
Continuously queries high-speed live sensor arrays without bus saturation |
0x2E |
WriteDataByIdentifier | Variant coding and adaptation value writing | Applies safe adaptation resets with automated rollback protection |
0x31 |
RoutineControl | Actuator actuation routines | Orchestrates safe automated component functional test sequences |
Workflow
From input to decision.
- 01
Collect Evidence
Import DTC freeze frames, CAN traces, and driver symptom descriptions into DiagAI.
- 02
Agent Analysis
Specialized agents evaluate evidence simultaneously, calculating fault probabilities and correlating sensor anomalies.
- 03
Prescribe Action
Receive an actionable, ranked root-cause diagnosis and a guided step-by-step physical verification procedure.
Why it exists
The veteran diagnostician embedded in software.
DiagAI does not produce generic chatbot summaries. It performs structured, protocol-aware diagnostic reasoning backed by automotive standards, isolating root causes in minutes rather than days.
Each agent operates on MDF/MF4 signal data and returns structured findings — cross-referencing diagnostic trouble codes against live measurement signals for root-cause analysis.
Agent capability matrix
Eight agents, each with a domain.
Specialized agents cross-examine the same evidence from different diagnostic angles.
| Agent | Diagnostic domain | Protocol coverage |
|---|---|---|
| MisfireAgent | Combustion analysis, cylinder-level anomaly detection | UDS, OBD-II |
| FuelAgent | BSFC / BMEP evaluation, long-term fuel trim, injector health | OBD-II, J1939 |
| WLTPAgent | Emissions compliance, regulatory drive-cycle simulation | OBD-II, CAN |
| DFCAgent | Fault code interpretation, DTCs, OEM-specific DFC logic | ISO 14229 UDS |
| IUPRAgent | OBD-II monitor readiness, in-use performance ratio | OBD-II |
| GearAgent, DrivabilityAgent, StartWarmupAgent | Gear hunting, drivability, start / warm-up | CAN, LIN |
Questions
Asked by engineers, answered plainly.
Which agents handle misfire detection diagnostics, and is there a WLTP data analysis tool?
DiagAI includes 8 specialized agents: MisfireAgent for combustion analysis, FuelAgent for BSFC and BMEP evaluation, WLTPAgent for emissions cycle analysis, DFCAgent for fault code interpretation, IUPRAgent for OBD-II monitor readiness, GearAgent for gear-hunting detection, DrivabilityAgent, and StartWarmupAgent. Each agent operates on MDF/MF4 signal data and returns structured findings.
Can DiagAI run completely on-premise without sending data to the cloud?
Yes. DiagAI supports fully on-premise deployment via LM Studio or Ollama-compatible local LLMs such as DeepSeek. Per-OEM RAG isolation means each organization's data and documentation stays in a separate local index. No data leaves your network unless you explicitly configure a cloud inference endpoint.
Is DiagAI a UDS ISO 14229 diagnostics tool and J1939 data analysis software?
DiagAI supports ISO 14229 (UDS), OBD-II, SAE J1939, CAN, and LIN. It parses diagnostic trouble codes and live signal data across these protocols, then cross-references them with MDF measurement signals for root-cause analysis.
Does DiagAI require an internet connection to function?
No. DiagAI is designed for offline-first operation. All signal parsing, agent inference, and RAG retrieval run locally. An internet connection is only needed if you configure an external cloud LLM endpoint, which is optional.
Next step
Ready to augment your diagnostic lab?
Eight protocol-aware agents, running on your own hardware, reasoning over your own measurement data — with every OEM index kept separate.
Go deeper
Guides and comparisons for DiagAI.
- DiagAI technical briefArchitecture, interfaces and limits, as a web page or a PDF.→
- UDS (ISO 14229)Services, sessions, security access and fault memory.→
- DoIP (ISO 13400)Vehicle discovery, routing activation and logical addressing.→
- SAE J1939PGNs, SPNs, DM1 fault messages and FMI codes.→
- CAPLEvent-driven CAN test scripting, and when Python is the better fit.→
Works with
- 01MDXAlso a fast MF4 file viewer, with a Python SDK and MCP server.↗
- 03CIE ProResponse models from test data, so trade-offs are explored before the dyno.↗
- 02HELIXChange packages, variant compare, validation gates and an audit trail.↗
- 07OrbisThe agentic engineering workspace for calibration, measurement and ECU software.↗
