Issue Clarification is needed on which batteries and PSU cards are compatible with x96 controllers in the BAS & Sigma systems. Product Line Satchwell BAS & Sigma Environment S-x96-STD S-x96-BAT Satchwell Sigma Satchwell BAS Cause Due to changes in battery legislation and evolving hardware requirements, selecting the correct battery and PSU card for BAS & Sigma controllers can be confusing. Additionally, spare parts are no longer available for sale. Resolution Battery Options for Sigma Controllers: Part Number Description Battery Type Voltage Capacity Runtime S-ARM7-BAT ARM7 CPU Board Battery Ni-MH 2-Button Cell 2.4V 80mAh — S-V53-BAT V53/V25 CPU Board Battery Ni-MH 3-Button Cell 3.6V 150mAh — S-X96-BAT Hi-Capacity Battery for x96 Ni-MH D-Cell Pack 10.8V 5Ah ~12 hours S-X96-STD Standard Capacity Battery for x96 Ni-MH AA-Cell Pack 10.8V 1500mAh ~1.2 hours ⚠️ Note: Due to UK legislation (2006), NiCad batteries are no longer permitted. NiMH batteries are now standard. Availability Notice 🚫 No spare parts are available for sale. Customers should consider alternative solutions such as system upgrades or contacting Schneider Electric support for guidance. PSU Card Compatibility Guidelines Timeframe PSU Card Notes 11/2008 – Present PSU cards support both NiMH and NiCad batteries. No replacement needed. 04/2004 – 10/2008 PSU card must be replaced to fully charge NiMH batteries. 1999 – 03/2004 PSU card must be replaced to fully charge NiMH batteries. Pre-1999 Requires 2 resistors (included with NiMH battery). See TPA for details.

Issue Customers may experience difficulty locating data sheets for Satchwell IAC controllers and touchscreens. Product Line Satchwell MicroNet Environment  IAC 400 IAC 420 IAC 600 IAC Touchscreen MIU Interface Cause Restricted access to internal or partner-only storage areas can prevent users from retrieving necessary documentation for legacy Satchwell MicroNet devices. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) To assist with this, the following data sheets are available for direct download: IAC 400 Controller Data Sheet IAC 420 Controller Data Sheet IAC 600 Controller & Touchscreen Data Sheet MIU Interface Data Sheet Download All Data Sheets (ZIP, 6.9 MB)

Issue This article provides a comprehensive cabling guide for Sigma and BAS, including best practices and requirements for optimal system performance. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Proper cabling is critical for the reliable operation of Sigma and BAS systems. Incorrect cabling can lead to communication failures, data loss, or degraded system performance. Resolution Refer to the attached Cabling Guide (PDF) for detailed specifications and diagrams. The guide includes: Cable Types and Specifications Recommended cable types for different BAS components (e.g., twisted pair, shielded cables). Maximum cable lengths and signal integrity considerations. Network Topologies Supported topologies for Sigma and BAS (e.g., star, daisy-chain, ring). Guidelines for segmenting networks to reduce interference and improve reliability. Termination and Shielding Proper termination techniques to prevent signal reflection. Shielding methods to minimize electromagnetic interference (EMI). Installation Best Practices Routing recommendations to avoid electrical noise. Grounding and bonding procedures. Labeling and documentation tips for easier maintenance. Troubleshooting Tips Common cabling issues and how to identify them. Tools and techniques for testing and verifying cable integrity. Additional Resources Download the Cabling Guide PDF

Issue On an NCP (Network Control Protocol) network with two or more MicroNet Touchscreens, certain values within MicroNet controllers located on the Sub-LAN of a Touchscreen may change unexpectedly and without user intervention. Product Line Satchwell Micronet Environment Micronet NCP Touchscreens Cause This issue typically arises due to high communication traffic through the MicroNet Touchscreens. When multiple Touchscreens are present on the same NCP network, the increased data exchange can lead to unintended value changes in connected controllers. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF)   Firmware version, MNTS0H, addresses this issue. This firmware has been validated with: VisiSat 2.1 Build 148 Service Pack 1 MN50 Series Controllers Xenta 555 and Xenta 731 hardware For detailed firmware information and installation guidance, refer to: TPA-LOND-09-0029.00 – Touchscreen TS0H Firmware (PDF)  

Issue How can wet bulb temperature be calculated using only a temperature sensor and a humidity sensor? Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Wet bulb temperature is a key parameter in HVAC and psychrometric calculations. While the most accurate method requires dew point and barometric pressure, a reasonably accurate estimate can be derived using just temperature and relative humidity. Resolution Method 1: Simplified Formula Using Assumed Pressure This method assumes a constant barometric pressure (typically 1006 mBar). Formula: tw = t * (0.45 + 0.006 * Rh * √(p / 1060)) Where: tw = Wet bulb temperature (°C) t = Dry bulb temperature (°C) Rh = Relative humidity (%) p = Pressure (mBar), typically set to 1006 Sigma/BAS Object Code: 10 XFlo = 0.000000 20 YFlo = 0.000000 30 XFlo = XFlo + ( SQRT ( 1006.00 / 1060.00 ) ) 40 YFlo = YFlo + ( 0.00600000 * POINT 0|50 * XFlo ) 50 YFlo = 0.450000 + YFlo 60 YFlo = POINT 0|49 * YFlo P0|49 = Temperature sensor (°C) P0|50 = Humidity sensor (%) Method 2: Polynomial Approximation This method provides a more accurate estimate within the range: Dry bulb temperature: 15–40°C Relative humidity: 10–90% Pressure: 1006 mBar Max relative error: ~6% Formula: Tw = (A * T) + (B * Rh) + (C * T²) + (D * Rh²) + (E * T * Rh) + F Constants: A = 0.539126 B = 0.104784 C = -0.000749356 D = -0.00107743 E = 0.00641463 F = -5.15153 Sigma/BAS Object Code: 10 XFlo = 0.000000 20 XFlo = XFlo + ( 0.539126 * POINT 0|49 ) 30 XFlo = XFlo + ( 0.104784 * POINT 0|50 ) 40 XFlo = XFlo + ( -0.000749356 * POINT 0|49 * POINT 0|49 ) 50 XFlo = XFlo + ( -0.00107743 * POINT 0|50 * POINT 0|50 ) 60 XFlo = XFlo + ( 0.00641463 * POINT 0|49 * POINT 0|50 ) 70 XFlo = XFlo + -5.15153 80 RETURN VIA TEXT 101 VALUE XFlo P0|49 = Temperature sensor (°C) P0|50 = Humidity sensor (%) Notes For higher accuracy, consider using actual barometric pressure and dew point if available. These formulas are suitable for most building automation applications where approximate values are acceptable.

Issue Are usernames and passwords encrypted during transmission from the Remote Client or Web Client to the Sigma Server? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause There is a need to understand the security measures in place for credential transmission between clients (Remote and Web) and the Sigma server, particularly regarding encryption. Resolution   Usernames are not encrypted during HTTP transmission from either the Remote Client or the Web Client to the Sigma server. Passwords are encrypted during HTTP transmission from both the Remote Client and the Web Client to the Sigma server.  

Issue This article provides guidance on connecting MN Touchscreens to various MicroNet controllers, including both older and newer series. It covers remote and direct mounting scenarios, wiring configurations, and important considerations for maintaining system integrity. Product Line Satchwell MicroNet Environment Satchwell MicroNet Touchscreen Cause Improper wiring of MN Touchscreens can lead to: Communication failures between controllers and the touchscreen. Incorrect LAN addressing, causing sub LAN conflicts or inaccessible devices. Power supply interference, especially when isolation is not maintained. Hardware damage, particularly when mounting newer touchscreens on older controllers without modifying connector pins. System instability, due to missing or incorrectly placed jumpers. These guidelines ensure consistent LAN behavior, prevent electrical faults, and maintain compatibility across controller generations. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) General Wiring Principles Touchscreen Addressing: Start at 1/2; avoid address 1. Sub LAN Numbering: Based on touchscreen address. Jumpers: Must be fitted across the top two auxiliary connector pins unless otherwise specified. Remote Mounted Touchscreen (NCP) Connected to MN550/MN650 LAN A: Front-end or local interrogation. LAN B: Sub LAN controllers. Power: Separate 24V supply recommended for isolation. Connected to MN500/MN620 Same as above. Ensure jumpers are fitted on sub LAN controllers. Direct Mounted Touchscreen (NCP) Mounted on MN550/MN650 LAN A: Front-end/local interrogation. LAN B: Other controllers. Jumpers: Remove from controller. Isolation: Not possible unless remotely mounted. Mounted on MN500/MN620 LAN A/B: Same as above. Jumpers: Remove from controller; touchscreen retains jumpers. Pin Modification: Cut pins 6 and 7 if mounting newer touchscreen on older controller.>p> 🔧 Once this modification has been carried out to the Touchscreen, the unit will no longer be suitable to run ARCnet communications. 🔧 Use MN50-TS-NCP (post-Q2 2007) for direct mounting compatibility. Compatibility Notes 50 series and 100 series controllers can share the same LAN. Follow model-specific LAN connection guidelines.

Issue During a Sigma Transition in Building Operation, Sigma controllers and the Enterprise Server (ES) may reside on different subnets. In such cases, global data is not passed to or from the Sigma system. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma controllers communicate global data using broadcast messages (e.g., 192.168.1.255 ). These broadcasts are typically blocked by network switches and routers, preventing communication across subnets. Sigma uses Link Addressing to overcome this limitation. However, if Link Addressing is not configured for the server subnet, the ES will not receive global broadcasts. Resolution To ensure global data is passed between the Sigma system and StruxureWare Building Operation: Assess the need for global data exchange during the Sigma Transition. If required, add a DNN3 controller to the ES subnet. Configure Link Addressing for the DNN3 to enable global data communication. 📘 For detailed steps, refer to the article: Link Addressing on a Sigma System. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue When performing a Data Import using the Sigma Interface within EcoStruxure Building Operation (EBO), the process fails with the error: "Failed to connect to server." Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Building Operation Workstation Satchwell Sigma Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This issue typically occurs when: The Sigma Transition Tool is installed on the Sigma server machine. The tool masks the actual version of the Sigma server and client. The required Sigma version is not installed prior to using the Transition Tool. Resolution To resolve the issue: Verify the Sigma Version Open Windows Explorer and navigate to: C:\Sigma\Bin Locate SigOp.exe (or similar executable). Right-click → Properties → Details tab. Confirm the version is at least 3.46.57. If Version is Below Required (e.g., 3.45.nnn): Uninstall the Sigma Transition Tool. Upgrade Sigma to version 4.08 (build 3.46.nnn). Reinstall the Sigma Transition Tool. Reattempt Data Import Once the correct version is installed and the Transition Tool is reinstalled, rerun the Sigma Data Import in EBO. Remote Clients Ensure all remote Sigma clients connected to the server are also upgraded to the correct version. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Sigma controllers generate alarms, but these alarms are not received or displayed at the Enterprise Server during normal operation. However, when alarms are manually triggered from the Enterprise Server, they are received correctly. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause This behavior is typically caused by firewall restrictions: When the Enterprise Server initiates communication with Sigma controllers, alarm messages are allowed through the firewall and displayed correctly. When the Sigma controllers initiate communication (i.e., during normal operation), the firewall may block these inbound messages, resulting in delayed or missing alarms. Resolution To resolve this issue, allow inbound communication to the Enterprise Server on UDP port 49152. Firewall Configuration Options: If Windows Firewall is not used: Refer to your firewall vendor’s documentation for instructions. If Windows Firewall is used but managed by IT: Contact your IT department to request the necessary exception. If Windows Firewall is used and you have access: You can manually add the exception or use the unofficial tool SBO Firewall Config. Note: While not officially supported, this tool has been successfully used at various sites. For manual configuration steps, refer to: Using Sigma on Windows 7 with Firewall ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Alarms generated by Sigma controllers are not appearing at the EcoStruxure Building Operation (EBO) Enterprise Server after transitioning from Sigma. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Sigma Transition Alarms Cause When changes are made to the Sigma system using the Sigma Server (e.g., configuration updates, device additions, or modifications), the updated configuration is not automatically reflected in the EBO Enterprise Server. As a result, alarms generated by the Sigma controllers may not be received or displayed in the Enterprise Server. Resolution To ensure that alarms are correctly received at the Enterprise Server after making changes in the Sigma system: Re-import the Sigma Configuration: After any modification in the Sigma Server (e.g., adding or editing devices, alarm configurations), re-import the entire Sigma configuration or the specific modified parts into the EBO Enterprise Server. This ensures that the Enterprise Server has the latest Sigma configuration and can correctly interpret and route alarms. Verify Alarm Routing: Confirm that alarm routing is correctly configured in both the Sigma system and the EBO Enterprise Server. Ensure that the alarm filters and routing rules are correctly set up to forward alarms from Sigma to the Enterprise Server. Check Communication Status: Verify that the communication between the Sigma Server and the Enterprise Server is active and stable. Review logs for any communication errors or dropped connections that may prevent alarm delivery. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue After transitioning Sigma controllers into EcoStruxure Building Operation (EBO), controllers that undergo a cold start do not recover correctly. While they receive the backup server number, they fail to request data from the Sigma Server. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Sigma Server Building Operation Enterprise Server Cause This issue occurs when a Sigma database is imported into the Sigma Interface on the Enterprise Server. Following a cold start, the controller does not initiate a full recovery due to a failure in requesting data from the Sigma Server. Resolution To resolve this issue, follow these steps: Import the Sigma Data Ensure the Sigma database is correctly imported into the Sigma Interface. Restart the Enterprise Server Use the Software Administrator to stop and restart the Enterprise Server. Cold Start the Controller Perform a cold start on the controller to verify full recovery. Note: If additional controllers are added to the Enterprise Server later, another restart of the Enterprise Server will be required. Device-Specific Notes ARM7 Controllers: The above workaround is applicable. V53 Devices: Install the Sigma 4.08 (3.46.79) Hot Fix from the Download Centre on the Sigma Server machine. This hotfix is separate from other Sigma hotfixes. Ensure the correct version of the Sigma Transition Tool is installed. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue After transitioning Sigma graphics into EcoStruxure Building Operation (EBO), certain graphic elements do not display correctly. Specifically, when a bound object commands an element to show or hide, the element fails to respond as expected. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Building Operation Workstation Building Operation Webstation Satchwell Sigma Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This issue typically occurs on machines with a Windows Language Pack installed that uses a comma (",") as the decimal separator—for example, Norwegian Bokmål. During the Sigma Graphics Data Import process, decimal separators used by the Sigma machine (typically a dot ".") are replaced with a comma (","). This affects commands such as condition , Bitmap , Alarm , and others, leading to incorrect graphic behavior in EBO. Resolution To resolve the issue, update the system's decimal separator setting in the Windows Registry: Open Registry Editor Press Windows Key + R, type regedit , and press Enter. Navigate to the following path: Computer\HKEY_USERS\S-1-5-18\Control Panel\International\ Locate the sDecimal entry. This value will likely be set to a comma ( , ). Change the value of sDecimal to a dot ( . ). Re-import the Sigma graphics using the Graphics Data Import feature in EBO. Verify the fix: Open a graphic in the EBO Graphics Editor. Select an element and confirm that the decimal separator in commands (e.g., condition ) is now a dot ( . ). Test the graphic by changing object states and verifying that the corresponding elements respond correctly. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Sigma logging does not function correctly after transitioning to EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause The Sigma logging functionality has been migrated to EcoStruxure Building Operation, but logging fails due to incomplete or incorrect configuration. Resolution To enable and verify Sigma logging within EcoStruxure Building Operation, follow these steps: 1. Import Log Data Sets Navigate to the Sigma Interface in the system tree. Highlight Log Sets. Select Send Log Sets to import them into EcoStruxure Building Operation. 2. Confirm Logging Activity Select the appropriate controller. Go to Diagnostics → Log Set Statistics. Review the statistics to confirm logging has started. This includes log set and object details. 3. Retrieve Logged Values Highlight the required Log Set. Select Retrieve Logged Values to upload the data. 4. Review Uploaded Data Highlight the desired Log Value. View the data as needed to confirm successful upload. 5. Disable Sigma Server Logging Once logging is confirmed to be working correctly in EcoStruxure Building Operation, disable logging from the original Sigma server to avoid duplication or conflicts. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Sigma server fails when a Data Import is initiated during a Sigma transition into EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Satchwell Sigma Building Operation Enterprise Server Cause The failure typically occurs due to data integrity issues within the Sigma database. These issues must be resolved before initiating the transition. Resolution Before transitioning Sigma into EBO, run the SigmaX Doctor utility to validate and clean the database. Address the following common issues: 1. Longtext File Issues Symptoms: Contains 'Mandarin'-type characters, likely from previous BAS/Sigma upgrades. Action: Delete the longtext file located at C:\sigma\data . The file will auto-recreate if needed. 2. Shorttext File Issues Symptoms: Contains incorrectly formatted entries. Action: Use a binary search method to locate the faulty entry: Delete entries 1–250. If the issue persists, check entries 251–500. Continue halving the range until the problematic entry is found and corrected. 3. Index A Errors Types: Looping Segment: Page references itself. Multiple References: Page can be accessed via multiple routes. Action: Use SigmaX Doctor to correct the index structure. 4. Object Corruption Symptoms: Object fails to open in Sigma. Action: Open the object in Sigma and correct it using appropriate methods. If unresolved, the server will fail during Data Import. 5. Log Sets Import Failure Symptoms: Log sets fail to import. Action: Locate logset.rec in C:\sigma\data\server...folder . Make a backup copy. Delete 50% of log sets and retry the import. If it fails, delete another 50%. If it succeeds, the issue lies in the deleted portion. Use the backup to reinstate and isolate the problematic log sets. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue After transitioning Sigma into EcoStruxure Building Operation (EBO), users may notice that alarms and alarm clears do not require acknowledgment. This occurs because the Type of Acknowledgement on the Sigma Interface object alarm is set to 'No' and cannot be changed directly in EBO. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause The issue arises due to incorrect alarm priority settings in the Sigma Alarm Manager. During the data import process into EBO, the system checks the Sigma Alarm Manager configuration. If no alarm priorities are assigned to acknowledgment groups in Sigma, the imported configuration in EBO will reflect a 'No' acknowledgment type. Resolution To enable acknowledgment of alarms and alarm clears, follow these steps in Sigma: Open Alarm Manager. Navigate to Configure > Acknowledgement Groups. Redistribute alarm priorities into appropriate acknowledgment groups based on site requirements. Once the priorities are correctly assigned: Redo the Data Import into EBO. The Type of Acknowledgement should now be set to 'Single'. Note: If the acknowledgment type is set to 'Extended' instead, refer to the related KCS article: Type of Acknowledgement Set to 'Extended' on Sigma Interface Object Alarm for further instructions. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Users need to determine the version or build number of the Sigma software installed on their system. Product Line Satchwell Sigma Environment Satchwell Sigma Cause Sigma software installations are identified by build numbers, not just release numbers. This can cause confusion when troubleshooting or verifying compatibility. Resolution To identify the Sigma release and build number: Open the Sigma Client on the Sigma Server. Navigate to Help > About System Manager. A window will display both the release number and build number. Reference Table Use the table below to match build numbers with their corresponding release versions and file dates. Sigma Release No. Build No. Software/Firmware File Date   SigmaX   Release 1 1.52 Software/Firmware 22.06.2001 SigmaX 4.5 Release 2 2.13 Software/Firmware 14.02.2002 SigmaX 5.2 Release 2 3.12 Supplement 14.02.2002 SigmaX 5.2 Release 3 3.12 Software 31.07.2002 SigmaX 5.2 Release 3.1 3.17 Software 17.09.2002 SigmaX 5.2 Release 3.3 3.3 Software 30.07.2003 SigmaX 5.2 Release 3.4 3.31.1 Software 03.10.2003 SigmaX 5.2 Release 3.6 3.32.10 Software 19.11.2003 SigmaX 5.2 Release 3.7 3.33.9 Software 22.12.2003 SigmaX 5.2 Release 3.7 SP2 3.33.11 Software 27.01.2004 SigmaX 5.2 Release 3.7 SP3 3.33.13 Software 19.02.2004 SigmaX 5.2 Release 3.10 3.34.11 Software 21.04.2004 SigmaX 5.2 Release 3.11 3.34.11 Supplement 31.08.2004 SigmaX 5.2 Release 4.00 3.36.11 Software 16.12.2005 SigmaX 6.0.1 Release 4.00 SP2 3.36.16 Software 02 03 2006 SigmaX 6.0.1 Release 4.00 SP4 3.36.20 Software 23.05.2006 SigmaX 6.0.1 Release 4.01 3.37.08 Software 07.09.2006 SigmaX 6.0.1 Release 4.01 SP1 3.37.09 Software 26 09 2006 SigmaX 6.0.1 Release 4.01 SP3 3.37.12 Software 20 10 2006 SigmaX 6.0.1 Release 4.01 SP4 3.37.13 Software 13 08 2006 SigmaX 6.0.1 Release 4.01 SP4a 3.37.16 Software 17 11 2006 SigmaX 6.0.1 Release 4.01 SP5 3.37.18 Software 05 01 2007 SigmaX 6.0.1 Release 4.02 3.39.09 Software 26 01 2007 SigmaX 6.0.1 Release 4.03 3.40.06 Software 06 06 2007 SigmaX 6.0.1 Release 4.03 Sp1 3.40.09 Software 09 08 2007 SigmaX 6.0.1 Release 4.04 3.41.14 Software 27.02.2008 SigmaX 6.0.1 Release 4.04 SP1 3.41.15 Software 09.05.2008 SigmaX 6.0.1 Release 4.04 SP2 3.41.16 Software 15 09 2008 SigmaX 6.0.1 Release 4.04 SP3 3.41.18 Software 08 01 2009 SigmaX 6.0.1 Release 4.04 SP4 3.41.19 Software 08 01 2009 SigmaX 6.0.1 Release 4.05 3.42.34 Software 06 11 2009 SigmaX 6.0.1 Release 4.05 SP1 3.42.43 Software 22 03 2010 SigmaX 6.0.2 Release 4.05 SP2 3.42.48 Software 26.08.2010 SigmaX 6.0.2 Release 4.05 SEB 3.43.18 Software 08 12 2010 SigmaX 6.0.2 Release 4.06 3.44.14 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.16 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.18 Hotfix 01 02 2012 SigmaX 6.0.2 Release 4.07 3 45 48 Software 20 08 2012 SigmaX 7.0.6 Release 4.07 SP1 3 45 51 Service Pack 09 12 2012 SigmaX 7.0.6 Release 4.07 SP2 3 45 58 Service Pack 20 12 2013 SigmaX 7.0.6 Release 4.08 3.46.57 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.62 Hotfix 21.05.2014 SigmaX 7.0.7 Release 4.08 3.46.70 Hotfix 23 07 2014 SigmaX 7.0.7 Release 4.08 3.46.72 Hotfix 04 08 2014 SigmaX 7.0.7 Release 4.08 3.46.73 Hotfix 12 08 2014 SigmaX 7.0.7 Release 4.08 3.46.79 Hotfix 08 10 2014 SigmaX 7.0.7 Release 4.08 (**1) 3.46.80 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.81 Hotfix 17 02 2015 SigmaX 7.0.7 Release 4.08 3.46.85 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 3.46.86 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 (**2) 3.46.89 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.98 Hotfix 14 12 2016 SigmaX 7.0.7 Release 4.08 (**3) 3.46.104 Software 28 02 2017 SigmaX 7.0.9 Release 4.08 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**4) 3.46.106 Software 28 03 2017 SigmaX 7.0.9 Release 4.08 3.46.107 Hotfix 08 08 2017 SigmaX 7.0.9 Release 4.08 3.46.108 Hotfix 01 05 2018 SigmaX 7.0.9 Release 4.08 (**5) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**6) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.131 Software 29 01 2020 SigmaX 7.0.9 Notes:   **1 Sigma build 4.46.57 with StruxureWare Building Operation v1.5 or 1.6 transition support program installed. **2 Sigma build 4.46.57 with StruxureWare Building Operation v1.8 transition support program installed. **3 Sigma build 4.46.57 with StruxureWare Building Operation v1.9 transition support program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support program installed.. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 transition support program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.2 or later transition support program installed.   Notes: 1. SigmaX version 7.0.9 is now available and can be used on any Sigma version that supported SigmaX version 7.0.6. 2. This information can be downloaded as a PDF file: Sigma Build Numbers 2023 3. When SigmaX 6.0.2 is installed, the build information provided by Sigma (Help > About) can be wrong (later than the actual version). This arises because SigmaX installs a file with Build 3.42.47 in the c:\sigma\bin folder. This is only a problem prior to Sigma Release 4.05 SEB. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue Ensuring correct alarm routing when operating both Sigma and EcoStruxure Building Operation (EBO) together following a transition Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Building Operation Cause During a transition, alarms must be routed to both the Sigma Client and the SBO Enterprise Server (ES). Misconfiguration can lead to alarms not being received correctly. Resolution To route alarms to both systems: Add the ES Server to the Sigma Network In addition to the main Sigma Server, manually add the Enterprise Server (ES) as a Server (node). Use the actual ES server name for clarity and consistency. Example: Server 101: Sigma Server Server 102: ES Server Create a Dummy Sigma Client for the ES Manually add a dummy Sigma Client representing the ES. Assign the ES server to this client.  Verify Sigma Server Settings Ensure the Sigma Server configuration is correct and supports dual routing. Configure RouteSets Add both the Sigma Client and the dummy ES Client to the RouteSets. This enables alarms to be sent to both servers. Distribute Configuration Files Download and distribute the following files to all outstations: routeset.rec att.set ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue During a Sigma transition into EcoStruxure Building Operation (EBO), a duplicated set of Short Form Edit (SFE) graphics appears in a different language alongside the original graphics. Example: First Data Import: English Second Data Import: Danish This results in two sets of SFE graphics—one in English and one in Danish—linked to the same objects. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Satchwell Sigma Cause The language setting in EBO was different during each Data Import. When the Sigma Interface is imported with a different language setting, EBO creates a new set of SFE graphics in that language. Resolution To prevent duplicated graphics in multiple languages: Before starting the Sigma Data Import: Delete the existing Sigma Interface in EBO. Set the correct language in EBO that matches the desired import language. Restart the Sigma transition process. Important Note: Deleting the Sigma Interface will remove all existing SFE graphic links from the objects. A clean set of SFE graphics will be generated during the new import, ensuring consistency in language and structure. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue The supported operating systems for Sigma 4.08 are not clearly documented in the official product documentation, leading to confusion during installation and deployment. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The official documentation has not been updated to reflect the expanded list of operating systems compatible with Sigma 4.08, particularly in scenarios involving integration with EcoStruxure Building Operation (SBO/EBO). Resolution Sigma 4.08 support varies depending on the build version and its role within the system. Below is a breakdown of supported operating systems based on usage context and build version: 1. Sigma 4.0.8.57 (Front-End User Interface) Supported Operating Systems: Windows XP Professional SP3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 2. Sigma 4.0.8 (Builds 80–89) – Engineering Tool for Sigma Transitioned into SBO/EBO Supported Operating Systems: Windows XP Professional SP3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 3. Sigma 4.0.8 (Build 104 Onwards) – Engineering Tool for Sigma Transitioned into SBO/EBO Supported Operating Systems: Windows XP Professional SP3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Windows 10 (only when part of an SBO/EBO installation) Windows Server 2012 (only when part of an SBO/EBO installation) Note: Support for Windows 10 and Windows Server 2012 is confirmed by R&D and applies only when Sigma is integrated within an SBO/EBO system. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.