DiagnosticsEvery plan
The fault code is the easy part.
Anyone can look up what a code is called. Lyxter answers whatever comes up at the machine: where a part sits, a symptom with no code, what the manual says, the facts on this vehicle, and what a code means on this machine. It ranks what to check first, says whether the vehicle should still be moving, and remembers the job. On every plan, in the bay and at the roadside.
An illustration of one diagnosis: a mechanic reports fault code SPN 3251 FMI 0 with a derate; Lyxter shows the five steps it worked through, including checking the code, the workshop's manuals and the vehicle's history; then answers with a Critical severity call, a plain-language explanation and a ranked most-likely cause, above buttons asking whether the fix worked.
What Diagnostics does.
A senior technician's instinct on every bay, including the bays where the senior technician is not standing.
- Any question, not only a code
- Ask it the way you would ask a colleague: where something sits on this machine, what a noise under load points at, which part that is, what the manual says, what this vehicle is fitted with. Fault codes are one question among many, and a machine with no fault code system is worked from the symptom.
- Where it looks
- The Lyxter knowledge base of real problems and the fixes mechanics confirmed worked, your own manuals, the web, and the machine's own record: its earlier chats and cases, its services and its readings. Your own material comes first, and Lyxter judges the best source per question rather than following a fixed order.
- Point at it on a photo
- Send a photo and ask where a part is, and Lyxter marks it on the photo with a numbered box and names each one. It marks only what it can see and confirm, and says which it could not. The marks show in the browser; the iPhone and iPad app says it in words for now.
- Reads what your tool put on screen
- Photograph the fault screen from Jaltest, Texa, Autocom, Delphi, Bosch, WABCO or an OEM tool and Lyxter reads the codes off it. Up to eight photos on one message, PDF documents too, and they all stay with the case.
- Causes ranked, not a definition
- A code list tells you what a code is called. Lyxter tells you which causes to check first on the machine in front of you, in what order, and what would rule each one out.
- A severity call on every diagnosis
- Critical, Warning or Info, first thing on the first line, and re-assessed on every reply as the picture changes. On a machine you keep in Fleet, a critical or warning call also flags the machine and opens an issue on it.
- It says what an answer rests on
- What a code means on your brand and model is stated as fact only when something backs it: reviewed knowledge, one of your own manuals, or that machine's history. Where nothing does, Lyxter says the meaning is unconfirmed for this machine and names what would settle it, rather than guessing convincingly.
- Your workshop's own memory
- The AI searches your company's earlier chats and its recorded cases, matched on the machine or on the fault code, and answers with what your shop already found. Cases belong to the workshop, so any mechanic can pick up a colleague's diagnosis mid-job. Only ever your company's work, never another workshop's.
- Your manuals, reviewed before use
- Upload the workshop's library, or the manuals for one machine so they are used on that machine only. Lyxter staff review each upload before the AI may use it, and an approved manual stays private to your company.
Included on every plan. A plan is sized by its diagnostics: 10, 30 or 50 a month per user, shared by the whole company. Lyxter does not order parts, and it does not plug into your diagnostic tool: it reads what the tool shows you.
Severity
Every diagnosis opens with the call.
At six in the morning with a driver waiting, the first thing you need is not the cause. It is whether the vehicle moves.
- Critical
Stop the vehicle now. Risk of engine damage, component failure or a safety hazard, or the vehicle has gone into derate.
- Warning
Drivable, but it must be checked soon: a circuit fault, a failed sensor, an emissions fault that is not limiting power yet.
- Info
Minor. No immediate risk, and it can wait for the next service: an intermittent fault, a comfort system, a stored code that is not active.
Formats it reads
- J1939 SPN + FMI
- OBD-II P / C / B / U
- Volvo MID / PID / FMI
- Fendt and AGCO alpha-numeric
- Plain symptoms, no code at all
Manufacturer codes mean different things on different machines, so Lyxter will not read an E-code off a J1939 table and call it a diagnosis. It gives you the part it can defend, says the rest is unconfirmed for this machine, and names the one thing that would settle it.
The stack
Under the answer, seven layers.
The Lyxter dOS, in short: how a general-purpose model becomes a mechanic's assistant. Skip it if you only care that it works.
Large Language Models
Lyxter is model-agnostic, selecting the best model for each task. As reasoning models get better, our agents get better.
Agentic Harness
The orchestration engine that turns a general-purpose LLM into a mechanic's assistant: it works out what is being asked, which sources hold the answer - the Lyxter knowledge base, your manuals, the web, the machine's own history - and what to say first.
Data Foundation
The Lyxter knowledge base: real problems and the fixes mechanics confirmed worked, reviewed by Lyxter staff before they are shared - plus your own. Upload your workshop's manuals, down to one specific vehicle's exact documentation, and Lyxter uses them where they apply.
Context & Knowledge
A frontier model's general knowledge of the trade is the floor, and the sources above are what an answer stands on. On top of that Lyxter keeps learning: completed cases are distilled into general lessons, each one reviewed by Lyxter before the AI may use it, and mechanics confirm with one tap whether a fix worked, so repairs proven on real vehicles outrank plausible guesses. Each vehicle carries its own history into every new case, and a fix that failed on that vehicle is never suggested first again. Your chats and data stay your own - only reviewed knowledge and anonymous worked/didn't-work counts are ever shared.
Diagnostic Capabilities
Fault code interpretation across OBD-II, J1939 (SPN/FMI), KWP2000, UDS. Symptom-to-cause reasoning, guided procedure generation, and a severity call on every diagnosis - Critical, Warning, or Info - so the mechanic knows at once whether the vehicle can stay on the road.
Products & Interfaces
Purpose-built surfaces for every workshop workflow: a chat for any question at the machine, in the bay or at the roadside, on the phone, the tablet or the desk; Fleet with every machine's record, history and schedule; and Service with the checklist and the report. Every chat is shared with the team. Built from the ground up for grease-stained hands and gloves.
Security & Governance
The foundation that makes Lyxter enterprise-ready. Customer data isolation, audit trails, role-based access, EU data residency. Built into every layer, not bolted on.
One loop
Three products, one record per machine.
What one records, the next already knows.
- DiagnosticsLyxter answers the question at the machine and names the likely cause.You are here
- FleetBetaLyxter holds the machine, its history and its schedule.Open Fleet →
- ServiceBetaLyxter runs the work and produces the document.Open Service →
Finish a service on one of your own machines and it lands on that machine's timeline in Fleet. Open a chat on the same machine and the AI answers with that timeline behind it.
Diagnostics, Fleet and Service are on every plan. What you choose is how many diagnostics you need a month.
Stop guessing. Start fixing.
Set your workshop up today, or inquire for a trial with our team.
Take Lyxter with you.
