Residential gas furnace fault code lookup by brand

What the flashing-LED or displayed fault code on a residential gas furnace's integrated control board means, taken from each manufacturer's own manual. A furnace tech reads a blink pattern or a short alphanumeric code off the control board and needs the manufacturer-specific meaning before touching anything; the code alone (e.g. '13', 'A033_F') means nothing without knowing whose board it is. Codes look alike across brands and mean different things: 13 on a Carrier 58MVP is a limit switch lockout, while e13 on a Trane S8V2 is a blower horsepower or OEM ID mismatch. Each record is one fault code from one brand's control board: the code as the board displays it, and the fault the manual names beside it. The corrective procedure is not reproduced here; the linked manual has it. No single source publishes this across brands because each manufacturer's control board firmware defines its own code set independently.

The data

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 3 sources this dataset was assembled from.

• graycoolingman.comhttp://www.graycoolingman.com/uploads/1/0/6/6/10667336/carrier_variable-speed_2-stage_troubleshooting.pdf
• airmanagementsupply.comhttps://airmanagementsupply.com/documents/rheem-ruud_R802V_UH_installation_instructions.pdf
• elibrary.tranetechnologies.comhttps://elibrary.tranetechnologies.com/public/residential-hvac/Literature/Installation%20Operation%20and%20Maintenance/FNR-SVX003A-EN_10312025.pdf

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup residential-furnace-fault-codes-by-brand brand=Carrier

npx -y refsource lookup residential-furnace-fault-codes-by-brand brand=Carrier

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Residential gas furnace fault code lookup by brand", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `residential-furnace-fault-codes-by-brand`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

79 records. last verified against source 2026-08-28. due for re-check by 2028-08-27.

Licence. factual compilation from manufacturer technical manuals