Original corpus study

How appliance brands document error codes

A reproducible snapshot of FaultCodeLab's source-backed error-code corpus. It shows how manufacturers present codes and their documented scope, so a short display string can be read with the right brand and appliance context.

What this study measures

The snapshot is based on the committed FaultCodeLab record corpus as of. It measures record coverage, source scope, display formats, and repeated code strings.

The page uses static values that are checked against the corpus by a repository test. It is a documentation study, not a diagnosis guide.

Snapshot

  • 249 source-backed error-code records
  • 35 appliance brands
  • 51 brand and appliance pairs
  • 34 manufacturer source hosts

Documented appliance coverage

Appliance typeDocumented records
washer104
dishwasher93
dryer22
refrigerator21
range9

Documentation scope is part of the meaning

These labels describe the boundary stated by a record's source. They do not describe appliance ownership or distribution outside the corpus.

Source scopeRecordsHow to read it
regional87An official source applies to a stated market or region.
exact-model56An official source names a specific model.
model-family51An official source names a model family or series.
broad-appliance29An official source applies at appliance level without a narrower label.
not specified26The current record has no structured scope label.

Short display strings can recur across brands

A shared string is a lookup cue, not a shared diagnosis. Keep the brand, appliance type, spacing, and source scope together before using a record.

Visible codeBrands in this corpus
E36
PF6
E45
E14
E124

Manufacturers use more than one display format

Keep the code exactly as shown when searching. Spaces, hyphens, and grouped characters can be useful context rather than decoration.

Display formatRecords
letters followed by numbers117
other manufacturer display format54
letters only33
spaced or hyphenated groups18
letter-number groups12
numbers followed by letters9
numbers only6

Safety boundaries remain separate

The corpus records whether limited owner-safe checks are appropriate; that status is separate from the code's documented meaning.

  • 198 records: no
    The record keeps the next step with qualified service rather than an owner action.
  • 51 records: limited
    The record permits only bounded owner-safe checks before its service boundary.

Source mix

Every record in this snapshot uses an official source type. The source label supports traceability, while the stated model, family, and region still set the record's boundary.

  • 249 records: official

Inspect the source-backed corpus

Use the dataset for machine-readable records, the methodology for the evidence and confidence rules, and coverage to see the current scope.

Install FaultCodeLab