{"id":112511,"date":"2026-02-09T13:07:04","date_gmt":"2026-02-09T13:07:04","guid":{"rendered":"https:\/\/knowledge.ramtechglobal.com\/?page_id=112511"},"modified":"2026-03-03T10:02:43","modified_gmt":"2026-03-03T10:02:43","slug":"thermocable-and-ramtech-troubleshooting-quick-guide","status":"publish","type":"page","link":"https:\/\/knowledge.ramtechglobal.com\/fr\/thermocable-and-ramtech-troubleshooting-quick-guide\/","title":{"rendered":"Thermocable and Ramtech Troubleshooting Quick Guide"},"content":{"rendered":"


<\/span>Troubleshooting Quick Guide
<\/span><\/h3><\/div>
<\/div><\/div>

\nThermocable + Ramtech<\/strong><\/p>\n

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.<\/p>\n

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.<\/p>\n<\/div>


<\/span>Troubleshooting Matrix
<\/span><\/h5><\/div>
<\/div><\/div>
<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
What you see<\/th>\nWhat it means<\/th>\nWhat to check first<\/th>\nNext action<\/th>\n<\/tr>\n<\/thead>\n
ALARM<\/strong><\/td>\nOverheat detected on linear heat detection cable<\/td>\n\n
    \n
  • Note displayed distance to activation point<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Follow site fire procedure<\/li>\n
  • Verify area visually or via CCTV<\/li>\n
  • Arrange replacement of activated cable section<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
ZONE FAULT<\/strong><\/td>\nCable integrity fault<\/td>\n\n
    \n
  • Visible cable damage<\/li>\n
  • Loose terminations<\/li>\n
  • End-of-line resistor present and secure<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Rectify if obvious<\/li>\n
  • Escalate if fault persists<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
I\/F FAULT<\/strong><\/td>\nSignal instability or interference<\/td>\n\n
    \n
  • Junction boxes and glands<\/li>\n
  • Moisture ingress<\/li>\n
  • Loose or intermittent connections<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Secure connections<\/li>\n
  • Remove moisture sources<\/li>\n
  • Escalate if unresolved<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
RLY FAULT<\/strong><\/td>\nThe unit monitors for relay faults<\/td>\n\n
    \n
  • Relay does not switch state<\/li>\n
  • Check Zone connection inside DSCU<\/li>\n
  • Moisture ingress<\/li>\n
  • Loose or intermittent connections<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Secure connections<\/li>\n
  • coil failure<\/li>\n
  • Escalate if unresolved<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Alarm on DSCU-EN but no WES3 alarm<\/strong><\/td>\nAlarm output not reaching WES3<\/td>\n\n
    \n
  • DSCU-EN output wiring to WES3 Interface<\/li>\n
  • Correct input mapping<\/li>\n
  • Correct output used in interlock mode<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Correct wiring or mapping<\/li>\n
  • Escalate to system engineer if required<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
WES3 alarm active but no REACT alert<\/strong><\/td>\nRemote escalation not triggered<\/td>\n\n
    \n
  • REACT routing rules<\/li>\n
  • Time-based escalation settings<\/li>\n
  • Network connectivity<\/li>\n<\/ul>\n<\/td>\n
\n
    \n
  • Correct configuration if authorised<\/li>\n
  • Escalate to REACT administrator<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
Repeated faults after rain or cleaning<\/strong><\/td>\nLikely moisture ingress<\/td>\n\n
    \n
  • Junction boxes<\/li>\n
  • Cable glands<\/li>\n
  • Low points in cable routing<\/li>\n<\/ul>\n<\/td>\n
\n