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 The Sigma Analogue Output card is expected to produce a voltage range of 0–10 V DC. However, it only outputs a maximum of 9.9 V DC. Product Line Satchwell BAS & Sigma Environment Sigma Analogue Output Card Cause Although the card is specified to produce a 0–10 V DC output, in practice it delivers slightly less than 10 V. This is a known limitation of the hardware design and is within acceptable tolerance levels for most applications. Resolution This behavior is normal and expected. The card is designed to output up to 9.9 V DC, which is considered acceptable for systems requiring a nominal 0–10 V range. If precise 10 V output is critical for your application, consider the following options: Calibration: Check if downstream devices can be calibrated to account for the 0.1 V difference. Alternative Hardware: Evaluate other output modules that guarantee full 0–10 V range. Refer to the product datasheet DS13353_0208 for detailed specifications.

Issue After installing and launching Remote Alarm Manager 2.0 (RAM 2.0) for the first time, the application starts in Demo mode, providing only a 2-hour trial period. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause This behavior is expected. RAM 2.0 enters Demo mode by default upon initial startup because it has not yet detected a valid license. Resolution To exit Demo mode and activate the full version of RAM 2.0: Create the Input Interface (e.g., Sigma R4). Once the interface is created, RAM 2.0 will: Detect the customer’s dongle or Read the engineer’s PC ID code (if applicable). Upon successful detection, the software will exit Demo mode and operate under the licensed configuration.

Issue An interface alarm is generated a few minutes after launching the Remote Alarm Manager (RAM), particularly after upgrading Sigma to release 4.05 or later. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager Satchwell Sigma 4.05 and later Cause In Sigma versions prior to 4.05, the Remote Alarm Manager monitored the Alarmcli.exe process (Sigma Alarm Manager). However, Sigma version 4.05 and later no longer includes this executable. As a result, RAM triggers an interface alarm because it cannot detect the Alarm Client. Resolution To prevent the interface alarm in Sigma version 4.05 or later: Start the Remote Alarm Manager services. Open the RAM Console. Navigate to the Configuration tab. Select Interfaces. Choose Sigma (R4) RAMServer. Go to the Applications section. Deselect the entry for Sigma Alarm Manager (alarmcli.exe). This adjustment ensures RAM does not attempt to monitor a non-existent application, resolving the interface alarm issue. Additional Notes This change is specific to Sigma release 4.05 and later. Ensure all other RAM configurations are reviewed after upgrading Sigma to maintain compatibility.

Issue When using Remote Alarm Manager (RAM) with Sigma 4.05, Long Text messages cannot be sent as part of the RAM message. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 Remote Alarm Manager Cause In Sigma versions prior to 4.05, Long Text messages were stored individually in the Sigma\Data\LongText folder. Sigma 4.05 introduced a new unified format: File: LongText.rec Location: Sigma\Data The Remote Alarm Manager does not recognize this new format, resulting in failure to send Long Text messages. Resolution Scenario 1: Upgrading an existing Sigma site to 4.05 with RAM installed If RAM needs to use Long Text messages: Upgrade the Sigma system to version 4.05. Retain the original Sigma\Data\LongText folder. Create messages manually using the steps below. Scenario 2: Adding a new Long Text message Use the Sigma 4.05 Long Text editor to create the message. Copy the message. Save it as Ltxt???.txt in Sigma\Data\LongText , where ??? is a unique identifier. Scenario 3: Configuring a new Sigma 4.05 system with RAM Create a folder: Sigma\Data\LongText . Use the Sigma 4.05 Long Text editor to create the message. Save it as Ltxt???.txt in the folder, using a unique number for ??? . Additional Notes Ensure that the Sigma\Data\LongText folder exists and is correctly populated with .txt files for RAM to function properly. This workaround allows RAM to access Long Text messages despite the format change in Sigma 4.05.

Issue Users experience significant delays when editing Sigma objects. After editing, the object file appears as zero bytes, and the system behaves similarly even when skipping upload/download steps. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The issue stems from a misconfiguration of the Sigma server. Specifically, the system was incorrectly set up as a remote Sigma client, even though the client and server were running on the same machine. Resolution To resolve the issue: Verify Sigma Client Configuration Launch SetupSvr.exe located in C:\Sigma\Bin\ . Check Client Type If the machine is running both the Sigma client and server, ensure the "This Computer" checkbox is ticked. If the Sigma client is remote (on a different machine), untick the checkbox and enter the IP address or machine name of the Sigma server. Apply Correct Configuration For local clients, ticking the checkbox ensures proper communication and object file handling. For remote clients, entering the correct server details ensures stable editing and file integrity.

Issue Can the Alarm Manager configuration differ between a local and remote Sigma client? Product Line Satchwell BAS & Sigma Environment Sigma Alarm Manager Cause There is a need to configure alarms differently for remote Sigma clients compared to local ones. Resolution The Alarm Manager is a shared component between both local and remote Sigma clients. This means any configuration changes made to the Alarm Manager will affect both clients simultaneously. To achieve differentiated alarm behavior between clients, use Routesets. Routesets allow you to define specific alarm routing rules for individual object alarms. By assigning different Routesets to alarms, you can control which alarms are sent to the local client and which are sent to the remote client. Best Practice Tips Plan Routesets carefully to avoid unintended alarm routing. Test configurations in a staging environment before applying them to production. Document Routeset assignments for future troubleshooting and audits.

Issue This article provides guidance on integrating the Schneider Electric PM710 Power Meter with the following Xenta controllers using Modbus RTU: Xenta 511, 527, 555, 701, 711, 721 (Firmware version 5.1.5 and above) Xenta 731, 913 (All versions) Product Line TAC Vista Environment XBuilder Schneider Electric PM710 Power Meter Xenta 5xx / 7xx / 9xx series controllers Cause Integration is required when PM710 Power Meters are used in systems managed by Xenta controllers via Modbus RTU. To support this, Product Support has developed a device template to assist with configuration. This template is intended as a starting point and may require customization to meet specific project needs. It is not a comprehensive points list. Note: For assistance with template customization or troubleshooting, contact your local Schneider Electric Support team. Resolution To integrate the PM710 Power Meter with Xenta controllers using XBuilder, follow these steps: Download and Extract the Device Template Download the .zip file containing the .dev file from the link below. Extract the .dev file to a convenient location on your hard drive. Add the Device in XBuilder Open your XBuilder project. Right-click on the Modbus Master device. Select Add Device. Browse to the extracted .dev file and click Open. Configure the Device Rename the newly added device to ensure it has a unique name within the Modbus Master network. Adjust the device template as needed to match your specific integration requirements. Downloads Modbus Device Template – PM710 (.zip) PM710 User Manual (PDF)

Issue Understanding the meaning of various LED indicator lights on the front panel of Xenta Server controllers. Product Line TAC Vista Environment Xenta Server Controllers 511, 527, 555, 701, 711, 721, 731, 911, 913 Cause The LED indicators on Xenta Server controllers provide visual feedback about the device's operational status and communication activity. Interpreting these indicators correctly is essential for troubleshooting and system monitoring. Resolution The Xenta Server controller features multiple LED indicators that display the status of the device and its communication ports. Below is a detailed explanation of each LED and its meaning. LED Indicator Overview Position Indicator Description 1 Neuron Status Indicator - Off: Normal mode - Red, blinking: Unconfigured mode - Red, steady: Hardware fault 2 Serial RS-232 B Port - RX: Data is being received - TX: Data is being transmitted 3 Overall Run Indicator - Green, steady: Normal mode - Green, blinking: Start mode - Red, steady: Fail-safe mode - Red, blinking: Unit fault 4 Serial RS-232 A Port - RX: Data is being received - TX: Data is being transmitted 5 Serial RS-485 C Port - Activity Indicator: Shows communication activity 6 Ethernet 10Base-T Port - Activity Indicator: Shows Ethernet communication activity Note: The LEDs for the RS-232 A interface (Position 4) do not indicate communication when using the RS-485 A interface, even though both share the internal Port A. Diagrams Figure 1: LED Layout on Xenta Server Device Figure 2: Internal Serial Ports and RS-232/485 Interfaces

Issue When upgrading a TAC Vista site to EcoStruxure Building Operation (EBO), LonWorks devices may not be discovered during the device discovery process in the AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P). Cause This issue typically occurs when the original TAC Vista database was configured using a third-party network management tool such as LonMaker or NL220. These tools can assign a custom domain ID to the LonWorks network. Default Domain ID in TAC Vista: 1/11 Default Domain ID in EBO: 1/254 If the domain ID used during the initial setup differs from EBO’s default, the AS-P will not detect devices on that domain. Resolution Identify the Current Domain ID Use the existing TAC Vista database to determine the domain ID configured on the LonWorks devices. Alternatively, use NodeUtil to identify the domain ID. Refer to the article: Finding LON devices under a different domain length with NodeUtil Configure a Spare AS-P Set the domain ID on a spare AS-P to match the existing domain ID used in the site. For guidance, see: How to locate and change the LonWorks domain ID Discover Devices Use the spare AS-P (now configured with the matching domain ID) to perform device discovery. The previously undetected devices should now appear and be accessible. Decommission Devices In the AS-P, navigate to the Actions menu for each discovered device. Select Decommission to revoke the device’s address and stop communication. Reintegrate Devices After decommissioning, re-add the devices to the LonWorks network. They should now be discoverable by an AS-P configured with the standard EBO domain ID (1/254).

Issue Routers or devices with routing capabilities may not support BACnet Protocol 16 Extended Frames (1474 bytes) and only support BACnet MSTP Frame size (480 bytes), so devices that support the larger size need to receive a request with a smaller APDU defined or they will use the largest APDU they support, which will be dropped at the router. Each BACnet device has a Max APDU Length Accepted property and SpaceLogic/Easylogic, which supports Extended Frames, is 1474 bytes. Product Line TAC IA Series Environment MP-X under Tridium offer SE branded Tridium offer I/A Series MNB 1000 Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic MP-C Building Operation EasyLogic RP IO Expansion Module Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause Routers and devices, acting as routers, that support BACnet Protocol Revision lower than 16 will drop the extended frames (aka large packets). BACnet Protocol 16 introduced Extended Frames (1474 bytes) to BACnet MSTP, which increased the frame size from 480 bytes. BACnet devices have Max APDU Length Accepted, which communicates the largest frame size accepted. SpaceLogic/Easylogic have Max APDU Length Accepted = 1474 bytes. Resolution Add bacnetUtil-rt module to the station, which is included in default Niagara installation, using Platform -> Software Manager. Open Palette -> bacnetUtil Select ApduSizeOverride from DeviceOverrides folder Drag-n-drop it on the BACnet controller The default is 480 for BACnet MSTP. To disable for SpaceLogic/EasyLogic controllers communicating via IP or on MSTP supporting Extended Frames, you can change to 1474 to match the CONFIG -> Device Object -> Max APDU Length Accepted. NOTE A: This can be added to any device, so changing to 480 will indicate how much slower communication would be if using an MSTP router that does not support Extended Frames. I tried by viewing Device Report in N4.14 while capturing in Wireshark, so I could see packet timing on the wire, and it was about 3 times slower. ApduSizeOverride # of Request Required Period 480 46 17.13 secs 1474 14 6.76 secs

Issue Is it possible to view license information for all Automation Servers connected to an Enterprise Server (ES), including details such as the Entitlement ID, Product ID, and Fulfillment ID? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium(AS-P) Building Operation Automation Server Bundled(AS-B) Cause In certain scenarios, it may be necessary to verify the licenses activated on all Automation Servers connected to an Enterprise Server. This includes identifying the Entitlement ID, the specific Product ID, and the Fulfillment ID associated with each license. Resolution Yes, it is possible to retrieve license information for all connected Automation Servers via the Enterprise Server. Follow the steps below: Open the Enterprise Server (ES) in WorkStation. Perform a search for "Product 0" : Use the Search function in WorkStation. Ensure that the search is conducted across all folders and that subservers are included in the search scope. Review the search results: Add columns for: EntitlementID ProductID FulfillmentID This method provides a centralized way to audit and verify the licensing status of all connected Automation Servers from the Enterprise Server.

Issue In EcoStruxure Building Operation (EBO) version 6 and later, users may encounter a persistent Modbus Network Offline alarm, even when all Modbus devices under the network are online. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium(AS-P) Building Operation Automation Server Bundled (AS-B) Cause The Modbus communication architecture was restructured between EBO versions 5 and 6. In EBO version 5, the system could generate alarms for the Modbus network itself being offline. In EBO version 6 and later, network-level offline alarms are deprecated. Alarms are now only generated at the device level, not for the network. If a site is upgraded from version 5 to 6, any existing Modbus network offline alarms will persist, but EBO will no longer monitor or clear them, as it no longer tracks network-level status. Resolution To remove the obsolete Modbus network offline alarm in EBO version 6, you have two options: Hide the Alarm Since the alarm is no longer relevant in version 6, you can simply suppress or hide it from the alarm list. Delete and Recreate the Modbus Network This method ensures complete removal of the alarm. Important: Ensure you have a verified backup before performing these steps: Export the Modbus network configuration. Delete the network using the “Keep Bindings” option. Re-import the network configuration.

Issue The "Short Form Edit" command is not available by default in the BAS 2800+ user interface, which may limit user customization and quick access to editing functions. Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause The "Short Form Edit" command is not pre-configured in the default system setup and must be manually added to the user menu. Resolution To add the "Short Form Edit" command to a user menu: Navigate to: System Setup → User Menus Create a New Command: Select "New Command" Fill in the command details as follows: Menu Text: Short Form Edit Executable Path: C:\BAS\BIN\BASPNTSF.EXE Command Line Options: {Osn No} {Pnt No} sf Add the Command to Menus: Once created, assign the new command to the relevant user menus where quick access is needed.

Issue Clarification is needed on the physical location and port assignments of communications modules when upgrading a BAS NIU Type 3 to a Sigma DNN. Product Line Satchwell BAS & Sigma Environment BAS NIU Type 3 Sigma DNN Communications Modules (ARCnet, Ethernet) Cause There are three available module slots in the DNN (formerly NIU). Understanding how these slots correspond to port numbers is essential for proper network configuration. Resolution Each module slot corresponds to a specific port number and network function: Top Slot → Port 1 Typically used for Sub-LAN connections Example: ARCnet module installed here Middle Slot → Port 5 Typically used for Main Network connections Example: Ethernet module installed here Bottom Slot → Port 6 Typically used for Backup Network connections Often left unused unless redundancy is required Visual Reference: In the image below, the DNN is configured with: ARCnet in Port 1 (Top) Ethernet in Port 5 (Middle) Port 6 (Bottom) is vacant

Issue Understanding the impact of Sigma on IT networks and its communication requirements. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause General information regarding Sigma’s behavior and requirements when integrated into an IT network. Resolution Sigma is designed to be IT-friendly and adheres to several IETF standards, ensuring compatibility and minimal impact on network performance. 1. Standards Compliance Sigma complies with the following IETF protocols: RFC 791 – Internet Protocol (IP) RFC 972 – Internet Control Message Protocol (ICMP) RFC 826 – Address Resolution Protocol (ARP) RFC 950 – Subnet Mask RFC 1256 – Router Discovery RFC 768 – User Datagram Protocol (UDP) RFC 1058 – Routing Information Protocol (RIP) 2. Network Utilization Sigma typically uses 1–2% of a 100 Mbps Ethernet connection. 3. Communication Model Utilizes peer-to-peer communication. Device communication occurs only when required by the system or user. 4. Standalone Operation Devices can operate independently for extended periods during network outages. 5. Data Management Controllers can be configured to limit the frequency of global data exchanges. 6. Client Polling Sigma Remote Clients poll the Sigma Server to maintain connection integrity. 7. Protocol Usage Server ↔ Controllers/DNNs/ICs: Use UDP messages (size varies). Client ↔ Server: Use TCP messages (size varies). 8. Port Requirements Sigma uses the following ports: 49152 3614 80 8080 9. Communication Speeds Sigma V53 devices: Communicate at 10 Mbps half duplex. Sigma ARM devices: Negotiate speed starting at 100 Mbps half duplex, then 10 Mbps full duplex, and finally 10 Mbps half duplex. Additional Notes Sigma’s design ensures minimal disruption and efficient operation within modern IT infrastructures. For firewall and network configuration, ensure the above ports are whitelisted.

Issue When running Sigma 4.05 with a backup from a previous Sigma release, the DeviceCnf.rec file is overwritten with a default or blank version. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 and later Cause Sigma 4.05 introduces a new format for the DeviceCnf.rec and GenCnf.rec files. If these files are not in the expected format, Sigma automatically replaces them with default versions during startup or backup restoration. Resolution To prevent data loss and ensure compatibility: Use the Sigma Upgrade Tool: Navigate to: C:\sigma\bin\SigUpgrade.exe This tool upgrades your existing configuration files ( DeviceCnf.rec and GenCnf.rec ) to the correct format for Sigma 4.05. Steps to Upgrade: Close Sigma if it's running. Launch SigUpgrade.exe as Administrator. Select the backup files you wish to upgrade. Follow the on-screen instructions to complete the upgrade. Restart Sigma and verify that the configuration files are intact.

Issue How to correctly node a BAS outstation and what node commands are available. Product Line Satchwell BAS & Sigma Environment Satchwell BAS UNC532 UNC496 UNC596 Cause Users may be unfamiliar with the correct node commands or the process for node configuration using terminal utilities. Resolution To node a BAS outstation, follow these steps: Connect to the Controller: Use either the Pocket Terminal Utility or HyperTerminal. Plug the lead into SK1. The terminal should display "ready". Use the Following Commands: Command Description O Initiates the node command (Note: This is the letter O, not zero). H132 Used for specific controller types (⚠️ Not applicable to x96 controllers). S Displays the current node setup. Note: Always verify controller compatibility before using H132 . 📎 Attachments POCKTERM.ZIP – Pocket Terminal Utility

Issue How to enable or disable Contingency Logging in Sigma. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Users may be unsure when and how Contingency Logging is activated or deactivated for Sigma objects. Resolution Default Behavior When a new Sigma object is created, Contingency Logging is enabled automatically. Disabling Contingency Logging Ensure the controller is online and connected to the Sigma server. Open System Manager. Navigate to the Logging menu and select Contingency Setup . In the dialog box: Uncheck Enable to deselect Contingency Logging. Click OK to confirm. Contingency Logging is now disabled for the selected object. Enabling Contingency Logging Follow the same steps as above to access the Contingency Setup dialog. In the dialog box: Click Enable to activate Contingency Logging. The Entries and Interval fields will become available. Note: The number of entries shown is the maximum allowed for the selected interval. Do not exceed this value. Click OK to complete the process. Contingency Logging is now enabled for the object.

Issue Users may want to configure Sigma clients to communicate with multiple Sigma server sites simultaneously. Product Line Satchwell BAS & Sigma Environment Sigma server and clients. Cause Sigma architecture is designed to support client-server communication with a single active server connection at a time. This limitation is due to routing and session management constraints within the Sigma system. Resolution A Sigma client can only connect to one Sigma server at a time. To switch between servers, use the Start Sigma Client utility. This tool allows users to manually select which Sigma server the client should connect to during startup.

Issue Negative values presented to an IC3-SNP Integration Controller are incorrectly displayed starting at 65535, rather than their true negative representation. Product Line Satchwell BAS & Sigma Environment Sigma IC3-SNP Cause The IC3-SNP Integration Controller miscalculates negative values due to limitations in its internal value handling logic. Resolution To resolve this issue, a custom Lookup Table must be created and assigned to the Analogue Input object within Sigma. Follow these steps: Step-by-Step Instructions Create a Lookup Table Open Sigma System Manager. Navigate to System Setup. Create a new Lookup Table using the configuration below. Assign the Lookup Table Edit the Analogue Input object. Assign the newly created Lookup Table number. Select Download Object. Download the Lookup Table Open Sigma System Diagnostics. Download the Lookup Table to the IC3-SNP controller. Lookup Table Configuration If values are presented in whole numbers: Input Output 0 0 32767 3276.7 32768 -3276.8 65535 -0.1 If values are presented with a ×10 factor, adjust the table accordingly. Additional Notes Ensure the Lookup Table matches the scaling of incoming values. This workaround corrects the display issue but does not change the underlying controller logic.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sigma - The Analogue Output Card Only Produces 9.9 Volts DC

Remote Alarm Manager 2.0 Starts in Demo Mode

Interface Alarm Triggered After Starting Remote Alarm Manager

Remote Alarm Manager Unable to Send Long Text Messages in Sigma 4.05

Sigma - Editing Objects is Very Slow and the Object File Shows Zero Bytes

Sigma – Can the Alarm Manager on a Remote Client Be Configured Differently from the Local Client?

[Dev File] Xenta 5/7/9xx Modbus RTU Integration to Schneider Electric PM710 Power Meter

How to read the LED indicator lights on a Xenta Server controller

LonWorks Device Not Discovered During Discovery Process

Niagara workaround for routers that do NOT support Extended Frames

How to View License Information for Automation Servers Connected to an Enterprise Server

Modbus Network Offline Alarm in EBO Version 6 and Later

BAS 2800+ - Adding a "Short Form Edit" command to a User Menu.

Upgrading a BAS NIU Type 3 to a Sigma DNN – Location of Communications Cards

Sigma - Impact and requirements on an IT network.

Sigma: Preventing DeviceCnf.rec Overwrite During Backup Restoration

How to Node a BAS Outstation – Node Commands Explained

Sigma – Contingency Logging: Enabling & Disabling Guide

Can More Than One Sigma Server Report to Sigma Clients?

Sigma – IC3-SNP Integration Controller Displays Incorrect Negative Values

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!