Quick answer
An offline indication generally means the controller is not receiving the expected communication from an identified detector, but its exact meaning depends on the system manual. Possible review areas include power, communication wiring, addressing, settings and equipment compatibility. It is not a gas-free reading. Report the affected monitoring point under site procedures; any gas alarm or suspected release requires the emergency plan first.
Identify which device reports the loss
Begin with the exact wording on the reporting device and the associated point label. Record whether the message appears on the gas controller, a supervisory display or another system. Ask for the applicable manual definition rather than assuming that every product uses 'offline' identically.
A useful report separates 'no local display', 'local display available but controller reports offline' and 'controller appears normal but supervisory display is stale'. These are descriptions for support, not diagnoses. Do not travel into a suspect area to check the local display; provide observations only when site arrangements allow them.
Describe the pattern across points and time
State whether one point, a group or the entire displayed network is affected. Include the first known occurrence and whether the condition is continuous or intermittent. Attach the approved point list or a simplified layout if it helps identify the affected group without exposing sensitive site information.
Record recent authorized changes, such as replacement equipment or a planned power event. A timing association is a lead for investigation, not proof of causation. Avoid calling a cable or detector defective solely because the symptom appeared after work nearby.
Separate interface evidence from protocol evidence
The Modbus Organization's introduction distinguishes message interpretation from the underlying connection and explains device addressing and manufacturer data mapping. An RS485 label alone cannot establish that a controller and detector exchange compatible messages.
Ask the supplier to confirm the installed detector-controller combination, applicable protocol documents and approved configuration. Include any gateway in that request. Keep these as document-review questions, not instructions to try addresses, change communication settings or write registers on an operating safety system.
Give the technician a bounded evidence package
The following checklist organizes a support request. Electrical inspection and measurements belong to qualified personnel under the approved site work arrangements; this article does not specify terminal connections or live tests.
| Review area | Information to provide |
|---|---|
| Power observations | Existing power-event record and safely available status indications |
| Communication route | Approved drawing, affected point identifiers and known gateway model |
| Configuration | Authorized configuration record, not guessed replacement values |
| Version identity | Detector/controller model and available software or document revision |
| History | Last confirmed operation, changes and previous investigation reference |
Restored communication needs an appropriate close-out
Ask the responsible reviewer to document the cause as confirmed, suspected or unresolved and to specify the required verification. A message disappearing establishes less than a documented demonstration that the intended point and state are correctly represented. Do not equate reconnection with a completed gas-response test.
The UTAI controller planning guide provides the wider system-selection context. This troubleshooting page adds symptom organization only. It gives no instructions to swap wires, alter termination, bypass monitoring, power-cycle equipment or assume cross-version compatibility.