Alarms Not Received at the Sigma Server

[Product_Support]

Issue

Alarms generated by Sigma controllers are not being received or displayed at the Sigma server.

Product Line

Satchwell BAS & Sigma

Environment

Sigma software - All versions

Cause

Although the controller successfully generates alarms, they are not transmitted to the Sigma server. This is often due to misconfiguration or network communication issues. Evidence of alarms pending transmission can be seen using the Comms Stats request, which may show a backlog in the Alarm Buffers.

The screen shot below indicates that the "Alarm buffers" have 21 alarms waiting for transmission.

Resolution

To diagnose and resolve the issue, follow these steps:

1. Verify Alarm Generation

   • Use the Comms Stats request from the Sigma server to confirm that alarms are present in the controller’s buffer.

2. Check Client Configuration

   • Ensure the Sigma client (local or remote) is correctly configured. Refer to the article:
     “Alarms are not displayed in the Sigma local or remote client Alarm Manager window”.

3. Validate Server Configuration

   • In System Setup > Networks and Devices, confirm that the Sigma server is properly defined.

4. Confirm IP Address Settings

   • Ensure the Sigma server’s IP address matches the configuration in Network Connections.

5. Inspect Alarm Routing

   • Upload an object with an alarm from the controller and check the Routing Page.
     • Ensure there are no references to “T”, which was used in BAS2800+ but is not valid in Sigma.

6. Check Network Health

   • Collaborate with your IT department to confirm there are no network issues (e.g., firewall blocks, routing problems, or IP conflicts).