Issue
After upgrading from BAS 2800+ to Sigma, the Sigma server receives recurring node reset messages.
Product Line
Satchwell BAS & Sigma
Environment
- Sigma software - all releases.
- Sigma firmware - all versions.
Cause
In the legacy BAS 2800+ system, Controllers and Terminals could share the same device numbers.
Sigma, however, requires unique device numbers for all nodes.
If a controller configuration inadvertently retains a reference to a terminal (with a reused device number), the controller may attempt to send messages to that device. If the referenced device is actually another controller, it will reset upon receiving unexpected messages.
Resolution
To identify the source of the reset messages, use one of the following methods:
Method 1: Using SigView
- Open SigView and display all object data for the controller experiencing resets.
- Search for entries referencing the resetting node number, such as:
T(<resetting node number>) - Investigate any such references and correct the configuration.
Method 2: Using Wireshark
- Disconnect the affected controller from the network.
- Connect a laptop configured with the same IP address as the controller.
- Run Wireshark to capture network traffic for a duration longer than the reset interval.
- Filter the capture to show only messages sent to the IP address of the resetting node.
- Identify the source IP address of these messages.
- Use SigView to inspect the configuration of the source controller.
Example:
A Wireshark trace filtered by Source IP Address can help pinpoint the origin of the problematic messages.
