Glow-worm F70 Fault Code
The Glow-worm F70 fault code means: your boiler's main control board has lost communication with its internal identity chip, effectively meaning the boiler has forgotten which model it is and cannot operate.. It appears on 17 Glow-worm models in our database.
Technical description: PCB personality chip fault
What causes the Glow-worm F70 fault?
This fault occurs when the boiler's main control board loses its connection to the identity chip that tells it how to operate correctly. The most common reason is a hardware failure within the printed circuit board (PCB) or a loose connection to the data chip, often caused by age or electrical wear. In some cases, this can also happen after a replacement part has been installed but not correctly coded to the specific boiler model.
Engineer required
This fault requires a Gas Safe registered engineer. Do not attempt gas-related repairs yourself.
Find a Gas Safe engineer
Search the official register for a qualified engineer in your area.
Gas Safe Register →Avoid the next call-out bill
A cover plan would handle faults like F70: no call-out fees, no surprise bills.
Affiliate links. We may earn a commission at no extra cost to you.
Glow-worm models that show the F70 fault code
Click a model for the full fault code list and model-specific repair notes.
- Betacom2 24
- Betacom2 28
- Easicom 24 Repair: £100-350
- Flexicom 18sx Repair: £250-450
- Flexicom cx Repair: £150-300
- Flexicom hx Repair: £250-450
- Flexicom hxi Repair: £150-300
- Flexicom sx Repair: £250-450
- Ultracom 2 12sxi
- Ultracom 2 18sxi
- Ultracom 2 30cxi
- Ultracom 2 30sxi
- Ultracom 2 35cxi
- Ultracom 2 SXI
- Ultracom 35 Store Repair: £250-450
- Ultracom cxi Repair: £250-450
- Ultracom sxi
Source
Glow-worm F70 fault code information on this page is sourced and cross-checked against the official Glow-worm service / installation manuals for each affected model.
- Glow-worm Betacom2 28 manual (PDF)
- Glow-worm Easicom 24 manual (PDF)
- Glow-worm Flexicom sx manual (PDF)
Reviewed by the BoilerFaultCodes Editorial Team · Last reviewed 31 August 2026