How this reference is built
14,984 fault-code pages across ABB, KUKA, FANUC and 74 spare-part pages. This page explains where the data comes from, what we will and will not reproduce, and how quality is enforced — so you can judge how much to trust what you read here. · D'où viennent les données, ce qui est verbatim, comment la qualité est verrouillée.
Where the data comes from
The corpus is field-curated for LogrobotLM: diagnostic write-ups drafted in-house from real troubleshooting practice, a structured hardware fault base (component, cause, actions, severity, controller generation — each entry carrying its source), and the production diagnostic engine that analyses robot backups. English page content is generated from these structured fields, never translated out of a manufacturer manual.
What is verbatim — and what never is
Part references and designations (DSQC 572 « DeviceNet Board », KPP, A06B-…) are reproduced exactly as the manufacturer names them: they are factual identifiers a technician must be able to match character-for-character when ordering. Everything else — causes, checks, remedies — is our own wording. No manufacturer manual text is copied; manual document numbers are never mistaken for part references (enforced by test).
How quality is enforced
- No empty templates: a page exists only when it carries distinct data; symptom and part hubs have minimum-content floors.
- Brand partitioning: an ABB reference can never leak onto a KUKA or FANUC page — locked by automated tests on every change.
- FAQ answers are extracted from page data and shown visibly on the page — never invented.
- Every change passes type-checks, >1,700 automated tests and a full build before publication; each page carries its dateModified.
Limits, safety and corrections
This is indicative field information: your robot's own manual and safety procedures always prevail, and the real cause on your robot is confirmed against its own backup — that is what the free browser-based diagnosis is for (the backup never leaves your PC). Spotted an error on a page? Report it via the site contact — corrections ship in the next update cycle.