Troubleshooting Quick Guide
Thermocable + Ramtech
This guide provides first-line troubleshooting guidance for Thermocable Linear Heat Detection systems integrated with Ramtech WES3 and REACT. It is intended to support site teams in identifying common alarm and fault conditions and understanding the initial checks and actions required.
Where a condition cannot be resolved through the checks outlined, or where there is any uncertainty, the issue should be escalated in line with the project escalation plan. Any alarm condition must be treated as a potential fire event until confirmed otherwise.
Troubleshooting Matrix
| What you see | What it means | What to check first | Next action |
|---|---|---|---|
| ALARM | Overheat detected on linear heat detection cable |
|
|
| ZONE FAULT | Cable integrity fault |
|
|
| I/F FAULT | Signal instability or interference |
|
|
| RLY FAULT | The unit monitors for relay faults |
|
|
| Alarm on DSCU-EN but no WES3 alarm | Alarm output not reaching WES3 |
|
|
| WES3 alarm active but no REACT alert | Remote escalation not triggered |
|
|
| Repeated faults after rain or cleaning | Likely moisture ingress |
|
|
Troubleshooting FAQs
These frequently asked questions are designed to support site teams and duty holders in understanding common alarm and fault conditions associated with Thermocable Linear Heat Detection systems integrated with Ramtech WES3 and REACT.
An alarm indicates that a fixed-temperature overheat condition has been detected on the linear heat detection cable. This should always be treated as a potential fire event until verified in line with the site fire procedure.
No. ProReact EN Digital Linear Heat Detection cable is non-resettable. Once a section has activated due to overheat, that section must be removed and replaced.
The displayed distance indicates how far along the detection cable the overheat condition was detected.
In interlock mode, alarm output only activates when both zones detect an overheat condition.
An I/F fault indicates unstable or fluctuating signals caused by loose connections, moisture ingress, or cable disturbance.
A zone fault indicates a cable integrity issue such as a break or loose termination.
This may indicate the alarm output is not reaching the WES3 Interface or is misconfigured.
Check REACT routing rules, escalation windows, and network connectivity.
Mechanical damage or incorrect routing near heat sources can cause unintended activation.
No. Alarms must never be ignored. Controls should be implemented in advance in line with the site fire strategy.
Print or save as PDF
Click the button below to open a print-ready version of this page. From there, you can print it or save it as a PDF.