Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue After a period of operation, graphics, Dynaview, Actipane, alarm, and logging data may stop updating in Sigma systems. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue is typically caused by the controller communication buffer not clearing. A common scenario is when engineers temporarily use their laptops as Sigma servers and later disconnect them without disabling logging or alarm routing. As a result, data continues to be routed to non-existent servers, causing the buffer to fill up. Resolution Follow these steps to resolve the issue: Check Controller Alarm Buffer Perform a controller stat ( F3 ) to verify if the alarm buffer is retaining data. Attempt to Clear the Buffer Use the ‘Request Deferred Logs and Alarms’ function. If Unsuccessful, Proceed with the Following Checks: Ensure logging and alarm routing information is correct for the active server. Verify the tolerance settings for analogue object values. Confirm that controller backup/default servers are correctly configured. Clear the Controller Archive Use the SDCU utility (Advanced option) to clear the archive. Cold Start the Controller Perform a cold start and allow the server files to download again. Additional Notes Always ensure temporary servers are properly decommissioned by stopping any active logging or alarm routing before disconnecting. Regularly monitor controller buffers to prevent data loss or system lag.

Issue When logging off from Sigma, the graphics window freezes and an error message appears stating: "Sigma must be shutdown by using the Operators Panel Only." Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Sigma 4.06 Cause During the logoff process, a dialog box appears. If the user does not click OK, the dialog box disappears, causing the graphics window to freeze. Subsequent attempts to click OK during login or logoff have no effect. Resolution To resolve the issue: Open Sigma. Navigate to: System Setup > General > Graphics Check the Startup Graphic setting: If it is set to 0 (none), change it to any number other than 0. Preferably, set it to an overview graphic. If no overview graphic exists, create one. This change ensures that Sigma initializes with a valid graphic, preventing the freeze during logoff.

Issue This article addresses common questions regarding the NiMH battery packs used in Sigma X96 controllers, including: What is the average shelf life of these batteries? Can the battery voltage be checked without disconnecting them from the controller? Is there a recommended preventative maintenance interval for checking the batteries? Product Line Satchwell BAS & Sigma Environment Sigma UNC controllers Cause These questions typically arise during routine maintenance or troubleshooting of Sigma controllers, especially when assessing battery health or planning replacements. Resolution Battery Shelf Life NiMH cells degrade over time, especially in long-term storage. Typical shelf life: Up to 2 years. Risk: Prolonged storage can lead to internal short circuits, a known characteristic of NiMH chemistry. Measuring Battery Voltage Direct measurement without disconnection is not recommended. If the battery remains connected, the voltage reading will reflect the charge circuit, not the battery itself. Recommended method: Power down the controller completely (turn off both mains and battery switches). Insert multimeter probes into the back of the battery connector to measure voltage. Note: Voltage alone is not a reliable indicator of battery health. For accurate assessment, measure the run-time on battery power or use a commercial battery analyzer. Preventative Maintenance Interval No fixed interval is officially specified. Why? Battery lifespan is influenced by several factors, especially ambient temperature. Best practice: Monitor battery performance periodically and replace if degradation is observed.

Issue After commissioning a Sigma IC-Lon device, it is necessary to upload the NvConfig.bin file. However, in some cases, this file cannot be backed up using Windows Explorer or third-party backup software. Product Line Satchwell BAS & Sigma Environment Sigma IC-Lon Cause Once the NvConfig.bin file is uploaded, its file properties may restrict access. This can prevent backup tools or Windows Explorer from copying or backing up the file. Resolution To enable backup of the NvConfig.bin file: Modify File Permissions: Right-click the file and select Properties. Go to the Security tab. Click Edit to change permissions. Add the following groups: Authenticated Users Users Assign Full Control to both groups. Apply Changes: Click Apply and then OK to save the changes. Confirm that the file is now accessible via backup software or Windows Explorer.

Issue Can a Windows user be logged off while ModBMS is running? Product Line Satchwell BAS & Sigma Environment Satchwell ModBMS Cause Due to IT security policies, there may be a requirement for Windows user accounts to be logged off when not actively in use. However, ModBMS has specific operational dependencies that affect this. Resolution ModBMS requires an active Windows user session to operate. It is not supported to run as a Windows Service, which means: If the user logs off, ModBMS will terminate. To ensure uninterrupted operation, the Windows user must remain logged in while ModBMS is running. This behavior is by design and cannot be changed.

Issue Need programming assistance to allow HVAC plant override using momentary switches for Plant Start and Plant Stop, bypassing the standard time schedule control. Product Line Satchwell BAS & Sigma Environment Sigma Programming Cause The HVAC plant is typically governed by a time schedule. However, operational flexibility is required to manually override this schedule using physical momentary switches. Resolution The solution involves creating a programmable object that responds to two momentary switch inputs: Point 1: Override ON (Plant Start) Point 2: Override OFF (Plant Stop) Point 33: Time Schedule Status The logic ensures: When the time schedule is ON, the plant can be stopped or returned to schedule control. When the time schedule is OFF, the plant can be started for a fixed duration or returned to schedule control. If overridden OFF, the plant will automatically revert to time schedule control the next day. Sample Code Logic 10 IF POINT 0|1 ON THEN XInt = 1 20 IF POINT 0|2 ON THEN XInt = 2 30 IF POINT 0|33 OFF THEN GOTO 90 40 IF XInt = 2 THEN YInt = 1 50 IF XInt = 1 THEN YInt = 0 60 XInt = 0 70 IF YInt = 0 THEN RETURN TRUE 'Plant On' 80 RETURN FALSE 'Plant Off' 90 YInt = 0 100 IF XInt = 1 THEN SET TIMER 3600 'Start for 1 hour' 110 IF XInt = 2 THEN SET TIMER 0 'Stop immediately' 120 XInt = 0 130 IF TIME LEFT THEN RETURN TRUE 'Plant On' 140 RETURN FALSE 'Plant Off' Notes Point 1: Momentary switch for starting the plant. Point 2: Momentary switch for stopping the plant. Point 33: Indicates whether the time schedule is active.

Issue In Remote Alarm Manager (RAM) 2.0, the “Stop transmission of the Alarm Message” setting within an Action may be unintentionally lost when reviewing or modifying the configuration. This setting is part of the “What should be done when an alarm is acknowledged” menu. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager (RAM) 2.0 Cause The issue arises due to the way the Action configuration is navigated. Depending on the method used to review or edit the Action, the setting may be deselected without user awareness. Resolution There are two methods to modify an Action, each with different implications: Sequential Navigation (Using “Next” Button): Open the Action and proceed through each page using the Next button until reaching Finish. If you repeat this process, the “Stop transmission of the Alarm Message” option may become deselected, even if it was previously enabled. Direct Page Selection (Using Left-Side Navigation): Open the Action and directly select the desired page using the navigation boxes on the left. Important: If this method is used, always verify that the “Stop transmission of the Alarm Message” checkbox is ticked before clicking Finish. Best Practice Tip: When modifying Actions in RAM, always double-check the status of the “Stop transmission of the Alarm Message” setting before finalizing changes. This ensures alarm behavior remains consistent and avoids unintended message transmission.

Issue When attempting to shut down the PC, the Sigma SUM application prompts for a password to close. Product Line Satchwell BAS & Sigma Environment Sigma SUM Cause Sigma SUM is designed to run continuously in the background. When the PC is shut down, the application requests a password to ensure controlled termination. Resolution To close the Sigma SUM application when prompted for a password, enter: Password: SUM Additional Recommendation: To avoid manual startup, add Sigma SUM to the PC’s startup programs so it launches automatically when the system boots.

Issue Editing a Sigma object versions prior to Sigma 4.05 SEB an error message similar to the following is seen: The object has not been read from the terminal database. The controller object file PNTFLE.REC, couldn't be opened. The object cannot be edited Product Line Satchwell BAS & Sigma Environment Sigma 4.05 and earlier Cause The error is triggered by a network connection failure between the local Sigma client and a remote Sigma client. Although the issue originates from the remote client, it can affect the local client once the failure occurs. Resolution To resolve this issue: Restart the Sigma server to temporarily restore functionality. For a permanent fix, upgrade the site to Sigma 4.05 SEB or later. Sigma 4.05 SEB includes improvements that address this network-related issue.

Issue How to connect a Modbus TCP device to the IC3-MODBUS controller. Product Line Satchwell BAS & Sigma Environment Sigma IC3-MODBUS Cause The Modbus device uses a TCP/IP interface instead of traditional RS-232 or RS-485 serial communication. Resolution To establish communication between the IC3-MODBUS controller and a Modbus TCP device: Single IP Connection The IC3-MODBUS controller requires only one IP connection. This connection supports both: The Sigma interface The Modbus TCP interface Network Configuration The Modbus TCP device must also be connected to the same IP network as the IC3-MODBUS controller. IP Address Mapping The IP addresses of both the Modbus controllers and the Modbus TCP devices must be defined. These mappings are configured in the gateway.txt file located in the Sigma system. Firmware Reference For detailed setup instructions and compatibility, refer to: Sigma Release 4.06 - Firmware IC3-Modbus Release Note

Issue When using Sigma 4.00 or later, users may encounter system alarm message No. 19997: "Contact Sigma Support" in the Sigma Alarm Manager. This typically indicates an undefined or unrecognized system message. Product Line Satchwell BAS & Sigma Environment Sigma 4.00 and later IC-Modbus Cause In earlier versions of Sigma, system messages were stored in a master file that could be edited to accommodate new integrations or error messages. However, starting from Sigma 4.00, system messages are hard-coded and cannot be modified. If a system receives an undefined message, it is likely due to: A newer version of controller firmware being used in the field. The Sigma software not yet supporting the newer system message. Resolution Upgrade Sigma Software Ensure the Sigma software is updated to the latest version to include support for newer system messages. Understand IC-Modbus Exception Codes For system messages in the range 19992–20002, the message number is derived from the Modbus exception code using the formula: System Message Number = 19992 + (Modbus Exception Code - 1) Exception Code Meaning Sigma Message No. 1 Illegal function code 19992 2 Illegal data address 19993 3 Illegal data value 19994 4 Slave device failure 19995 5 Acknowledge delayed 19996 6 Slave device busy 19997 7 Undefined error code 19998 8 Memory parity error 19999 9 Undefined error code 20000 10 Gateway path unavailable 20001 11 Gateway target device failed to respond 20002

Issue ModBMS is unable to perform write operations to Sigma version 4.04 (3.41.14), although read operations function correctly. Product Line Satchwell BAS & Sigma Environment Sigma 3.41.14 ModBMS Cause Sigma 4.04 (3.41.14) has a known defect where DDE write commands are not accepted. This affects ModBMS functionality when attempting to write data to Sigma. Resolution To resolve this issue: Install Service Pack 1 for Sigma 4.04 (3.41.14). This service pack corrects the DDE write command issue and restores full read/write functionality. 👉 Download Sigma SP1 for release 4.04

Issue How can a 16-bit signed integer value be correctly interpreted and displayed when read from a Modbus register? Product Line Satchwell BAS & Sigma Environment Sigma IC-Modbus Cause Modbus registers store data in 16-bit format. When dealing with signed integers, the value range is from -32,768 to +32,767. If a value appears as 65xxx, it typically indicates a negative number due to the way signed integers are represented in binary (two's complement format). Resolution To correctly interpret a 16-bit signed integer from a Modbus register, use a lookup table that maps the raw register values to their corresponding signed integer values. Here’s a simplified version of the mapping: Raw Value Signed Integer 0 0 32767 32767 32768 -32768 65535 -0 Explanation: Values from 0 to 32767 represent positive integers. Values from 32768 to 65535 represent negative integers, using two's complement encoding.

Issue Dynaview chart values in Sigma are incorrect when compared to values displayed from an index entry. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause When a Sigma Dynaview chart is first opened, it records an initial value. Subsequent updates occur only on a Change of Value (CoV) condition. If the object tolerance setting is too large, minor changes won't trigger updates, resulting in outdated or misleading chart data. Resolution To ensure accurate and timely updates in Dynaview charts: Close the Dynaview chart. Adjust the object tolerance setting using the Sigma Object Editor: Reduce the tolerance to a suitable level. Download the updated object to the controller. Restart the Dynaview chart. ⚠️ Note: Setting the tolerance too low may cause excessive updates, potentially overloading the controller’s communication resources. Example Tolerance Settings Object Type Suggested Tolerance Notes Temperature Sensor 0.05 Updates every 0.1°C Change of State (Boolean) 0.5 Reflects binary state (True/False) Pressure Sensor (Pascal scale) 10 Suitable for rapidly changing values Tool Available For bulk updates of tolerance settings across Sigma objects, use the Sigma Tolerance Utility. 👉 Download SigmaTolerance.zip

Issue Windows displays an error indicating that Remote Alarm Manager (RAM) services do not start or stop in a timely manner. This may occur during system startup, shutdown, or when manually starting/stopping the service. Product Line Satchwell BAS & Sigma, TAC Vista Environment Remote Alarm Manager (RAM) Cause This issue is typically caused by a corrupted or misconfigured RAM configuration file ( setup.mdb ). Reinstalling RAM alone does not resolve the issue if the configuration file remains unchanged. Resolution To resolve this issue, follow these steps: Backup Configuration (if possible): Launch the RAM Console. Record or export the current RAM setup for reference. Uninstall RAM: Use the standard Windows uninstallation process to remove RAM from the system. Remove or Archive Configuration Files: Navigate to the Remote Alarm Manager installation directory. Locate the setup.mdb file and either: Delete it, or Move it to a backup location for safekeeping. Reinstall RAM: Download and install the latest version of RAM (2.1.025 or newer if available). Reconfigure RAM: Use the previously recorded setup to reconfigure the system. Ensure all settings are correctly applied and saved. Additional Notes This issue may also present as the service being stuck in a “Starting” or “Stopping” state in the Windows Services console. Always ensure you have a backup of your configuration before making changes.

Issue Communication with Sigma controllers fails when using a Sigma laptop or PC running Windows 7. The error message varies depending on the user’s action at the time of the attempt. Product Line Satchwell BAS & Sigma Environment Windows 7 Operating system. Cause The network configuration in Windows 7 is set to “Public” instead of “Work”, which restricts communication between devices on the network. Resolution To resolve the issue, change the network type from Public to Work: Click Start and open the Control Panel. Select Network and Sharing Center. Under View your active networks, click the current network type (e.g., “Public Network”). Choose Work Network. Click Close. Your computer should now be able to communicate with Sigma controllers over the network. Additional Notes This issue is specific to Windows 7 and may not occur on other operating systems. Ensure that firewall settings and antivirus software are not blocking Sigma communication ports.

Issue How to add a new logging database in BAS 2800+ and set it as the current active database. Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause A new logging database is required—either due to data management policies, storage limitations, or the need to archive historical data. Resolution To create and activate a new logging database in BAS 2800+, follow these steps: Open System Manager. Navigate to DataView. Select Data > Logging Databases from the top menu The system will display a list of existing logging databases. Click Add to create a new database. Enter a name for the new database. Select the option to Make Current to set the new database as the active one. The system will now begin storing all new data in the newly created logging database. Additional Information Ensure that the new database name is unique and follows your site’s naming conventions. Making a database “current” means all subsequent data will be logged to this new database. Archived databases can still be accessed for historical data review.

Issue Sigma global points are not functioning correctly when the IP address structure is 192.168.xxx.xxx with a subnet mask of 255.255.0.0 (16-bit mask). Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The issue arises due to a mismatch between the IP address class and the subnet mask used. Specifically: 192.168.xxx.xxx is a Class C IP address. Class C addresses require a minimum subnet mask of 255.255.255.0 (24-bit). Using a Class B subnet mask (255.255.0.0) with a Class C address is invalid and leads to improper network segmentation. This misconfiguration disrupts the broadcast domain, preventing Sigma globals from functioning correctly. Resolution An IP address is divided into two main parts: Network ID Host ID The Subnet Mask determines how many bits are allocated to the Subnet ID and Host ID. Examples: Valid Configuration (Class C): IP Address: 192.168.0.1 Subnet Mask: 255.255.255.0 (24-bit) Subnet ID Bits: 0 Host ID Bits: 8 Broadcast Address: 192.168.0.255 Invalid Configuration (Class C with Class B Mask): IP Address: 192.168.xxx.xxx Subnet Mask: 255.255.0.0 (16-bit) This is invalid because Class C addresses require a minimum of 24-bit subnet masks. Valid Configuration (Class B): IP Address: 190.168.xxx.xxx Subnet Mask: 255.255.0.0 (16-bit) This is valid because 190.x.x.x falls within the Class B range. To ensure Sigma globals function correctly, choose one of the following options: Option 1: Use a subnet mask of 255.255.255.0 (or greater) with the 192.168.xxx.xxx IP address range. Option 2: Change the IP address range to a Class B address (e.g., 190.168.xxx.xxx) to match the 255.255.0.0 subnet mask.

Issue The PCID of a Sigma WinCE device changes from the originally registered code. Product Line Satchwell BAS & Sigma Environment Sigma WinCE PDA devices. Cause This issue typically occurs when the Sigma WinCE device remains connected to a PC or laptop during: Registration of the Sigma WinCE software Startup of the WinCE software Resolution To prevent PCID changes: Disconnect the PDA from the PC or laptop before registering the Sigma WinCE software. Ensure the PDA is not connected to any PC or laptop when starting the WinCE software.

Issue When launching the Sigma Remote Client, a Runtime Error is reported: Program: c:\Sigma\Bin\Sigop.exe Application requested the runtime to terminate in an unusual way. After selecting OK, the following error appears: Software exception 0x40000015 occurred in this application at location 0x7857bb47 Product Line Satchwell BAS & Sigma Environment Sigma Remote Client Cause The error occurs because the incorrect version of Sigma Client software has been installed on the remote client PC. For example: The site is running Sigma 4.05 SEB The remote client was mistakenly installed with Sigma 4.06 Sigma software versions must match across all components (Client/Server and Remote Clients). Mixing versions will result in runtime errors and instability. Resolution To resolve the issue: Verify the site’s Sigma software version: Open Sigma System Manager Navigate to Help > About Sigma Note the build number displayed Ensure the Remote Client matches the site version: Uninstall the incorrect version (e.g., Sigma 4.06) Install the correct version (e.g., Sigma 4.05 SEB) that matches the site ⚠️ Important: Always confirm the site’s Sigma version before installing or updating any Remote Clients.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Graphic, Dynaview, Actipane Alarm and Logging Data Stops Updating

Sigma Graphics Window Freezes – Error Message When Logging Off".

Questions on Sigma backup NiMH batteries.

Sigma IC-Lon file cannot be backed up using windows explorer or a backup program

Can Windows Users be logged off when running ModBMS?

Sigma - Programmable Object: Plant Override Using Momentary Switches

Remote Alarm Manager – “Stop transmission of the Alarm Message” Setting May Be Lost

Sigma SUM Password Required to Close the Application

Sigma - Editing a Sigma object causes an error message

IC3-MODBUS: How is the TCP Version Connected?

Sigma IC-Modbus System Alarm Messages

Sigma - ModBMS Write Commands Do Not Work

Sigma IC-Modbus – Reading a 16-bit Signed Integer Value

Sigma - Values on a Dynaview chart are not correct.

Windows Reports That RAM Services Do Not Start or Stop in a Timely Manner

Sigma Communications Failure on Windows 7

BAS 2800+ – Adding a New Logging Database and Making It Current

Sigma - Globals Do Not Work When Using IP Address Structure 192.168.xxx.xxx with Subnet Mask 255.255.0.0

Sigma WinCE - Device PCID changes.

Sigma - Remote client will not start and generates an error.

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!