Issue Clarification is needed regarding which communication protocols and hardware interfaces are supported when using VisiSat software on Windows 7 operating systems. Product Line Satchwell MicroNet Environment Satchwell VisiSat Windows 7 32/64 bit Cause There is ambiguity around the compatibility of various communication protocols and hardware interfaces with VisiSat when installed on Windows 7 systems. Additionally, some legacy hardware components are no longer supported or available. Resolution The following communication options are supported for VisiSat on Windows 7: SNP Protocol Via computer’s native RS232 port Via USB to RS232 converter Via PCMCIA to RS232 converter Via ExpressCard to RS232 converter IP tunneling through Xenta 555/731 or AS/AS-P LAN network Remote site connection NCP Protocol Via computer’s native RS232 port Via USB to RS232 converter Via PCMCIA to RS232 converter Via ExpressCard to RS232 converter IP tunneling through LAN network Remote site connection ARCnet Protocol Via RS232 port connected through a null modem cable to a MicroNet Interface Unit (MN50-MI-ARC) Via PCI120U-485 PCI card (no longer manufactured) Note: USB22 Series (USB to ARCnet adapters) are not supported with VisiSat IP tunneling through LAN network Remote site connection LON Protocol Not supported on Windows 7 (both 32-bit and 64-bit)

Issue Understand methods for integrating Security Expert with Active Directory for creation and management of Operators and Users. Product Line EcoStruxure Security Expert Environment Security Expert Active Directory SX-AD-OPR SX-AD-USR SX-DB-SYNC PowerShell Cause Security Expert Active Directory Integration provides synchronization and authentication for Active Directory users enabling organizations to leverage on the user management and security policies that Active Directory provides. This article looks at the details between each integration option. Resolution There are four options for Active Directory Integration. 1. Default Windows Authentication option. This allows for logging in to Security Expert with the Windows User account credentials which could include AD users if on a Domain. Operator object must be created in Security Expert and configuration of windows authentication option has some specific steps to be followed for it to work. Unable to login to Security Expert using Windows Authentication Remember to use syntax "<domain>\<username>" for the username when configuring the Operator for a Windows user ON a  Domain. Remember to use syntax "<computername>\<username>" for the username when configuring the Operator for a Windows user that is NOT on a Domain. No extra license is required for this. 2. SX-AD-OPR : License for adding Security Expert Operators from AD. Security Expert Operators will need to be added manually using the following steps: Navigate to Operators and click Add. Check the Windows Authentication box. Click the ellipsis adjacent to the User Name. Use the Active Directory Users window to search for the AD credentials you wish to use. Once the Operator has been added, you may check the Windows Authentication option when logging in. 3. SX-AD-USR : License for adding Security Expert Users from AD. This will allow an active directory domain windows group to be periodically polled for updates that will in turn update the Users in Security Expert. Individual options for importing users, disabling user if AD user is disabled, disabling user if AD user is deleted. Only user names are imported, other than this only action can be disabling of users in Security Expert. No other details can be updated or added. See application note AN-141 Security Expert LDAP User Import Configuration. 4. SX-DB-SYNC : Data Sync Service with Powershell script. Powershell script pulls user details out of AD and writes to a CSV file that the Data Sync Service then imports into Security Expert. Can perform more functions than SX-AD-USR as any attribute from AD users can be mapped to any attribute in Security Expert users. Will require powershell experience as the sample script may need to be modified. See SEC-APP-03-1.0 – SX AD integration using PowerShell for a sample script and in-depth details on how to configure this solution for importing User data. See Security Expert Data Sync Service for details on setting up and using the Data Sync Service.

Issue Clarification is needed on how to correctly wire and connect Micronet LCDs to various Satchwell MicroNet controllers.  Product Line Satchwell MicroNet Environment Micronet LCD / Micronet 50 series LCD Micronet 300 / 350 series controllers Micronet 440 / 450 series controllers Micronet 500 / 550 series controllers Micronet 620 / 650 series controllers Cause Micronet LCDs have multiple wiring and connection options depending on: The specific controller model in use Communication type (e.g., direct, networked) Installation method (e.g., panel mount, wall mount) This variability can lead to confusion or miswiring during installation or maintenance. Resolution Refer to the Micronet LCD Connections document (updated July 2012), which provides a comprehensive summary of connection options for Micronet LCDs across different controller models. 📎 Attachment: MN LCD connections (updated July 2012).pdf This document includes: Wiring diagrams Supported controller models Communication interface details Installation best practices Ensure that: The correct controller model is identified before wiring Communication settings (e.g., bit switch configurations) are verified Power supply requirements (e.g., 24VDC) are met

Issue Attempts to download images or object files to UNC532 controllers only partially complete and then fail. This behavior is often observed in the Sigma debug window. Product Line Satchwell BAS & Sigma Environment Sigma UNC532 Cause The UNC532 controller has limited processing capability. When global data broadcast rates are high (e.g., 600 broadcasts per minute), the controller may experience communication timeouts during file transfers. This results in incomplete downloads. Resolution To diagnose and mitigate the issue: Check Global Broadcast Rates Use Wireshark to trace Ethernet backbone communications. Refer to the article: Using Wireshark to Analyse Communications on an Ethernet Network. Reduce Global Data Load If analysis confirms excessive broadcast traffic, consider: Segmenting the network Reducing unnecessary global points Optimizing controller configurations

Issue Alarms generated by Sigma controllers are not being received or displayed at the Sigma server. Product Line Satchwell BAS & Sigma Environment Sigma software - All versions Cause Although the controller successfully generates alarms, they are not transmitted to the Sigma server. This is often due to misconfiguration or network communication issues. Evidence of alarms pending transmission can be seen using the Comms Stats request, which may show a backlog in the Alarm Buffers. The screen shot below indicates that the "Alarm buffers" have 21 alarms waiting for transmission. Resolution To diagnose and resolve the issue, follow these steps: Verify Alarm Generation Use the Comms Stats request from the Sigma server to confirm that alarms are present in the controller’s buffer. Check Client Configuration Ensure the Sigma client (local or remote) is correctly configured. Refer to the article: “Alarms are not displayed in the Sigma local or remote client Alarm Manager window”. Validate Server Configuration In System Setup > Networks and Devices, confirm that the Sigma server is properly defined. Confirm IP Address Settings Ensure the Sigma server’s IP address matches the configuration in Network Connections. Inspect Alarm Routing Upload an object with an alarm from the controller and check the Routing Page. Ensure there are no references to “T”, which was used in BAS2800+ but is not valid in Sigma. Check Network Health Collaborate with your IT department to confirm there are no network issues (e.g., firewall blocks, routing problems, or IP conflicts).

Issue An Analogue Input (AI) point configured for a 0–10V signal in Sigma or BAS may display a default or erroneous value when the input voltage exceeds 10V DC. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Sigma AI points are designed to operate within a 0–10V DC range. If the connected sensor or device outputs a voltage greater than 10V, the system interprets this as an out-of-range condition, causing the AI point to revert to its default value. This behavior is commonly observed with certain sensors (e.g., SHD100 / SHD101 Humidity Sensors) that can output voltages above 10V, especially under specific environmental conditions. Resolution To prevent out-of-range values and ensure accurate readings, consider the following mitigation strategies: 1. Voltage Clamping Using a Zener Diode Component: Zener Diode (e.g., 9.1V rating) Installation: Can be installed at the sensor end (preferred for ease) or at the controller input. Operation: Limits the input voltage to the Zener’s breakdown voltage (e.g., 9.1V). Any voltage above this threshold is clamped, preventing overvoltage conditions. Note: Typically, a series resistor is used with Zener diodes. However, if the sensor has high impedance, the current is minimal, and a resistor may not be necessary. Diagram: 2. Series Diode Voltage Drop Component: Standard Diode (e.g., 1N4001) Installation: Connect in series with the sensor’s output signal to the controller. Operation: Introduces a voltage drop (~0.6V), effectively reducing the input voltage. Requires a revised lookup table to compensate for the voltage drop. Example: 10V input becomes 9.4V at the controller. 3. Limiting Actuator Feedback Voltage Scenario: When feedback is sourced from an actuator. Solution: Restrict actuator output to a maximum of 9.5V. Ensures feedback signal remains within acceptable range. Caution: May slightly reduce valve/system performance if the actuator controls a mechanical device like a valve. Additional Notes Always verify the sensor’s output characteristics before integration. Consider using lookup tables to calibrate and correct voltage offsets introduced by diodes. For humidity sensors like SHD100/101, refer to their datasheets for voltage output behavior under varying humidity levels.

Issue Fault Finding on an IC-SNP / IC3-SNP and associated IAC controllers. Product Line Satchwell BAS & Sigma Environment IC-SNP IC3-SNP IAC controllers Cause Communication faults on the SubLAN may be caused by: Cause Description Incorrect LAN Termination Missing or improperly placed 120-ohm resistors can cause signal reflections and data corruption. Biasing Misconfiguration Bias jumper not set to “D” (Full Biasing) can result in unstable idle voltage levels. Faulty Controller Driver A single IAC controller with a failed RS-485 driver can hold the RX line low, blocking communication. Corrupted gateway.txt Entries Invalid or misconfigured entries can prevent the IC-SNP from initializing communication properly. Physical Layer Issues Damaged cables, poor connections, or incorrect wiring can interrupt signal transmission. Power Supply Problems Inadequate or unstable power to controllers can cause intermittent or complete communication loss. IC-SNP Hardware Failure Internal faults in the IC-SNP or IC3-SNP can prevent proper LAN operation. Excessive LAN Length or Load Too many devices or long cable runs without repeaters can degrade signal quality. Environmental Interference Electrical noise from nearby equipment can disrupt RS-485 signals. Resolution 1. Use of Alarm Manager Access via Sigma default/backup server. Review system messages (priorities 22–30) for controller-specific errors. Look for messages like “Unable to Communicate with Controller ???”. 2. Troubleshooting gateway.txt File Symptoms: “Unable to open gateway.txt file” error. Steps: Start with a minimal gateway.txt (1–2 entries). Use a known-good version from Exchange-On-Line. If errors persist: Remove all entries except one. Download and warm-start the controller. Gradually reintroduce entries to isolate the faulty line. 3. Controller Not Responding Single Controller: Check local communication using Visisat and LIB-4-485. Verify LAN wiring and power supply. Multiple Controllers: Indicates partial or full SubLAN failure. Begin investigation at the IC-SNP. 4. IC-SNP Hardware Checks Component Expected Behavior Bias Jumper Set to D (Full Biasing) Termination 120-ohm resistors at both ends Channel 2 TX LED Flashes after warm-start (gateway.txt processing) Channel 2 RX LED Flashes if receiving replies RX LED Permanently On: Indicates a faulty IAC controller driver disrupting LAN comms. 5. IC-SNP Retry Mechanism Retries each controller 3 times before marking offline. Sends error to Alarm Manager. Retries offline controllers every 30 minutes (on the hour and half-hour). 6. Binary Chop Method for LAN Isolation Purpose: Efficiently isolate faulty segments or controllers. Steps: Identify LAN midpoint. Disconnect twisted pair at nearest controller. Observe RX LED behavior: LED Off: Fault lies beyond midpoint. LED On: Fault lies before midpoint. Repeat by halving LAN again (25% or 75%) until fault is found. 7. Voltage Testing Guidelines Use a DC voltmeter to measure: Measurement Expected Voltage +ve to 0V ~2.5 V –ve to 0V ~0.15 V +ve to –ve ~2.31 V Note: Negative voltages suggest LAN faults. Compare readings across segments to identify anomalies. 8. RX LED Not Flashing at All Possible Causes: Faulty IC-SNP Faulty SubLAN Faulty Controllers Steps: Disconnect LAN after first controller. Warm-start IC-SNP. Observe RX LED: If flashing resumes, use binary chop to isolate fault. If not, test cable and controller individually. 9. Cable Testing Procedure Disconnect both ends and separate cores. Measure resistance: Between cores: ∞ Each core to earth: ∞ Short cores at one end. Measure resistance at other end: Between cores: ~0 Ω Each core to earth: ∞ 10. Controller Testing Use LIB-4-485 and Visisat Engineering software. Confirm controller responds to direct communication. Final Steps: Once faults are resolved: Download full gateway.txt. Warm-start IC-SNP. Monitor Alarm Manager for new errors.

Issue After upgrading from BAS 2800+ to Sigma, the Sigma server receives recurring node reset messages. Product Line Satchwell BAS & Sigma Environment Sigma software - all releases. Sigma firmware - all versions. Cause In the legacy BAS 2800+ system, Controllers and Terminals could share the same device numbers. Sigma, however, requires unique device numbers for all nodes. If a controller configuration inadvertently retains a reference to a terminal (with a reused device number), the controller may attempt to send messages to that device. If the referenced device is actually another controller, it will reset upon receiving unexpected messages. Resolution To identify the source of the reset messages, use one of the following methods: Method 1: Using SigView Open SigView and display all object data for the controller experiencing resets. Search for entries referencing the resetting node number, such as: T(<resetting node number>) Investigate any such references and correct the configuration. Method 2: Using Wireshark Disconnect the affected controller from the network. Connect a laptop configured with the same IP address as the controller. Run Wireshark to capture network traffic for a duration longer than the reset interval. Filter the capture to show only messages sent to the IP address of the resetting node. Identify the source IP address of these messages. Use SigView to inspect the configuration of the source controller. Example: A Wireshark trace filtered by Source IP Address can help pinpoint the origin of the problematic messages. Additional Resources Using Wireshark to Analyse Communications on an Ethernet Network

Issue Clarification of setup requirements for a basic Sigma Autodial configuration involving one main site and one remote site. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma System with Remote Autodial Sites Cause Sigma Autodial systems are used in scenarios where remote sites lack permanent IP connectivity to the central Sigma Server. Instead, communication is established on-demand via modem dial-up. This configuration ensures: Reliable data exchange over PSTN lines. Cost-effective remote access without requiring continuous network presence. Compatibility with legacy infrastructure where IP networking is limited or unavailable. Resolution A simple Autodial configuration consists of: Main Sigma Site (with Sigma Server and DNN) One Remote Site (with Sigma Controller and Modem) Although based on Sigma 4.05 SEB, the general steps apply across all Sigma releases. Configuration Steps 1. Sigma Server Setup Refer to Autodial Setup.doc for detailed configuration. Download the CO??.set file to the DNN. Connect the modem to the DNN (specify port, e.g., COM1 or COM2). Use the correct connection lead (see Autodial connection lead.jpg). 2. Network Routing Configure RIP Listener on the Sigma Server. If RIP is unavailable, use Persistent Routes: route add -p 192.168.100.0 MASK 255.255.255.0 10.158.72.123 # Ethernet network Reference: Persistent Routing on Sigma Server 3. Remote Site Setup Connect the modem to the controller (specify port). Use the correct connection lead. Locally connect to the controller and download the CO??.set file. Perform a Coldstart on the controller. Allow recovery from the Default Sigma Server. 4. Testing Request data from the remote site. Confirm that the modem initiates dialing as expected. Attachments Autodial Setup.doc Autodial connection lead

Issue When Remote Alarm Manager (RAM) attempts to initialize the GSM modem, it fails during the reset command. However, the modem responds correctly when the same commands are sent via a terminal emulation program. Product Line Satchwell MicroNet, Satchwell BAS & Sigma, TAC Vista Environment Remote Alarm Manager (RAM) GSM Modem Cause The GSM modem returns result codes in a format that is not compatible with RAM’s GSM driver. RAM expects numeric result codes, but the modem may be configured to return verbose or generic error messages. Resolution To ensure compatibility, configure the modem to return numeric error codes using the AT+CMEE command. Steps to Configure the Modem: Connect to the GSM modem using a terminal emulation program (e.g., HyperTerminal or PuTTY). Check current error format: AT+CMEE? Returns the current setting (0, 1, or 2). Set error format to numeric: AT+CMEE=1 Save the setting to non-volatile memory: AT&W Disconnect the terminal program and retest with Remote Alarm Manager. AT+CMEE Format Options: Value Description 0 Disable result codes; returns ERROR 1 Enable numeric result codes 2 Enable verbose (text) result codes

Issue Alarms generated on the Sigma system are not appearing in the Alarm Manager window of either the local or remote Sigma clients. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma 4.04 or later Cause Follow these steps to ensure proper alarm routing to Sigma clients: 1. Confirm Client Alarm Configuration Open Sigma System Setup. In the tree structure, navigate to: Clients → [Select the required client] Ensure the correct Sigma server is selected from the list. 2. Verify Routeset Assignments In the tree structure, navigate to: Controllers → Routesets   For each routeset, confirm that the intended client is selected to receive alarms. 3. Download Updated Routesets If any changes were made to the routesets, download them to all Sigma controllers to apply the configuration.

Issue Sigma clients that were previously used remain listed in the Registered Clients list, even if they are no longer active or required. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma clients are retained in the system registry after use. These entries do not automatically clear and may persist unless manually removed. Important: A Sigma client cannot be deleted if it is still associated with a Sigma server. Resolution To remove outdated or unused Sigma client entries: Open the Sigma System Setup application. Navigate to the Clients menu. Select the client entry that is no longer needed. Once highlighted, delete the client using either: The delete icon, or The File > Delete option from the menu. ⚠️ Note: If the client is still linked to a Sigma server, deletion will not be permitted. Refer to the related article: Sigma client cannot be deleted for further guidance

Issue IAC touch screens unexpectedly reset to their default address (65) every Sunday when time broadcast is enabled. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Enterprise Server Building Operation Automation Server MicroNet transition IAC touch screen Cause When the AS or ES broadcasts time to MicroNet devices, the day number is incorrectly sent as 0 on Sundays instead of 7. The IAC touch screen does not recognize day 0, which triggers a reset to factory defaults, including its network address. Impact: The touch screen resets to address 65. If the original address was not 65, communication with controllers on the SubLAN fails. Manual reconfiguration is required to restore connectivity. Resolution The issue is resolved in SBO version 1.8 and later. ⚠️ 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.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Remote Tools: RealVNC, TeamViewer, LogMeIn, UltraVNC, etc. Cause Remote control software may not fully render graphical elements or interactive UI components of BMS applications. This is often due to: Graphics acceleration limitations UI rendering differences between local and remote sessions Security or permission restrictions in remote sessions Example: When using RealVNC to access the SmartStruxure License Administrator, the dropdown menu for adding license details may not appear, even though it functions correctly in a local session. Resolution Local Verification: Run the BMS application directly on the host machine to confirm full functionality. Remote Software Settings: Enable full desktop rendering or mirror driver (if available). Disable any performance optimizations that reduce UI fidelity. Alternative Access Methods: Use Remote Desktop Protocol (RDP) instead of third-party remote tools. Consider web-based access if supported by the BMS platform. Additional Notes These issues are not specific to one remote control tool; they may occur across various platforms.

Issue When a Sigma animation is created, the object is assigned and the graphic is run, but the animations do not move or rotate as expected. Product Line Satchwell Sigma Environment Satchwell Sigma Graphics Cause The animation configuration parameters (e.g., frames, pitch, dimensions) may not match the actual structure of the animation bitmap file. This mismatch prevents proper rendering or movement of the animation. 🔍 Note: If you're using a BAS Legacy animation, refer to the related article: BAS Legacy Animations Are Not Moving in Sigma Graphics Resolution Follow these steps to correctly configure the animation: 1. Locate the Animation File Navigate to: C:\Sigma\Data\Graphics\Animations\ Identify the relevant .bmp animation file (e.g., fan animated 4.bmp ). 2. Inspect the Bitmap in Microsoft Paint Open the file in Microsoft Paint. Note: Frames Across (number of frames horizontally) Number of Rows (vertical frames) 3. Update Animation Properties in Sigma Change the Frames Across and Num Frames (rows x frames across) to that seen in MS Paint. Change the Width and Height by sizing the image in the preview window so that only 1 animation is visible e.g. 1 fan. Change the Horz Pitch and Vert Pitch so that the animation moves completely to the next animation in 1 step. Example: fan animated 4.bmp will be Frames Across = 4 Num Frames = 8 Start Col = 1 Start Row = 1 Width = 267 Height = 267 Horz Pitch = 267 Vert Pitch = 267

Issue When installing Sigma 4.08 using a software license, the following error appears in the License Administrator after entering the Entitlement ID: “Unable to connect to 'Server'” Product Line EcoStruxure Building Operation Environment Satchwell Sigma Building Operation License administrator Cause The License Administrator requires an active internet connection to communicate with Schneider Electric’s online licensing server when validating or activating an Entitlement ID. If the PC is offline, the License Administrator cannot reach the server, resulting in the error. Resolution If internet access is not available, use the Offline Activation Tool to activate the license manually: 🔧 Offline Activation Process Download the Offline Activation Tool Offline activation Tool Generate a Request File Open License Administrator Enter the Entitlement ID Choose Offline Activation Save the generated request file Transfer the Request File Move the file to a PC with internet access Upload to Licensing Portal Go to the Schneider Electric Licensing Portal Upload the request file Download the response file Activate License Transfer the response file back to the original PC Load it into License Administrator to complete activation

Issue Users are unclear about how to complete the offline registration process in EcoStruxure Building Operation, particularly regarding the location and use of the System ID and Registration Code. Product Line EcoStruxure Building Operation Environment EBP Systems requiring offline activation Cause This confusion arises due to: Misinterpretation of the registration email: Users expect both the System ID and Registration Code to be included, but only the System ID is provided. Limited visibility of the registration code: The code is only shown in the browser on the online machine used for registration. Manual transfer requirement: Users may not realize that the registration code must be manually copied to the offline machine. Uncertainty around System ID resets: Users may not know how or when to reset the System ID, especially after hardware changes or reinstallation. Resolution System ID Visibility: The registration email contains only the System ID. The registration code is not included in the email. Where to Find the registration Code: The registration code is displayed in the web browser on the online machine during the registration process. This code must be manually copied and entered into the offline machine to complete activation. Resetting the System ID: If a reset is required, refer to the official guide: 🔗 Reset System ID – EcoStruxure Building Help Offline registration Instructions: 🔗 Offline Registration Guide 🔗 Registering Your System Offline Dialog Box

Issue The official documentation lacks clarity on how the EPU305LCD behaves in bi-directional mode, especially compared to unidirectional mode, and how reverse flow is interpreted. Product Line Field Devices. Environment EPU305LCD. Cause The confusion arises due to: Limited explanation in datasheets regarding how pressure differentials are calculated and displayed in bi-directional mode. Misinterpretation of analog output scaling, especially when switching between modes. Assumption that reverse flow is directly measured, whereas the sensor only calculates differential pressure between its ports. BMS misconfiguration, where systems expect unidirectional scaling and misinterpret negative values. Resolution Key Differences Between Modes Mode Display Range Behavior Unidirectional 0 to 50 Pa Only positive pressure differences are displayed. Bi-directional -50 to +50 Pa Displays both positive and negative pressure differences.   Note: The EPU305LCD does not directly measure reverse flow. It calculates the pressure differential between the positive and negative ports. Example Calculation Positive Port: 10 Pa Negative Port: 15 Pa Bi-directional Mode Result: -5 Pa Unidirectional Mode Result: 0 Pa (negative values are suppressed) Display Behavior When DIP switch 3 is enabled for bi-directional mode: Display shows “SEL -50” to indicate the selected range. Briefly shows “SET” when a new range is selected. Analog Output Ranges Configuration Analog Output Unidirectional Range Bi-directional Range 3-Wire 0–10 V / 0–5 V 0 to 50 Pa -50 to +50 Pa 2-Wire 4–20 mA 0 to 50 Pa -50 to +50 Pa   All ranges are configurable for either mode. Lower ranges are ideal for detecting small pressure differences. Higher ranges suit larger pressure measurements. Application Notes   Use bi-directional mode when monitoring both positive and negative pressure differentials is required. When switching modes, SCADA systems may show different readings due to scale changes—this is expected and normal.

Issue During installation of hotfix for EBO you get a "Hotfix file signature validation" error saying that Device Administrator cannot verify the issuer of the file signature's certificate.   In older versions of Device Administrator you might get an alternative error message "Invalid hotfix file" saying that the file does not have a valid Schneider signature. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Device Administrator Offline system Version 3.1 and later Cause EBO hotfixes for SmartX Server are signed with a certificate to ensure that only valid files can be used. This certificate must be validated before you can use a new PC to install a hotfix. If the PC has not had any internet connection while previously installing a hotfix or does not have an internet connection, the certificate cannot be validated and hotfix installation therefore fails. Resolution There are two solutions Solution 1 Connect your PC to the Internet and install the hotfix on a SmartX Server. The certificate is validated, and the PC can subsequently be used to install hotfixes on other SmartX Servers, even if you are offline. Solution 2 You can manually import certificates and CRL (Certificate Revocation List) Download and save the following files: http://s1.symcb.com/pca3-g5.crl http://sv.symcb.com/sv.crl If the above URL's are blocked by your browser please download them here or the attached ZIP file.  Start a command prompt (cmd.exe) as administrator. Browse to the folder where the files from step 1 are stored. Run the following commands: CertUtil -AddStore CA pca3-g5.crl CertUtil -AddStore CA sv.crl Export host, intermediate, and root certificates from the hotfix file. Install the 3 certificates with the default selection. Restart Device Administrator and install the hotfix. Video for step 5 and 6:     November 2025: Added Intermediate and Root Certificates for Global Sign. Root: GlobalSign Timestamping Root R45 Intermediate: GlobalSign R45 AATL TimeStamping Root CA 2021

Issue Customers or internal teams require documentation for Unifact Pro controllers or the NCP Palm engineering tool, but these resources are no longer publicly available due to product obsolescence. Product Line Satchwell MicroNet Environment Unifact Pro NCP Palm Cause The Satchwell MicroNet product line has been officially retired. As a result, associated documentation is no longer hosted on public platforms or Schneider Electric’s external portals. Resolution The following documents can be downloaded directly: 📄 Document 🔗 Download Link Unifact Pro Controller MLi MLI13303-1205.zip Unifact Pro Controller Data Sheets Unifact Data sheets.zip NCP Palm Engineering Guide NCP Palm Engineering Guide-0106.zip ✅ These documents are useful for understanding controller specifications, wiring, and communication setup using IR tools or RS-485 converters. Additional Notes These resources support field engineers and partners working with legacy Satchwell MicroNet systems. For long-term support and cybersecurity compliance, consider recommending migration to EcoStruxure Building Operation (EBO).