Sigma – Previously Configured Object Logging Has Stopped Recording

[Product_Support]

Issue

Sigma data logging has stopped recording unexpectedly.

Product Line

Satchwell BAS & Sigma

Environment

Sigma all versions

Cause

The issue may stem from:

• Changes to the Sigma server PC (e.g., IP address, hostname)
• Network configuration changes
• Controller misconfiguration
• Network communication issues
• Logging configuration missing from the controller

Resolution

• Verify Server Configuration Changes

  • Check if the Sigma server PC has undergone any of the following:
    • IP address change
    • Hostname change
    • Network reconfiguration
  • If changes occurred, update all affected controllers with the correct configuration files.

• Isolate the Scope

  • If multiple controllers are affected, it likely points to a server/network-wide issue.
  • If only one controller is affected, consider:
    • Controller misconfiguration
    • Network issues preventing data transmission
    • Logging configuration missing on the controller

• Controller Diagnostics

  • Use System Diagnostics > Logging Servers from the controller to check:

    • Num Log Buckets – Number of objects being logged
    • Num of Log Records in Use – Tracks in use or full
    • Num of Log Records Free – Available records
    • Num of Log Records Waiting Transmission – Records pending transmission (should be zero if on the same network)
    • Server – Indicates log configuration received

  • Use System Diagnostics > Logging Objects to verify:

    • Object numbers being logged
    • Associated data sets

      

    • If objects are missing from the list:

      • Re-download the log configuration to the controller
      • Note: Objects will only appear after the first log action

---

Additional Tips

• Ensure the controller can communicate with the Sigma logging server.
• Check for alarms or data routing conflicts that may block log transmission.
• Confirm that the logging configuration is present and active on the controller.