Methodology

Every technical statement is traced to a source, and sources are ranked:

• Manufacturer official documentation — installation, user and service manuals.
• Manufacturer support centre articles and official troubleshooting pages.
• Authorised technical documentation.
• Reputable technical service references.
• Community reports — accepted only as supplemental context and never to override documentation.

A record cannot be marked verified without a source attached to it. Where no documentation could be found, the page states that plainly instead of guessing.

Codes are recorded against the narrowest device scope we can confirm — model, then product family, then brand. A code confirmed only at brand level is labelled as such, and pages never imply that a code applies to every model of a brand.

Each fault carries a safety level and a technician requirement:

• General — visible, external checks only.
• Electrical caution — isolate at the breaker before inspecting connections.
• High voltage — do not open covers or access internal wiring unless qualified.
• Technician only — user troubleshooting stops here.

Safe checks are deliberately limited to low-risk actions. We never instruct readers to open high-voltage enclosures, bridge components, defeat isolation or work on live wiring.

Editors can add causes, safe checks, technician actions, symptoms, related codes and sources. Every change is recorded in an internal audit log with the previous and new value, together with who made the change.

A duplicate-code check runs whenever a code is added: if the same code already exists for another product family, the editor must decide whether the meaning is the same, different, or applies to an additional model. This prevents one meaning leaking across a whole brand.

“Last verified” is the date the record was last reviewed against its source document. It is not moved when a page is edited for spelling or layout. If a source link stops working, the record is flagged for review rather than silently deleted.

Every fault page has a “Report an error” form that pre-fills the page address and code. Reports are stored for editorial review. If a correction changes a technical statement, the record is re-verified and the verified date moves.

We do not reproduce manufacturer manuals. Records store short factual summaries, the document title, the version, the relevant section or page, and a link to the official source so you can read the original.