Issue Guidance required for configuring Sigma UNC controllers when connecting to a subnetted Ethernet network. Product Line Satchwell BAS & Sigma Environment All Sigma controllers connected to a subnetted Ethernet network Cause General configuration advice for network integration. Resolution A subnetted Ethernet network consists of multiple subnets. For example, a network with the address 10.158.1.0 and a subnet mask of 255.255.255.0 includes IP addresses ranging from 10.158.1.1 to 10.158.1.254. An IP address such as 10.158.2.1 belongs to a different subnet within the same broader network. To successfully connect a Sigma controller to a subnetted network, the following parameters must be configured: IP Address Subnet Mask Default Gateway (specific to the subnet) Default Server (controller’s designated server) These settings should be entered using the Sigma Device Configuration Utility (SDCU). 🔧 Note: Ensure that the Default Gateway corresponds to the correct subnet to enable proper routing between subnets. Additional Resources Connecting Sigma Controllers to a Flat Ethernet Network Sigma DNN Configuration for Subnetted Networks

Issue What needs to be changed in the Sigma configuration when the Sigma server is moved or its IP address is changed? Product Line Satchwell BAS & Sigma Environment Sigma Server Cause When relocating the Sigma server or changing its IP address, configuration updates are required to ensure proper communication between the server, clients, and controllers. Resolution To successfully move the Sigma server or change its IP address, follow these steps: Assign a New IP Address Locate the PC in the new area. Assign an appropriate IP address based on the new network. Start Sigma Services Launch the Sigma server and local client. Update System Setup Navigate to System Setup → Networks and Devices. Configure Network Select the zone where the server resides. Under Networks, check if the network exists: If not, create a new network entry. Update Server Settings Under Servers, select the Sigma server. Assign the correct network and updated IP address. Verify Client Connections Under Clients, ensure all clients are correctly attached to the appropriate servers. Confirm Controller Routesets In Controller Items / Routesets, verify that routesets are correctly matched to the clients. Download Configuration Files Download the Node Configuration to all devices. Download the Att.set and Routeset.rec files to all controllers.

Issue Unable to establish communication between a Sigma laptop and a Sigma controller via the RS-232 connection (Diagnostic Port SK1). Product Line Satchwell BAS & Sigma Environment Sigma UNC Controller Cause Incorrect configuration settings. Resolution Use the following checklist to verify and correct the configuration: On the Main Sigma Server ✅ Create a Service Server in the main Sigma server. ✅ Ensure Att.set files are downloaded to the controllers. On the Laptop ✅ Edit the configuration file located at C:\\Sigma\\Data\\Sigma.ini : Set RS232 = 1 Set Commport = 1 , Baudrate = 9600 ⚠️ Note: Ensure the BAS Integrator is disabled, as it defaults to Comm Port 1. ✅ Set the Laptop Server Number to match the Service Server Number configured in the main server. (Navigate to: System Setup → General → Server Details) ✅ Restart the Sigma Server on the laptop. Software Version Considerations If using Sigma 4.05 build 3.42.34, a Hotfix is required to enable serial communications. 👉 Download Hotfix 3.42.46 Later Sigma releases do not require this hotfix. Hardware Check ✅ Confirm that the RS-232 cable wiring is correct and not damaged.

Issue What is required to upgrade a UNC 196 outstation to a Sigma x96 controller? Product Line Satchwell BAS & Sigma Environment UNC 196 UNC 296 Sigma x96 Controller BAS 2000/2800(+) Cause Requirements to modernize BAS infrastructure by replacing legacy UNC 196 hardware with Sigma x96 components. Resolution To successfully upgrade the UNC 196 outstation to a Sigma x96 controller, the following components must be replaced: Comms/CPU Card Power Supply Card These components are available as a bundled upgrade kit: ➡️ S-x96-UPKIT Additional Consideration: If the outstation includes a Maximum Demand Card, it must be replaced with a: ➡️ Digital Input Card (S-UNC-DI)   Notes: Ensure compatibility with existing BAS infrastructure before proceeding. Refer to Sigma documentation for installation and configuration details.

Issue Difficulty in configuring and interpreting 32-bit values when interfacing an IC3-Modbus with a third-party Modbus device. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IC3 Modbus Devices using 32-bit Modbus registers Cause Incorrect configuration of the gateway.txt file and unclear device documentation can read to errors in reading 32-bit values. Resolution The following steps outline the troubleshooting and resolution process: Initial Configuration Attempt The gateway.txt file was configured as per initial guidance. Error encountered: Function code 4 was not allowed. Function Code Correction Modified gateway.txt to use function code 3, resolving the function code error. New issue: Register address still caused an error. Address Correction Attempt Updated string to: 304,3,3,0xC652,1,1,0,0,0 This eliminated address errors but did not return the correct value. Data Format Adjustment (Unswapped) Changed string to: 304,3,3,0xC652,1,0x0202,0,0,0 This represents a 32-bit unsigned value (not swapped). Result: Still incorrect value. Final Configuration (Swapped) Updated string to: 304,3,3,0xC652,1,0x1202,0,0,0 This represents a 32-bit unsigned value (swapped). Result: Correct value returned. Additional Resources Download Gateway.txt file  Related Articles: Sigma - IC3-Modbus Documentation Reading “Long” or 32-bit Data Values Sigma - Release 4.06 - Firmware IC3-Modbus Release Note - Section 11.4.2 - 32bit Data Types

Issue Multiple passive 4-20mA sensors require an external power supply when connecting to a Sigma controller. How can this be done correctly and safely? Product Line Satchwell BAS & Sigma Environment Sigma UNC Controller Passive 4-20mA Sensors External Power Supply (12V DC or 24V DC) Cause Unlike active 4-20mA sensors, which include an internal power source, passive sensors do not. Therefore, an external power supply is necessary to operate them when interfacing with a Sigma controller. Resolution To connect multiple passive 4-20mA sensors to a Sigma controller: Use a dedicated external power supply for each sensor. Voltage: 12V DC or 24V DC, depending on sensor specifications. Wiring Instructions: Connect the positive terminal of the power supply to the positive input of the Sigma controller. Connect the negative terminal of the sensor to the common ground. Configure Sigma Controller: Ensure the Universal Input jumper settings are correctly set to current (mA) mode. Verify input scaling and calibration in the Sigma software to match the sensor's output range. Best Practices: Use shielded cables to minimize electrical noise. Label each sensor connection clearly for maintenance and troubleshooting. Avoid sharing power supplies between sensors unless specifically supported by the sensor manufacturer. Always consult the sensor's datasheet for exact wiring and voltage requirements.

Issue How to use the IR Tool or RS-485 converter to establish communication with a Unifact Pro controller. Product Line Satchwell BAS & Sigma Environment NCP Palm IR Tool RS232 to RS485 Converter Unifact Pro Controller Cause Need for proper configuration and connection method to communicate with the controller using NCP Palm. Resolution Using the IR Tool: Connect the IR Tool to both your laptop and the Unifact Pro controller. Launch the NCP Palm program. In the program: Select the correct serial communication port. Uncheck the CTS / RTS selection boxes. Click OK. From the File menu, select Connect. Enter Subnet Address: 0 Enter Node Address: 0 Click OK ✅ You are now connected to the IR Tool. To connect to the controller: Go to File > Disconnect Then go to File > Connect Enter Subnet Address: 1 Enter Node Address: 1 Click OK ✅ You are now connected to the controller Using the RS-232/485 Converter: The process is similar to the IR Tool method. Instead of using the IR Tool, connect directly to the controller’s communication terminals via the RS-232/485 converter. Additional Resources: 📎 NCP Palm Engineering Guide

Issue Temperature readings from two Unifact Pro controllers—each with its own sensor— are required to be averaged in the Sigma IC-Unifact system. The averaged value should then be transmitted back onto the network for use by both controllers. Product Line Satchwell BAS & Sigma Environment Unifact Pro Master and Slave Controllers Sigma IC-Unifact Networked temperature sensors Cause Each Unifact Pro controller is equipped with a temperature sensor. When "Network Temperature Updates" is enabled: The controller initially uses its local sensor value. Upon receiving a network update, the local value is overwritten. This overwritten value is then sent back to the Sigma IC, creating a feedback loop that excludes the actual sensor readings. Resolution This configuration is not supported due to the feedback loop issue described above. Averaging temperature values across controllers using Sigma IC-Unifact will not work as intended because: Controllers prioritize their own sensor data. Network updates overwrite local values. The overwritten values are re-sent, forming a loop that does not reflect true temperatures. Consider alternative approaches such as: Centralizing temperature averaging in a separate controller. Using one controller as the master source of temperature data. Additional Resources: Sigma IC-Unifact Datasheet

Issue What is the Master to Slave controller ratio of Unifact Pro controllers on a LAN? What is the maximum number of Unifact Pro controllers on a LAN? Product Line Satchwell BAS & Sigma Environment Unifact Pro Cause Clarification on: The ratio of Master to Slave controllers in a Unifact Pro setup. The maximum number of Unifact Pro controllers supported on a single LAN. Resolution   Master-Slave Ratio: ➤ One Master controller can support up to three Slave controllers. LAN Capacity: ➤ A single Unifact Pro LAN can support up to 80 controllers in total. S-Link Sensor Sharing: ➤ An S-Link sensor wired to the Master controller can be shared by up to three Slave controllers. ➤ Important Note: If fan speed control is enabled, S-Link sensors cannot be used on Slave controllers. Additional Resources 📎 Download the Unifact Pro Datasheet  Related documentation: DS_13_303A.pdf  

Issue Users may encounter connectivity issues when attempting to connect to the EcoStruxure Building Advisor Cloud while using a demo license. Product Line EcoStruxure Building Advisor Environment Building Operation Enterprise Central  Building Operation Enterprise Server  Building Operation Automation Server  Building Operation Building Advisor Portal Cause The EBO Demo License does not include the Cloud Connectivity feature, which is required for communication with the Building Advisor Cloud. Resolution Enterprise Server and Enterprise Central A valid production license is required to enable Cloud Connectivity. Demo licenses will not support this functionality. AS-P and AS-B Cloud Connectivity is supported only in versions 3.2.4 or later. When operating in Stand-Alone mode, AS-P and AS-B do not require a separate license for Cloud Connectivity.

Issue A streamlined and automated method is needed to move Enterprise Server (ES) backup files when the program is installed on the D:- drive and program data is stored on the C:- drive. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause   There may be operational or storage-related reasons to move or archive backup files. Installing the program on the D:- drive while retaining data on the C:- drive offers several benefits. Benefits of Separating Installation and Data Drives ✅ Storage Optimization The D:- drive often has more available space, allowing larger installations without impacting system drive capacity. ✅ Performance Improvement Separating installations from data can improve performance, especially if the D:- drive is a faster SSD. ✅ Simplified Backup and Recovery Storing data on the C:- drive simplifies backup and restore processes, avoiding the need to include the entire program installation. ✅ Improved File Organization This separation leads to a more structured file system, making application and data management easier. Resolution It is recommended to initially save backups in the default ProgramData folder on the C: drive and then move them to the D:- drive using a scheduled PowerShell script. PowerShell Script Example # Set variables $Now = Get-Date $Days = 5 $TargetFolder = "C:\\ProgramData\\Schneider Electric EcoStruxure\\Building Operation X.x\\Enterprise Server\\db_backup\\LocalBackup" $Extension = "*.xbk" # Backup file extension $LastWrite = $Now.AddDays(-$Days) $BackupLocation = "D:\\BackupArchive" # Destination folder for old backups # Ensure destination folder exists if (!(Test-Path -Path $BackupLocation)) { New-Item -ItemType Directory -Path $BackupLocation | Out-Null } # Move files older than $Days to the backup location Get-ChildItem -Path $TargetFolder -Filter $Extension -Recurse | Where-Object { $_.LastWriteTime -le $LastWrite } | Move-Item -Destination $BackupLocation -Force 💡 Tip: You can enhance this script with features like file compression, logging, or automatic cleanup of obsolete backups. Automation Recommendation Use Windows Task Scheduler to automate the script execution. 📘 How to schedule PowerShell scripts

Issue Integration between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO) fails due to default security settings that prevent embedding external web content. Product Line EcoStruxure Building Operation Environment Building Operation WebStation PME Web Applications Cause By default: PME restricts other applications from embedding its web content. EBO blocks external web content from being embedded in its UI. To enable integration, both systems must be configured to allow embedded content. Resolution  ✅ Enable External Content in EBO WebStation Log into Building Operation Workstation. Navigate to: Tools > Control Panel > Security and Communication > Security Settings Under WebStation, check the box: ✔ Enable external content to be embedded in WebStation  ✅ Authorize EBO to Embed PME Web Applications Open PME Web Applications. Go to: SETTINGS > Security > Authorized Hosts Add the Building Operation server URL to the Hosts That Can Frame list. Example: https://localhost:446 Click Save. Reset IIS (Internet Information Services) on the PME server to apply changes. Notes Ensure both systems are updated to compatible versions. Use secure URLs (HTTPS) when configuring host permissions. Resetting IIS may cause temporary downtime—schedule accordingly.

Issue Need to verify whether specific network ports are open, as certain ports may be blocked. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspected network port blockage affecting communication between devices or applications. Resolution You can check if a port is open using the Telnet command in Command Prompt. ⚠️ Note: Telnet uses the TCP protocol only. It cannot be used to test UDP connectivity. 📌 Command Syntax: telnet [domainname or IP] [port] [domainname or IP] – The server's domain name or IP address. [port] – The port number the server application is listening on. 🧪 Examples: telnet 192.168.0.20 9001 → Closed port: Displays a "connect failed" message.   telnet 192.168.0.20 9003 → Open port: Displays a blank screen.   🚪 To Exit Telnet Session: Press Ctrl + ] Type quit and press Enter. 📝 Note: Telnet may be disabled by default on some machines. Refer to Microsoft's documentation for instructions on enabling Telnet.

Issue Encounter difficulties configuring EcoStruxure Building Operation (EBO) to connect with the Building Advisor Portal. Product Line EcoStruxure Building Advisor Environment Building Operation Automation Server  Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Building Advisor  Cause Multiple server configuration options exist for connecting to the Building Advisor Portal, each with distinct requirements and roles. Resolution Below are the most common configurations and their requirements: 1. Stand-alone AS-P and AS-B SmartX Servers Requirements: EBO version 3.2.4 or higher Servers connect directly to the EBO cloud No intermediary server required 2. ES/AS Configuration Requirements: EBO version 3.2.4 or higher The Enterprise Server (ES) handles communication and data transfer with the Building Advisor cloud ES acts on behalf of downstream SmartX servers 3. EC/ES/AS Configuration Requirements: All servers must run EBO version 3.2.4 or higher The Enterprise Central (EC) communicates with the Building Advisor cloud only for itself Cloud-connect settings are configured on EC and cloned to each ES Each Enterprise Server (ES) manages communication for itself and its downstream SmartX servers

Issue A malfunction in Power Monitoring Expert (PME) may occur due to the installation of a 32-bit version of SQL Server. Product Line EcoStruxure Building Operation Environment Power Monitoring Expert Cause The issue may stem from using a 32-bit SQL Server, which is incompatible or suboptimal for PME. Resolution You can determine the SQL Server architecture using either of the following methods: Method 1: Using SERVERPROPERTY Open SQL Server Management Studio (SSMS) and connect to the target SQL Server instance. Click New Query. Ensure the master database is selected. Run the following query: SELECT CASE WHEN CHARINDEX('64', CAST(SERVERPROPERTY('Edition') AS VARCHAR(100))) > 0 THEN 64 ELSE 32 END AS [SQL Server Bit Version]; Click Execute. 🔍 Result: The query returns either 32 or 64 , indicating the bit version of the SQL Server instance. Method 2: Using @@VERSION Alternatively, run the following query: SELECT @@VERSION; 🔍 Example Output: Microsoft SQL Server 2008 R2 (SP1) - 10.50.2550.0 (X64) Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) Look for (X64) or (32-bit) in the output to determine the architecture.

Issue Unable to connect Enterprise Server or Enterprise Central to the Building Advisor Cloud Portal  Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment Building Operation Building Advisor EBO Health Module Building Operation Enterprise Server Building Operation Enterprise Central Cause There are specific Operating System (OS) requirements that must be met to ensure successful connectivity to the Azure-based Building Advisor Cloud services. Incompatible OS or software versions may result in missing trust certificates, preventing proper communication. Resolution To ensure reliable cloud connectivity, verify that your system meets the following OS and software compatibility requirements: Enterprise Server Software Compatibility Matrix EBO Version Windows 10 (64-bit) Windows 11 Server 2012 R2 Server 2016 Server 2019 Server 2022 Server 2025 v3.2.4 Yes   Yes Yes Yes     v4.0 Yes v4.0.2 Yes Yes Yes Yes   v5.0 Yes Yes Yes Yes Yes Yes   v6.0 Yes Yes Yes Yes Yes Yes   v7.0 v7.0.2 Yes   Yes Yes Yes Yes Note: Always verify the official Microsoft support status for your OS version to ensure ongoing compatibility and security. Additional Requirements Microsoft .NET Framework: Required: .NET Framework 4.7.2 or later Note: Versions 4.5 or 4.6 are not supported for cloud connectivity. TLS 1.2 Support: SmartX servers require TLS 1.2 to be enabled for secure communication with the Building Advisor Cloud. Automation Servers (AS-P/AS-B) have TLS 1.2 enabled by default. For Enterprise Servers running on Windows OS, ensure TLS 1.2 is enabled. Refer to: How to Check if TLS1.2 is Enabled Summary To maintain a stable and secure connection between EBO and the Building Advisor Cloud Portal: Ensure your EBO version is compatible with your Windows OS. Use .NET Framework 4.7.2 or later. Confirm TLS 1.2 is enabled on your system. Always consult Microsoft's official documentation for the latest OS support updates.

Issue Access to the correct version of Device Administrator or WorkStation is unavailable, and a backup of the Automation Server is required. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause In certain scenarios—such as on-site troubleshooting or version incompatibility—the appropriate tools (Device Administrator or WorkStation) may not be accessible. In such cases, an alternative method is needed to perform a backup.   Note: In EBO 2022 (4.0.3) and later, backups can be performed and downloaded using WebStation Resolution Follow these steps to perform a backup using WinSCP, a secure file transfer tool compatible with all system versions. WinSCP is compatible with all versions of EcoStruxure Building Operation. It requires communication over port 22 (SSH). Download WinSCP Launch WinSCP Open the application after installation. Log In Use the Admin username and password. Select SCP as the protocol.   Navigate to the Backup Folder Browse to the folder containing the server backup files. Refer to the image provided below for the folder location. Download the backup files to your local machine. Additional Notes Ensure SSH access is enabled on the Automation Server. If login fails, verify credentials and network connectivity. This method is suitable for quick, manual backups when standard tools are unavailable.  

Issue How to check installed Power Monitoring Expert (PME) and Cumulative Update (CU ) versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Power Monitoring Expert Cause When troubleshooting integration issues between Power Monitoring Expert (PME) and EcoStruxure Building Operation (EBO), it's important to identify the installed PME version and its corresponding Cumulative Update (CU). Knowing the exact PME and CU versions helps ensure compatibility and can assist in diagnosing integration problems between PME and EBO. Resolution To check the installed PME and CU versions: Open the Windows search bar and type regedit . Press Enter to launch the Registry Editor. Navigate to the following registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Schneider Electric\Power Monitoring Expert\X.X\CumulativeUpdate Review the values listed under this path. These entries will indicate: The installed PME version The Cumulative Update (CU) version, if applicable

Issue The Bluetooth adapter fails to power on when connected to the SmartX Sensor. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause The “Commissioning Tool Enable” property is set to Off, which prevents the Bluetooth adapter from receiving power. Resolution To resolve this issue: Open WorkStation. Navigate to the Sensor Bus Settings. Locate the “Commissioning Tool Enable” property. Set the property to On. Save the changes and verify that the Bluetooth adapter powers on.    

Issue Will client licenses from previous EBO versions activated prior to EBO 7.0 in License Administrator still be applicable after upgrading? Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause With the release of EBO 7.0, Schneider Electric introduced tier-based licensing. This change affects how previously purchased client licenses are recognized. Customers upgrading to EBO 7.0 and selecting the Essential Tier (which includes 3 concurrent client licenses) may be unsure how their existing licenses are counted. Examples of License Questions SXWSWCLIENT0999 in License Administrator, selected Essential Tier → Do they have 3 or unlimited client seats? SXWSWCLIENT0001 in License Administrator, selected Essential Tier → Do they have 3 or 4 client seats? SXWSWWORK00002 in License Administrator, no editor programs running, selected Essential Tier → Do they have 3 or 4 client seats? Resolution When upgrading to EBO 7.0, it's important to understand how client licenses are handled. Unlike previous versions, EBO 7.0 does not recognize client licenses purchased in earlier releases. Instead, license availability is determined by the selected tier during the upgrade. Client licenses from previous EBO versions are not automatically recognized in EBO 7.0. License availability is determined solely by the selected tier during the upgrade. The Essential Tier provides 3 concurrent client licenses. If unlimited concurrent client access is required, customers must upgrade to the Advanced or Advanced Plus Tier. The Workstation Pro license is separate and does not add to the 3 concurrent client licenses included in the Essential Tier.   🔹 Recommendation: Choose a tier that aligns with your concurrent client needs and any additional feature requirements.