Issue Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of Struxure EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch Building Operation Software Administrator Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric EcoStruxure\Building Operation X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing EBO, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db).     Launch Building Operation Software Administrator, click Start Service, and then OK.   Launch EcoStruxure WorkStation and log into the enterprise server Select the enterprise server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red, it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed-up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;   Select the automation server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue Steps to backup within EcoStruxure Building Operation (EBO) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a EBO server backup set. Resolution No need to stop AS or ES: EBO freezes the database during backup. Configuration changes are queued until backup completes; historical data is buffered. Do not use raw folder copy: Always use the built-in backup function. Three rules to remember: Restores must use the same software revision. Do not rename the backup set. If renaming is needed, zip the backup and rename the zip file. Default backup schedule: Every Sunday at 1:00 AM. When creating a backup, give the appropriate prefix to the standard name format. See screenshot below. The backup file will be shown as the screenshot below. Should the backup name need to be changed, then either create a new backup, or zip up the backup using the new name. Backup Procedure Enterprise Server (ES) Automation Server (AS) In Workstation, select the Server in the System Tree. Go to Actions → Backup. In Backup Options: Include column: Select servers to include. Backup content: All Data: Historical + configuration databases. Configuration only: Configuration database only. Add a Backup set description (up to 255 characters). Click Backup. Verify that each backup succeeded and click Close. Backup file location: C:\ProgramData\Schneider Electric\StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or C:\ProgramData\Schneider Electric\EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Log in to AS from Workstation. Navigate to System → Backup and Restore → Backup sets → Local. Right-click the backup file → Save To... (choose folder on HDD).

Issue When planning an upgrade to EcoStruxure Building Operation (EBO) 7.x or the latest version for existing sites, users often want to complete engineering work before applying commercial licenses through Software Companion. Product Line EcoStruxture Building Operation Environment EcoStruxture Building Operation Project Configuration Tool 2.0 Cause Software Companion only provides Engineering licenses for new sites, but not existing sites. This limitation means that existing sites cannot be engineered without applying the commercial license first. Resolution To engineer or upgrade existing sites before applying commercial licenses, use Project Configuration Tool (PCT) v2: PCT is a standalone engineering platform, independent of the live system. It allows flexible design and upgrade workflows without impacting production. After engineering or upgrading: Deploy the EcoStruxure BMS server to the live site directly from PCT, or Use an XBK backup and import for deployment. Recommended Steps Download and Install PCT v2.x Windows Installer – v2.2.1.12 Ubuntu Installer – v2.2.1.12 Release Notes v2.2.1 Create or Import Existing Site in PCT Use the Import XBK backup feature for existing sites. Perform Engineering and Upgrade Tasks Configure controllers, graphics, and logic as needed. Validate compatibility with the target EBO version. Deploy to Live Site Either direct deployment from PCT or export XBK and restore on the live server. Additional Resources Project Configuration Tool – Support Tools Specification Sheet

Issue After installing and configuring the LP4502 (online) and downstream devices per the Installation instructions, KGC devices remain offline. (See highlighted snapshot below) Link to Kone Integration Instructions: Access Expert Kone Elevator Integration  Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Kone Elevator Integration LP4502 Comm2 with Micro-B USB adapter (Pluggable USB2-OTGE100) Cause Using the LP4502 comm2 port with a Micro-B USB adapter for elevator communication on a separate subnet is NOT supported. Note: Other Elevator integrations (Thyssen Krupp, Otis) support this setup, which can cause confusion. Resolution 1. Use Comm1 for LP4502 to connect to the internet and site instance. 2. Ensure LP4502 and Kone elevator equipment are on the same subnet. 3. Configure site IT switch: Block internet-to-Kone communication. Allow local traffic on port 2005. KGC downstream IPs must communicate with the LP4502 primary NIC IP. Once completed, the LP4502 and the KGC downstreams will come online and will communicate with the Kone Elevator equipment. Summary KGC downstream devices fail to come online when LP4502 is configured using Comm2 with a Micro-B USB adapter. This setup is not supported for Kone Elevator integration.  

Issue What is the maximum number of site codes that can be loaded into a Continuum system? Product Line Andover Continuum Environment AC-1 and AC-1 Plus modules Cause Network design limitations Resolution There is no limit to the number of site codes that can be loaded in a Continuum system.  However, each door can contain a maximum of four (4) site codes.  In the case of an AC-1 module, if it loses communication with its associated Netcontroller, it will only allow access from the first two fields.

Issue When opening (pulling up) the sunblind, it stops at the end of runtime and then rolls back down. Similarly, when closing (pulling down), it stops at the end of runtime and then rolls back up. Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Lonworks devices including REG-N MSE4 (SVEA 32237-346) Sunblind actuators Cause The actuator is preconfigured for venetian blinds, which include lamella angle adjustments. For simple sunblinds, these parameters cause unintended motor actions after reaching the end position. Resolution For non-venetian blinds: Set the following parameters to zero: UCPTdownPanelAngle UCPTupPanelAngle UCPTpanelTurnTime UCPTpanelTurnTimeBottom Ensure SNVTsetting commands have zero in the rotation part. This disables unnecessary panel angle adjustments and prevents rollback after full movement.

Issue A single folder on a jobsite computer contains multiple DMS backups performed over several years. Each backup consists of multiple files, but they are not grouped by name or date, making it difficult to identify and retrieve complete backups. Product Line TAC IA Series Environment DMS35, DMS350A, and DMS3500 (revisions 9, 10, and 11) Cause Multiple backups were saved in the same directory without a naming convention or date-based grouping, resulting in a disorganized collection of files. Resolution A complete DMS database backup consists of the following files: For DMS35 and DMS3500: filename.IOC – Stores DMS point IDs, records, and alarm parameters. filename.UC – Stores DMS point configuration elements. filename.PG – Stores DMS tables and schedules. filename.UDP – Stores UDPs in the DMS panel. For DMS350A: Includes the four files above plus: filename.Dxx – Stores DCM tables, schedules, and other elements (where xx = DCM address 01–32). filename.Uxx – Stores DCM UDPs (where xx = DCM address 01–32). Recommendation: To simplify future retrieval, create a folder for each backup and name it using a clear convention (e.g., Backup_YYYYMMDD_SiteName ). Move all related files into that folder immediately after performing the backup.

Issue Information is needed about the Access Expert Kone Elevator Integration Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Kona Elevator integration information  Resolution Overview: Destination Dispatch is a licensed feature for Access Expert and used when customers are modernizing their elevator systems or deploying newer ones which do not utilize the relay-based approach for floor control and selection. Within Access Expert, 3 different elevator platforms are supported which include Otis, Kone and ThyssenKrupp. For this document, we will focus on a KONE deployment. It is important to note that a single Access Expert can support multiple integrations at the same time. The KONE integration supports up to 128 total floors of control. When using front and rear entry points within the elevator cabs), each entry point is considered a separate destination. This means a 32- story building using front and rear entry points will result in 64 individual destinations.   A KONE protocol was created so that the LP controllers can manage access for the KONE Elevator Group Controller. Mercury will support configuration for Destination Operation Panels (DOPs), Car Operation Panels (COPs), and turnstiles. This feature is supported on the LP4502, and EP4502. The support for KONE Elevators was added in firmware 1.25.5.   Prerequisites: 1. Access Expert System 2. KONE Destination Dispatch License - FN-DEST-KONERS 3. Appropriate Reader Licenses 4. AX-LP4502 5. Coordination with the Elevator Contractor A KONE Elevator Destination Dispatching System mode was created within Access Expert so that the LP4502 intelligent controller can inform a KONE DEC (Destination Entry Computer, E.g. touch screen or keypad) allowed and authorized floors for a cardholder. This feature is only supported on the LP4502. Note: Other Elevator Destination Dispatch integrations i.e. Thyssen Krupp and Otis use the 2 nd port on the LP4502 controller to communicate with the elevator equipment on a separate subnet. ** The Kone Destination Dispatch integration does NOT support using the 2 nd comm port on the LP4502 to communicate with the Kone elevator equipment. If you attempt to do this, you will be unable to connect to the KGCs, and they will not come online. If you use the Kone elevator simulator for testing, there will not be any response from the KGCs even though you can ping the IP addresses.   Controller Page 1. On the LP4502 controller page, navigate to the "Destination Dispatch" Tab. 2. Select Kone. 3. Enable "Has front and rear floors" if your Kone setup has front and rear floors. Make sure to take into consideration this flag when assigning elevator floors access. It is also recommended to consider the door when creating names. Examples like 2F or 2R are beneficial to system operators. 4. Set the Maximum Cabin Configurations. This is the number of Kone Cabin Access configurations that can be stored on the controller. 5. Press Save. 6. From the "Add Downstream" dropdown, select Kone KGC under the network port. 7. Enter the Display Name to be applied to be used.  8. Enter the KONE primary KGC IP address and Port. 9. Leave 2005 as the default port number. Press Save 10. Repeat steps 6 to 8 for the Backup KGC. 11. Issue a "Push Controller Database" command.   Reader Page Once the Interface Controller has been saved, add/Navigate to a reader attached to the Controller, and move to the elevator tab. The Reader does not reside on the KONE KGC downstream. The KGC downstream is only used to configure the controller with the Primary/Backup KGCs. The readers must be on the regular Mercury downstream modules or attached to the LP4502. Because of this, the actual reader setup is similar to a regular door/elevator deployment with the addition of new settings on the Elevator Tab. Once the Elevator Type is set to Destination Dispatch, a series of settings will be enabled and displayed. You will be presented with a WARNING Message when the Elevator Type is selected. This message is normal and you should select YES. 1. On the reader page, navigate to the "Elevator" tab. 2. Select "Kone Destination Dispatching" as the Elevator Type. 3. Select the Kone Operation Type. Please note that Kone does not support mixing Remote Call Giving Interface (RCGIF or turnstiles) with Destination Operation Panel (DOP) and/or Car Operation Panel (COP). Only one is supported at a time. 4. Depending on the Operation Type, specify the fields. 5. If desired, select an Override Elevator Access Level. This will allow a set of floors to be public during defined schedules. 6. Press Save. Kone Cabin Access Page 1. Navigate to "Access Configuration" on the Main Ribbon bar. 2. Go to "Kone Cabin Access". 3. Click on "Add Kone Cabin Access". 4. Enter a Display Name. 5. Enter the allowed cabins (up to 255). You can use the following formats to enter values: 1-10,15,16. 6. Press Save. Person Page Once the reader has been saved navigate to the person(s) who you want to grant access to the destination dispatch and select the new destination dispatch tab at the bottom of the page this will take you to a new Destination dispatch tab. To add an Elevator user setting, simply select the elevator type you wish to grant access to and click the add button. You will be prompted to select a controller. If there are no active LP4502 elevator controllers, then the dropdown will be empty meaning the user needs to add a valid controller. 1. On the person page, navigate to the "Destination Dispatch Settings" tab. 2. On the "Kone Settings" tab, click on "Add Kone Setting". 3. Select the Kone controller and press OK. 4. Enter the Default Floor. 5. Enter the Default Floor Side. 6. Select a Cabin Access 7. Select the Kone Elevator flags to be applied to the person. 8. Press Save.  *Users must configure the Instance Settings to reflect the correct number of floors. The Cab used will be sent by the Kone system to Keep on an 'Access Granted' and displayed in event data. Masks Kone has Global and Specific Masks that are used when setting schedules. These can be set and cleared by right-clicking on the controller and selecting the appropriate option. Setting the Global Mask opens the Global Mask Configuration window. To add a floor configuration, click the "Add Floor Configuration" button, then select the desired floors. From there the options for each floor can be selected by setting the appropriate flags for the floor. Click "OK" to save the changes. Other Information: Each Elevator Manufacturer has specific settings, commands or fields when deploying the Destination Dispatch integration. The following are specific to KONE: Supported Reader Types: 1. Destination Operation Panel (DOP) – Destination operation panels are located outside of the elevator car. Each of these will be configured as a separate reader. 2. Car Operation Panel (COP) – Destination operation panels are located inside the elevator cab. Each of these will be configured as a separate reader. 3. Turnstile (RCGIF) – Turnstiles are half-height sensor barrier solutions designed for public and commercial buildings and airports. Each turnstile will be configured as a reader and must use a Mercury reader port.

Issue Will we be able to use our Schneider Electric Workbench (Tech Laptop) to connect to the Honeywell Supervisor? Product Line TAC IA Series Environment I/A Series AX (all versions) I/A Series N4 (all versions) Cause The NiCS statement within the license controls the sharing of data and usage of Workbench on a G3 (AX) platform. Resolution The answer depends upon the NiCS statement within the Honeywell Supervisor license. If the Honeywell license accept.wb.in statement is open, the SE brand Workbench would be able to connect and engineer. Based on past experience, the accept.wb.in statement is typically set to webs and can only be accessed by a Honeywell licensed Workbench. The NiCS statement for the Jace is setup to prevent connection by a non-SE brand Workbench. The statements that control sharing of data (accept.station.in and accept.station.out) have always been open. Unfortunately prior to AX version 3.6, the Niagara driver point discovery process utilized some Workbench functionality to perform the connection and use basically defeating the main purpose of the NiCS statement. This meant that the points needed to be added manually. The software was corrected in 3.6 to allow discovering of points regardless of the NiCS accept.wb.in statement. The points will be able to be discovered with the Honeywell Supervisor as long as AX version 3.6 or higher is being used.

Issue EBO Automation Servers may fail to synchronize time with configured Network Time Servers. The system log reports: chronyd[1566]: Can't synchronise: no majority This error occurs when multiple configured NTP servers report significantly different times, preventing the NTP service from establishing a consensus. Product Line EcoStruxure Building Operation Environment Building Operation Automation Servers Cause EcoStruxure Building Operation uses chronyd as the time synchronization daemon on Automation Servers. chronyd is part of the Chrony suite, designed for fast and accurate time sync, especially on embedded systems or devices with intermittent connectivity. Why the Error Occurs: Equal Weighting of Servers: chronyd treats all configured NTP servers equally. There is no concept of “Primary” or “Secondary” in its logic. Quality-Based Evaluation: chronyd continuously assesses each server based on: Round-trip delay Jitter Offset Historical stability Majority Consensus Requirement: chronyd attempts to find a majority agreement among the sources. If the servers report significantly different times, and no consensus can be reached, synchronization fails with the error: Can't synchronise: no majority No Failover Logic: chronyd does not switch between servers. It uses both the Primary Network Time Server and Secondary Network Time Server concurrently to calculate the most accurate time based on latency and jumps.  Example Scenario: If Server A reports UTC+10:00 and Server B reports UTC+10:05, chronyd may reject both if it cannot determine which is correct, resulting in no synchronization. Resolution 1. Use a Single Reliable NTP Server Configure only one NTP server to avoid conflicting time sources. This ensures chronyd has a clear reference and avoids “no majority” errors. 2. Ensure NTP Server Stability To maintain reliable time synchronization, verify the following: Reachability Use ping <ntp_server> from a device on the same subnet as the AS to confirm the server is reachable. Ensure UDP port 123 is open for NTP traffic through any firewalls. Time Accuracy Use tools like ntpq -p <ntp_server> or chronyc sources to check the server’s reported time and offset. Avoid servers with large offsets or jitter values. Latency Prefer servers geographically close to the site or hosted within the same network. High latency can cause chronyd to reject the server as unreliable. Consistency Ensure the NTP server is synchronized with a reliable upstream source. Avoid mixing public and private NTP servers unless they are known to be in sync. Redundancy (if needed) If multiple servers are required, ensure they are synchronized with each other. Use trusted pools like NTP Pool Project for reliable public servers. Monitoring Periodically check synchronization status via WebStation or system logs. Look for chronyd messages indicating sync success or failure.

Issue Customer is unable to install the Security Expert Mobile app on newer Android devices. The app does not appear in the Google Play Store. Reported devices and OS versions: Samsung A15/A16 running Android 16, OneUI 7 Samsung S22 Ultra running Android 15, OneUI 7 Product Line EcoStruxure Security Expert Environment  Application: Security Expert Mobile App Platform: Android devices Store: Google Play Store Affected OS: Android 15 and Android 16 UI Version: OneUI 7 Cause The updated version of the Security Expert Mobile app has not yet been released on the Android Play Store. It is undergoing Cyber Security penetration testing and review, which is expected to complete by end of Q1 2026. Resolution Currently, the Security Expert Mobile app is not available for download on Android. Follow these steps for a workaround: Use the Protege Mobile app as an alternative: Go to the Google Play Store link. Download and install Protege Mobile. Log in using existing Security Expert credentials: Open the Protege Mobile app. Enter your Security Expert username and password. Confirm connectivity to your Security Expert system. Plan for future availability: The official Security Expert Mobile app for Android will be released after the Cyber Security review process (ETA: end of Q1 2026).

Issue A Sigma Programmable Object must detect changes in the state of multiple Digital Inputs (DIs), trigger an external alarm via a Digital Output (DO), and then reset itself to detect subsequent changes—even if the triggering DI remains active. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The programmable object is configured to monitor several digital input points. When any of these points change state (e.g., from OFF to ON), the object must activate an external alarm via a digital output. However, to ensure it can detect future state changes on the same input, the object must reset its internal state after a defined period—even if the input remains ON. Resolution Use a programmable object with logic that: Monitors multiple digital input points (e.g., points 33, 35, 36, 37). Increments a counter ( XINT ) for each input that is ON. Compares the current count ( XINT ) with the previous count ( YINT ). If a new change is detected ( XINT > YINT ), it: Updates YINT Starts a 60-second timer Triggers an alarm (priority can be adjusted) If no new changes are detected and the timer expires, it resets YINT to 0, allowing the object to detect future changes. Sample Code: 10 XINT = 0 20 IF POINT 0|33 ON THEN XINT = XINT + 1 30 IF POINT 0|35 ON THEN XINT = XINT + 1 40 IF POINT 0|36 ON THEN XINT = XINT + 1 50 IF POINT 0|37 ON THEN XINT = XINT + 1 60 IF XINT > YINT THEN GOTO 100 70 IF TIME LEFT THEN GOTO 120 80 IF XINT = 0 THEN YINT = 0 90 RETURN FALSE "reset" 100 YINT = XINT 110 SET TIMER 60 120 ALARM 1 130 RETURN TRUE "Alarm" Notes: Timer duration (Line 110) and alarm priority (Line 120) can be customized. Additional DI points can be added by replicating the logic in lines 20–50.

Issue Recipients receive a message from the Remote Alarm Manager (RAM) indicating that an alarm has been inactivated, even though no manual action was taken to clear the alarm. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause The Remote Alarm Manager is designed to automatically send an inactivation message after a fixed period if an alarm remains active but is not retransmitted. By default, this period is three days, and the message is sent at midnight to the on-call recipient. This behavior is part of the system’s design to prevent stale alarms from remaining indefinitely without notification. Resolution This is expected behavior and not a fault. To manage or modify this behavior: Understand the default configuration: RAM sends inactivation messages after 3 days of no retransmission. This helps ensure recipients are aware that the alarm is no longer considered active. Adjust the inactivation timer if needed: The default 3-day period can be changed in the RAM configuration settings. Consult the Remote Alarm Manager documentation or configuration interface to modify this value. Review alarm retransmission settings: Ensure alarms are configured to retransmit if they remain active and require ongoing attention.

Issue After upgrading from Sigma Version 4.07 to Version 4.08, only the default SIGMA USER is available when logging into the system. All previously configured users and groups are missing. Product Line Satchwell BAS & Sigma Environment Sigma Server Cause During the installation of Sigma 4.08, there is an option to start the Sigma server immediately after installation. If this option is selected during an upgrade, the system creates a new GenCnfEx.rec file containing only the default user. This overwrites the existing user configuration and results in the loss of all previous user and group data. Resolution To preserve existing user and group configurations during the upgrade: Do not start SigmaSvr immediately after installation. Ensure the checkbox to start the server post-install is unticked. Run the upgrade program manually after installation completes. Start SigmaSvr only after the upgrade program has successfully run. If the GenCnfEx.rec file has already been created in error: Stop SigmaSvr. Delete the newly created GenCnfEx.rec file. Ensure the GenCnf.rec file from Version 4.07 is present in the data folder. Re-run the upgrade program to correctly generate the new GenCnfEx.rec file with all server details and user information.

Issue How to configure a single RAM engine to monitor and manage alarms from multiple building automation systems across a site. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager Cause Some sites operate multiple BMS platforms concurrently. Rather than deploying separate RAM engines for each system, a centralized approach using one RAM engine can streamline alarm management and reduce system complexity. Resolution To configure RAM to monitor multiple systems from a single engine: Install RAM on the Master System Choose a primary system (e.g., Sigma) to host the RAM engine. Follow the installation and configuration steps outlined in the RAM Engineering Guide. Configure Alarm Actions Set up alarm actions on the master system (e.g., Sigma) to handle events from remote systems. Integrate Remote Systems Connect additional systems (e.g., BAS2800+, Micronet, Vista) to the master RAM engine. Ensure communication paths and alarm routing are correctly configured. Test and Validate Confirm that alarms from all connected systems are received and processed by the master RAM engine. Monitor for any communication or processing issues.

Issue MicroNet controller objects have a maximum allowable value of 10,000, which is insufficient for some energy meter readings that exceed this limit. Product Line Satchwell MicroNet Environment Satchwell MicroNet Cause MicroNet controller objects are limited to a maximum value of 10,000. When meter readings exceed this threshold, the controller cannot represent the full value using a single object. Resolution To represent meter readings above 10,000, implement a rollover counting mechanism using two counter objects and Menta logic: Create Two Counter Objects in VisiSat Counter 1: Handles the 0–999 part of the meter count. Counter 2: Increments by 1 every time Counter 1 rolls over (i.e., reaches 1000). Link the Rollover Pulse Output of Counter 1 to the Count Input of Counter 2. Diagram: Configure Menta Logic in Xenta 731 Use a Menta block to calculate the total meter reading: This allows representation of values up to 9,999,999. Display the Result The calculated total can be displayed on value pages, graphics, or used in further logic. Downloadable Examples VisiSat Project Xbuilder Project Vista Database All Files Bundle

Issue When importing IAC400 or IAC600 controllers into Building Operation via the Micronet Interface, digital outputs cannot be overridden or forced to a different value. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment IAC400 IAC600 Building OperationServer Cause During the import process, the Digital Output Override State is incorrectly configured in the XML export file. Specifically, the <P1="IsNonVolatile"...> line contains a value that prevents the output from being overridden. Resolution ⚠️ Important Notice Satchwell MicroNet is not supported in EBO 2022 and later. To continue supporting MicroNet devices, you can implement a multi-version system: Keep Servers with MicroNet devices on Building Operation 3.2. 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. To enable digital output override functionality: Create the SBO Export File in Visisat Use Visisat to generate the XML configuration file for the controller. Edit the XML File Before Importing into SBO Open the XML file using a text editor such as Notepad++. Locate the line containing: <P1="IsNonVolatile" Value="1" ...>​   Change the value from "1" to "0" : <P1="IsNonVolatile" Value="0" ...> Import the Modified XML File into SBO/EBO Use the Data Import function in the MicroNet Interface to bring the corrected configuration into Building Operation. Note This issue does not affect IAC420 controllers.

Issue Users need to transfer VisiSat licenses from one PC to another, typically due to hardware replacement or system upgrades. Product Line Satchwell MicroNet Environment Satchwell VisiSat 2.x Cause Licenses are tied to the original PC and must be exported and re-imported to function on a new machine. This process is necessary when: Replacing or upgrading a PC Consolidating engineering tools Migrating from VisiSat v2.0 to v2.1 Resolution Follow these steps to transfer VisiSat licenses: Export License from Original PC Use the VisiSat license management tool to export each license file. Save the exported files to a secure location (e.g., USB drive or network share). Transfer License Files to New PC Copy the exported license files to the target PC. Import License on New PC Use the license management tool on the new PC to import the license files. Ensure VisiSat v2.1 is installed before importing v2.0 licenses. Reference Documentation For detailed steps, refer to the Moving VisiSat Licenses PDF extracted from the VisiSat Engineering Guide. Also see: Transferring VisiSat version 2.0 license to Computer running VisiSat 2.1

Issue Clarification is needed on how data is transferred between Sigma Clients (Remote and Web) and the Sigma Server, including ports used and encryption methods. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma uses proprietary communication methods between clients and the server. Understanding the ports and encryption mechanisms is essential for secure deployment, firewall configuration, and troubleshooting. Resolution   Data transfer between Sigma Clients and the Sigma Server involves the following: Communication Ports TCP Port 3614: Used for general data transfer (e.g., index files, point files, logs, alarms). HTTP Port 8080: Used for web-based communication. Also handles keep-alive messages from clients. This port is configurable via SetupSvr located in C:\Sigma\Bin . Encryption Details Passwords: Encrypted during transmission. Transferred via TCP using ports 8080 and 3614. Usernames: Not encrypted during transmission. Data Security While data is not encrypted end-to-end, Sigma uses a proprietary method for data handling. For enhanced security, consider network-level protections (e.g., VPN, firewall rules). Additional Reference See related article: Sigma Username and Password Encryption for deeper insight into credential handling.

Issue A user needs to transfer a VisiSat version 2.0 license to a new computer that will run VisiSat version 2.1, but the license transfer process is unclear. Product Line Satchwell MicroNet Environment VisiSat 2.1 Cause VisiSat licenses are version-specific and stored in the Windows registry. To transfer a license from v2.0 to v2.1, the license must first be installed and registered using the older version before upgrading. Resolution Follow these steps to successfully transfer the license: Install VisiSat v2.0 on the target machine. This step is necessary to register the license correctly. Transfer the license from the original machine to the target machine. Use the standard license transfer method (e.g., USB drive or license file, depending on your setup). Once the license is successfully registered on the target machine, uninstall VisiSat v2.0. Install VisiSat v2.1 on the same machine. The license will remain valid because it is stored in the system registry.