Learn about the Community. Join our Core Community to Get Started

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Knowledge Base
Showing results for 
Search instead for 
Did you mean: 
Discover the Exchange Community Top members of July 
Discover the latest features your community has to offer: register to the webinar here

Node reset messages are received at regular time intervals after a BAS 2800+ to Sigma upgrade


Node reset messages are received at the Sigma server on a regular basis.

Product Line

Satchwell Sigma


  • Sigma software - all releases.
  • Sigma firmware - all versions.


Messages designed to be sent to a server are being sent to a device node.


The BAS 2800+ system allows Controllers and Terminals to have the same numbers allocated. In Sigma this is not possible as all device numbers are unique. Should a reference to a terminal accidently be left in a controller configuration, then the controller may send messages to this device number, the receiving controller will then reset.

There are two ways to locate the source of the messages being sent to the resetting controller, they are:

  1. Use SigView to display all of the object data for a controller, and then search the data for the node number of the resetting controller. You will be looking for entries such as T(resetting node number).


  1. Disconnect the controller from the network, and then connect a laptop, configured with the controller IP Address, and running WireShark to record all network messages.
  2. Allow WireShark to run for a period greater than the time between controller node resets.
  3. Filter the WireShark messages to review only messages sent to the IP Address of the resetting node. Check what the source IP address of these messages is, and then use SigView to review this controllers data.

A typical Wireshark display is shown below, in this case the trace is filtered on the "Source" IP Address.

For more information on using WireShark, please review Using WireShark to analyse communications on an Ethernet network.

Tags (2)
Labels (1)
No ratings