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 IC or Gateway is returning default values instead of expected data. Product Line Satchwell BAS & Sigma Environment Sigma ICs and IC3s Building Automation System (BAS) PIUs Communication protocols: Modbus, SNP, Unifact Cause In Sigma, default values may appear due to misconfiguration or communication issues. These values reflect the defaults set within the object itself. Resolution Check for Extra Spaces Open gateway.txt and select all content to reveal any hidden spaces. Extra spaces can disrupt parsing and cause default values to be returned. Verify Field Separators Ensure input and output fields are separated by commas ( , ) Commenting Format User comments (e.g., "Temperature Sensor" , "Setpoint" ) must be commented out using a semicolon ( ; ) at the end of the line. Communication Settings In some gateway.txt files, IC/PIU communication protocols (e.g., Modbus) must be explicitly defined. Confirm these settings match the third-party network configuration. Modbus IC Configuration Ensure gateway.txt is set to modbus or crompton as required by the applicati Troubleshooting Tips To simplify problem-solving: Start with one gateway.txt entry and one connected controller on the third-party network. Disconnect all other controllers temporarily. Choose a mapped point with a known value in the third-party controller. Once confirmed working, reconnect additional controllers and map remaining points.

Issue How to configure a Digital Input (DI) object using an Analogue Input (AI) hardware location on an S-UNC-AI Card. Product Line Satchwell BAS & Sigma Environment Satchwell S-UNC-AI Card Satchwell Sigma Cause The S-UNC-AI Card allows for flexible configuration where a DI object can be programmed at an AI hardware location. This is useful when digital input functionality is needed but only analogue input terminals are available. Resolution For Latest AI Cards (Production Code: 200705 and newer): No additional hardware is required. Ensure the board is configured for “Resistive” mode. The software will correctly interpret the input as digital. For Older AI Cards: A Digital Input Module (579-1-359) was previously required. Note: This module is now obsolete and no longer supported.

Issue Can a Sigma 4.05 site be run using a Sigma 4.04 database? Can a Sigma 4.04 site be run using a Sigma 4.05 database? Product Line Satchwell BAS & Sigma Environment Sigma version 4.04 Sigma version 4.05 Cause This issue arises when there is a mismatch between the site version and the engineer’s laptop database version: The site is running Sigma 4.04, but the engineer's laptop has a Sigma 4.05 database. The site is running Sigma 4.05, but the engineer's laptop has a Sigma 4.04 database. Resolution There are two recommended options to address this compatibility issue: Option 1: Use VMware Install the Sigma database version that matches the site requirements within a VMware environment. Advantages: Easier to implement More secure and reliable Avoids manual file manipulation Option 2: Manual File Transfer If VMware is not an option, you can manually transfer specific files between databases: Common Files Between Sigma 4.04 and 4.05: index.rec indexex.rec index.bin pntfle.rec Scenario A: Using a Sigma 4.05 Database in a Sigma 4.04 Site Create pointer.bin files using SigmaX. Manually recreate node files and other necessary configurations. Scenario B: Using a Sigma 4.04 Database in a Sigma 4.05 Site Upgrade the devicecnf.rec file from the site. Ensure only the following files are copied back to the site Sigma database: index.rec indexex.rec index.bin pntfle.rec Additional Notes SigmaX 6.02 is compatible with both Sigma 4.04 and 4.05 databases. Always exercise caution when updating or transferring database files to avoid data corruption or compatibility issues.

Issue Users are unable to change the value of a Sigma object using the standard Trackbar component in a Building Operation (SBO) graphic. Product Line Satchwell BAS & Sigma Environment Ecostruxure Building Operation (EBO) Sigma transitioned graphics Cause Sigma objects are inherently non-writable. Unlike typical objects in EBO, Sigma objects require a manual override (also known as a “force”) to change their values. The default Trackbar component in EBO does not support this behavior, as it attempts to write directly to the object’s value, which is not permitted for Sigma objects. Resolution To enable value changes for Sigma objects via a graphic, the standard Trackbar component Trackbar component must be modified to include a call to the setForce function. This mimics the behavior of legacy Sigma graphics, where moving a slider would automatically override the object. Steps to Modify the Trackbar Component: Open the existing Trackbar component in the graphic editor. Locate the setCurrentValue function. Modify the function to include the setForce call before setting the value: setForce(fullName, true); return setValue(fullName, value); Ensure the modified Trackbar is bound to the “Value” property of the Sigma object, just as it would be in legacy Sigma. Important: Do not bind the Trackbar to configuration values such as “Fixed value” or “Alarm High Limit,” as these cannot be changed via graphics in transitioned Sigma systems. Limitations: Only specific values can be overridden in transitioned Sigma systems. Configuration parameters like “Alarm High Limit” or “Fixed value” cannot be modified through graphics. Additional Resources: Modified Trackbar Component

Issue When opening a Sigma Flexima CSV export text file in Microsoft Excel, the following error message appears: “File not loaded completely” Product Line Satchwell BAS & Sigma Environment Sigma Flexima Microsoft Excel 2003 Cause This issue occurs because the Flexima export file contains more data than the version of Excel being used can handle in a single worksheet. Older versions of Excel (2003 and earlier) are limited to 65,536 rows, which can easily be exceeded by Flexima exports. Newer versions (2007 and later) support over 1 million rows, resolving this limitation. Resolution To resolve this issue, consider the following options: ✅ Option 1: Reduce Export File Size Run more frequent Flexima extractions from the Sigma Scheduler. This will generate smaller CSV files that stay within Excel’s row limits. ✅ Option 2: Upgrade Excel Version Use Excel 2007 or later, which supports up to 1,048,576 rows. This will allow the full file to load without errors. Additional Notes This issue is specific to older versions of Excel. Always verify the row count and file size before opening large CSV exports. Consider using Excel’s Power Query or Text Import Wizard for better handling of large datasets.

Issue How can the Sigma server, which typically run as a service, be configured to run as an application? Product Line Satchwell BAS & Sigma Environment Sigma 4.05 and above Windows 7 Windows 2008 server Windows XP Windows 2003 server Cause Certain operating systems, such as Windows 7 and Windows 2008 Server, do not support running the Sigma server as a service. To enable the ModBMS DDE connection on these platforms, the Sigma server must be run as an application. Resolution To switch between running the Sigma server as a service or as an application, use the following commands via the Windows Start > Run dialog: To run Sigma server as an application (after it has been installed as a service): "C:\Sigma\bin\SigmaSvr.exe" /regserver To revert and run Sigma server as a service (if it was previously set to run as an application): "C:\Sigma\bin\SigmaSvr.exe" /service How to Verify the Current Mode: Open Services on the computer. If SigmaSvr is not listed, the server is running as an application. If SigmaSvr is listed, the server is running as a service.

Issue When using SHD100 or SHD101 humidity sensors with a BAS 2800+ Outstation or Sigma Controller, the sensors may output a DC voltage exceeding the expected 0–10V range. This can cause the controller to display a default or erroneous value. Product Line Satchwell BAS & Sigma Environment BAS 2800+ Outstation Sigma Controller SHD100 / SHD101 Humidity Sensors Cause The sensors are capable of producing a DC voltage signal greater than 10V. When this occurs, the controller may interpret the signal as out-of-range and revert to a default value, potentially triggering alarms or incorrect readings. Resolution To prevent out-of-range errors and ensure accurate readings: Add a Series Resistor Install a 10K ohm, 0.1% tolerance resistor in series with the 0–10V signal line. This helps limit the voltage and protect the input circuitry. Create a Lookup Table In Sigma or BAS 2800+, configure a lookup table with the following values: Input (mV) Output (%) 0 0 83335 100 100000 100 This table allows the system to interpret voltages up to 11.335V without triggering an out-of-range alarm. Apply the Table Assign the lookup table to the analog input object. Then download both the object and the table to the Outstation or Controller. Outcome With this configuration, the system will tolerate sensor outputs up to 11.335V, ensuring stable operation and avoiding false alarms.

Issue Is IPv6 IP Addressing format support by Sigma controllers? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IPv4 and IPv6 network environments Cause The global pool of IPv4 addresses is nearly depleted. To accommodate the growing demand for IP addresses, the industry is transitioning to IPv6. This raises questions about compatibility with legacy systems such as Sigma controllers. Resolution Sigma controllers do not currently support IPv6 addressing. The recommended and supported protocol for IP addressing in Sigma systems remains IPv4. Additional Notes Ensure your network infrastructure continues to support IPv4 for Sigma devices. If planning a migration to IPv6, consider network segmentation or dual-stack configurations to maintain compatibility.

Issue Guidance on configuring a Sigma Distributed Network Node (DNN) when connecting to a subnetted Ethernet network. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Subnetted Ethernet network Cause A subnetted Ethernet network consists of multiple subnets. For example: Network: 10.158.1.0 Subnet Mask: 255.255.255.0 Valid IP range: 10.158.1.1 to 10.158.1.254 Another subnet might be: 10.158.2.0 In such environments, the Sigma DNN must be configured with: A valid IP address A Subnet Mask A Static Route Resolution Assign IP Configuration Set the DNN’s IP address and subnet mask according to the subnet it resides in. Configure Static Route Use the Pocket Terminal 32 program. Syntax: SR+ 0.0.0.0/0 <Default Gateway IP> <Ethernet Port Number> Example: If the default gateway is 10.158.1.254 and the Ethernet port is 5 , enter: SR+ 0.0.0.0/0 10.158.1.254 5 Disable RIP (Routing Information Protocol) RIP is enabled by default and may interfere with static routing. To disable RIP on port 5: Open Pocket Terminal Enter: RIPD 5 Click Send Inform IT Network Administrators Since RIP is disabled, sublan routes are not broadcast. Ensure that manual routing entries are added to network routers. Additional Notes This configuration ensures reliable communication between Sigma controllers and the DNN across subnet boundaries. Always verify routing with IT before deployment.

Issue An end user has requested guidance for their IT department on how to secure a Building Automation System (BAS) effectively. Product Line Andover Continuum, EcoStruxure Building Activate, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Building Automation Systems (BAS) IT/OT Network Infrastructure Cybersecurity Best Practices Cause With the increasing convergence of IT and OT systems, securing Building Automation Systems has become critical. Customers are seeking best practices to ensure their systems are protected from cybersecurity threats and vulnerabilities. Resolution To assist with securing your Building Automation System, Schneider Electric provides a comprehensive white paper authored by the Buildings BU IT Security Group. 📄 Download the white paper here: Best Practices for Securing an IBMS (PDF) This document outlines: Key cybersecurity principles for Building Automation Systems Network segmentation and access control strategies Secure configuration and hardening guidelines Monitoring and incident response recommendations Compliance with industry standards (e.g., IEC 62443, ISO/IEC 27001) 🔍 Additional Resources Schneider Electric Cybersecurity Solutions Scheider Electric Cybersecurity Support Portal IT System Planning Guide - EcoStruxure Building Management EcoStruxure Building Operation Webhelp

Issue Assistance is required to create a Sigma program that controls five chillers in a fixed sequence. The existing attempt does not function as intended. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Control five chillers in a fixed sequence Introduce a configurable delay (default: 20 minutes) between starting each chiller Allow for an adjustable temperature differential to determine when chillers are activated Resolution The following program logic can be used: Program Logic 10 XFlo = POINT 0|144 - POINT 0|140 20 IF XFlo <= 0.000000 THEN XFlo = 0.000000 30 IF XFlo >= POINT 0|141 THEN XFlo = POINT 0|141 40 XFlo = (XFlo / POINT 0|141) * 100.000 50 XInt = 0 60 IF XFlo >= 20.0000 THEN XInt = XInt + 1 70 IF XFlo >= 40.0000 AND YInt >= 1 THEN XInt = XInt + 1 80 IF XFlo >= 60.0000 AND YInt >= 2 THEN XInt = XInt + 1 90 IF XFlo >= 80.0000 AND YInt >= 3 THEN XInt = XInt + 1 100 IF XFlo >= 100.000 AND YInt >= 4 THEN XInt = XInt + 1 110 IF TIME LEFT THEN GOTO 180 120 IF XInt > YInt THEN GOTO 150 130 YInt = XInt 140 GOTO 190 150 ZInt = INT(POINT 0|142) * 60.0000 160 SET TIMER ZInt 170 YInt = YInt + 1 180 IF XInt < YInt THEN SET TIMER 0 190 RETURN VIA TEXT 92 VALUE FLOAT(YInt) Object Descriptions Object Type Description 140 SPA Object Setpoint (reference temperature) 141 SPA Object Differential (range over which chillers activate) 142 SPA Object Delay time (in minutes) 144 AI Object Chiller return temperature Chiller Command Configuration Each chiller command object must use hysteresis control. Configure as follows: Chiller Low Setting High Setting 1 0.1 0.9 2 1.1 1.9 3 2.1 2.9 4 3.1 3.9 5 4.1 4.9 Additional Notes Ensure the programmable object is linked to the chiller command objects. The hysteresis settings prevent rapid cycling and ensure stable operation. For a copy of the above text, click here.

Issue Customer requires a program to calculate sunrise and sunset times for Sheffield using Sigma programmable objects. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause There is no built-in function in Sigma to calculate sunrise/sunset times. A custom program is needed to determine these values based on date and location. Resolution To review sunrise/sunset times for a specific location: Visit the Sunrise/Sunset Almanac Tool. Enter the desired location and click GO. Select Almanac > Sunrise/Sunset. Choose the required month to view the data. Alternatively, use the following Sigma programmable objects to calculate these values directly. Programmable Objects Object 1 – Day of the Year Calculation 10 XInt = DAY 20 IF MONTH >= 2 THEN XInt = XInt + 31 30 XFlo = FLOAT(YEAR) 40 XFlo = XFlo / 4.00000 50 XFlo = FRAC(XFlo) 60 IF XFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 70 IF YInt = 0 AND MONTH >= 3 THEN XInt = XInt + 28 80 IF YInt = 1 AND MONTH >= 3 THEN XInt = XInt + 29 90 IF MONTH >= 4 THEN XInt = XInt + 31 100 IF MONTH >= 5 THEN XInt = XInt + 30 110 IF MONTH >= 6 THEN XInt = XInt + 31 120 IF MONTH >= 7 THEN XInt = XInt + 30 130 IF MONTH >= 8 THEN XInt = XInt + 31 140 IF MONTH >= 9 THEN XInt = XInt + 31 150 IF MONTH >= 10 THEN XInt = XInt + 30 160 IF MONTH >= 11 THEN XInt = XInt + 31 170 IF MONTH >= 12 THEN XInt = XInt + 30 180 RETURN VIA TEXT 200 VALUE XInt Object 2 – Sunrise Time Calculation 10 XFlo = POINT 0|1 20 YFlo = FLOAT(YEAR) 30 YFlo = YFlo / 4.00000 40 YFlo = FRAC(YFlo) 50 IF YFlo = 0.000000 THEN YInt = 1 ELSE YInt = 0 60 IF YInt = 1 AND MONTH >= 3 THEN XFlo = XFlo - 1.00000 70 ZFlo = LOOKUP(1001, XFlo) 80 ZFlo = ZFlo / 60.0000 90 YFlo = FRAC(ZFlo) 100 ZFlo = ZFlo - YFlo 110 YFlo = YFlo * 60.0000 120 YFlo = YFlo / 100.000 130 ZFlo = ZFlo + YFlo 140 RETURN VIA TEXT 203 VALUE ZFlo Object 3 – Sunset Time Calculation (Same logic as Object 2, using different lookup values) Object 4 – Sunrise/Sunset Interlock 10 XFlo = POINT 0|2 20 YFlo = FRAC(XFlo) 30 XFlo = XFlo - YFlo 40 YFlo = YFlo * 100.000 50 IF HOUR >= INT(XFlo + 1.00000) THEN GOTO 90 60 IF HOUR = INT(XFlo) THEN GOTO 100 70 XInt = 0 80 RETURN FALSE "Plant Off" 90 XInt = 1 100 IF MINUTE >= INT(YFlo) THEN XInt = 1 110 XFlo = POINT 0|3 120 YFlo = FRAC(XFlo) 130 XFlo = XFlo - YFlo 140 YFlo = YFlo * 100.000 150 IF HOUR >= INT(XFlo) THEN GOTO 170 160 GOTO 180 170 IF HOUR >= INT(XFlo + 1.00000) OR MINUTE >= INT(YFlo) THEN XInt = 0 180 IF XInt = 1 THEN RETURN TRUE "Plant On" 190 RETURN FALSE "Plant Off" Attachments Sunrise-Sunset Times.zip – Includes lookup table and object files.

Issue Some controllers do not support direct 0–20 mA current input signals. To ensure compatibility, the signal must be converted into a voltage format that the controller can accept—typically 0–10 V DC. Product Line Satchwell BAS & Sigma, Satchwell MicroNet Environment UNCX96 controllers UNCX32 controllers IAC controllers Satchwell Micronet controllers Cause Certain controllers are designed to accept voltage inputs only. Direct connection of a 0–20 mA signal may result in inaccurate readings or failure to register the signal. Resolution To convert a 0–20 mA signal into a 0–10 V DC signal: Install a precision resistor: Use a 500 ohm resistor with 0.1% tolerance. Connect the resistor in series with the 0–20 mA signal. Measure voltage across the resistor: The voltage drop across the resistor will range from 0 V (at 0 mA) to 10 V (at 20 mA). Connect this voltage to the controller’s Universal Input (UI) or Analog Input (AI). Configure the controller input: Set the input type to standard voltage input (0–10 V DC). Additional Notes Ensure the resistor is rated for the expected power dissipation. This method is also applicable for 4–20 mA signals, with appropriate scaling. Always verify controller specifications before applying this conversion.

Issue Configuring a UNC 532 outstation to operate with both a modem and a BAS 2800+ terminal presents challenges due to hardware limitations. Product Line Satchwell BAS & Sigma Environment BAS 2800+ UNC 532 Modem Cause The UNC 532 controller has shared UART communication ports, which restrict simultaneous use of a modem and a BAS 2800+ terminal when the controller is connected via LAN. This is due to the internal architecture where Channel 3 becomes unavailable in networked mode. Resolution LAN-connected configuration: Channel 3 is disabled. Modem and terminal cannot be used together. Refer to the Node Configuration window: PL3 = Port 3 PL4 = Port 2 Standalone configuration: Modem and BAS 2800+ terminal can be configured together. This setup bypasses LAN restrictions and allows full use of UART channels.

Issue The HVAC Optimization module in the Building Advisor (BA) portal is currently displaying data that is two months behind the current date. Snapshot: The image below illustrates the data available within the HVAC Optimization module as of October. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Advisor HVAC Optimization Module Cause This does not represent a defect in data collection or in the functionality of the Building Advisor Portal Resolution The limited data display is intentional and aligns with the system’s design principles. Energy providers often apply retroactive adjustments to consumption records, and interim placeholder values can be unreliable. By excluding these, the system ensures data integrity and accuracy. Additional Notes: This behavior is expected and documented. No action is required unless data is missing beyond the expected two-month delay.

Issue ModBMS does not allow an OPC Client to write OPC DA values to Sigma. However, reading values from ModBMS/Sigma is successful. Product Line Satchwell BAS & Sigma Environment Sigma versions 4.04 and earlier ModBMS OPC Client Cause ModBMS uses DDE (Dynamic Data Exchange) functions to read and write data to the Sigma server. In Sigma versions prior to 4.05, the DDE write function was not supported. This limitation was resolved in Sigma version 4.05 and later. Resolution To enable OPC DA write functionality, upgrade Sigma to version 4.05 or later, where the DDE write capability has been implemented.

Issue The battery supplied with the V53 processor board is dead and requires replacement. Product Line Satchwell BAS & Sigma Environment V53 532 Controller Cause The original battery installed on the V53 processor card and 532 controller has reached the end of its service life. Resolution The original battery is rated at 70mAh. The recommended replacement is the V53-BAT, which provides a 150mAh battery. Both the V53 processor card and the 532 controller are designed to support this higher capacity battery without any issues. 📌 Specifications Original Battery Rating: 70mAh Replacement Battery (V53-BAT): 150mAh Compatibility: Fully supported by V53 and 532 circuitry

Issue Users require access credentials to edit index or binary files within Doctor or SigmaX. Product Line Satchwell BAS & Sigma Environment BAS Doctor Sigma SigmaX Doctor Cause To perform modifications in Doctor or SigmaX, specific passwords are needed to unlock editing capabilities for index and binary files. Resolution To edit files in Doctor or SigmaX, use the following passwords: Index File Edit Password: IE Binary File Edit Password: BE 🔹 These passwords are not case sensitive. You may use either uppercase ( IE , BE ) or lowercase ( ie , be ).

Issue The default Sigma user name TAC USER does not work with Sigma 4.05 SEB. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Cause The default user name was updated starting from Sigma 4.05 SEB. Resolution From Sigma 4.05 SEB onwards, the default user name is: SIGMA USER (Note: The password remains unchanged.) Additional Notes If login fails using TAC USER , ensure the version is 4.05 SEB or later and use SIGMA USER instead. This change applies only from version 4.05 SEB onwards. Earlier versions still use TAC USER .

Issue After upgrading to Sigma 4.05 SEB, graphics now display with objects and text misaligned from their original positions. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Sigma 3 Cause Sigma 4.05 SEB includes fixes for previous graphic rendering bugs. These improvements may cause certain graphic elements to appear offset due to changes in how they are processed and displayed. Resolution A hotfix is available from Product Support. Please follow the appropriate steps based on your upgrade path: If upgrading from Sigma v3: Zip the contents of the following folder: C:\Sigma\data\Sgi Send the zipped file to Product Support. If upgrading from Sigma 4.0 or 4.05: Zip the contents of the following folder: C:\Sigma\data\graphics Send the zipped file to Product Support.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

IC or Gateway Returning Default Values – Modbus, SNP, Unifact

Programme a DI Point into an S-UNC-AI Card

Sigma 4.04 and 4.05 Sites Compatibility

Changing the Value of a Sigma Object from a Building Operation Graphic Using a Trackbar Component

When opening a Sigma Flexima CSV export text file in Microsoft Excel an error message occurs 'File not loaded completely'

Running Sigma Server as an Application

SHD100 / SHD101 - Humidity Sensors can give a DC voltage signal of greater than 10 Volts.

Is IPv6 IP Addressing Format Supported by Sigma Controllers?

Sigma DNN Configuration for Subnetted Ethernet Networks

Where Can I Find Information on Securing a Building Automation System?

Sigma – Site Requirement to Control Five Chillers in Sequence

Sigma - Program to calculate the Sunrise time / Sunset time

Converting 0–20 mA into a 0–10 V DC Signal

Can a BAS2800+ UNC 532 Outstation Be Configured to Use a Modem and BAS 2800+ Terminal?

Data Display Constraint in HVAC Optimization Module – BA Portal

ModBMS Prevents OPC Client from Writing OPC DA Values to Sigma

Battery Replacement for V53 Processor Card and 532 Controller

Password for Editing Index or Binary Files in Doctor or SigmaX

The Sigma default user name TAC USER does not work with Sigma 4.05 SEB

Updated a Sigma System to 4.05 SEB – Graphics Display Issues

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!