Issue A License Violation alarm is triggered without displaying a License Violation banner. Alarm reactivates after acknowledgment, approximately every 10 minutes.   Device Administrator also shows a license violation in "License status," when all servers show no violation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Potential communication issue, possibly related to return path or port configuration. An incorrect ES port may be in use, which could be contributing to the issue. The Communication Tab [Communication View] and Server List in xbk Analyzer show only the ES, indicating limited server visibility. Resolution Verify Communication Path Ensure the ES is defined as using the same ports across all servers. Confirm that the ports are correctly configured and open on all relevant servers. Review the Communication Tab [Communication View] and Server List Check that all expected servers are listed and actively communicating. If only the ES is visible, investigate potential network or configuration issues. See article for additional information: Updating a Enterprise Server IP Address - Schneider Electric Community Check AS Logs Log in to the Automation Servers to identify any communication errors. These errors may not be visible from the ES alone. Next Steps If the above steps do not resolve the issue or the root cause remains unclear: Refer to the article for possible communication-related troubleshooting options: Enterprise Server and Automation Server Bindings show Unresolved - Schneider Electric Community Refer to the article for additional license troubleshooting options: Troubleshooting EBO license violation issues - Schneider Electric Community Contact your local support organization for further assistance.

Issue The panel displays a Low Battery Voltage (With Charger Trouble) condition. This is accompanied by General Trouble and Power Trouble LEDs being ON. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Warning Hazard of Electric Shock: Battery terminals and leads are not power-limited. Short circuits can cause a fire or an explosion. Use extreme caution while connecting or disconnecting standby batteries. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Possible causes of this issue include: Battery impedance exceeds acceptable limits This can occur after several years of use as batteries degrade. Mixing different battery brands or using batteries of the same brand but with different ages (e.g., one new and one old) can also cause this issue. Faulty power supply If the power supply is malfunctioning, it may not charge the batteries correctly, triggering the fault. Resolution Step 1: Replace the existing batteries with a new set from the same brand. This often resolves the issue if battery impedance was the root cause. Step 2: If the issue persists after replacing the batteries, the power supply may be faulty. In this case, replace the power supply unit. After replacing either the batteries or the power supply, the panel should return to normal operation.

  Issue How can I troubleshoot communication issues between SEAL app and EBO server? Does the SEAL app provide a detailed log for troubleshooting communication issues between the app and the EBO server? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Ecostruxure SEAL Cause When troubleshooting SEAL communications issues to an EBO server, it may be helpful to get deeper information about the communication between the server and the SEAL application. To do this the following lines can be added to the appsettings.json application settings file as described below in the resolution Resolution Browse to C:\Program Files\Schneider Electric\SEAL Open the file appsettings.json. Depending on your user rights, you may need to copy and edit this file in another folder Go to line 26. After the closing brace }, enter a comma ,  Paste the following: "Serilog": { "Using": [ "Serilog.Sinks.File" ], "MinimumLevel": { "Default": "Information", "Override": { "Microsoft": "Warning", "Microsoft.Hosting.Lifetime": "Information", "SE.SEAL": "Debug", "SE.SEAL.Web.Auth": "Verbose" } }, "WriteTo": [ { "Name": "File", "Args": { "path": "%LOCALAPPDATA%/SEAL/logs/SEAL.txt", "rollingInterval": "Day", "shared": true } } ], "Enrich": [ "FromLogContext" ] }   Save the file. Try logging into the SEAL app and connecting to the EBO server Save the log found under: %LOCALAPPDATA%/SEAL/logs/SEAL.txt Restore the appsettings.json file to its original state.   Attached to this article is a ready-made file for use. Move the original file to another folder Place the attached file in C:\Program Files\Schneider Electric\SEAL After saving the logs, delete the attached file Move the original file back to its original location   In addition to this, it is always recommended to take an event view - Application log

Issue Having issues with the panel's networking and unable to operate the touch screen or receive trouble messages on the screen. Product Line ESMI Fire Detection. Environment FFSULH1009. Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause The display touch screen may not be working. Resolution You can identify the current situation by checking the LED status as described below:    LED Status LED indicators provide diagnostic information to identify communication.   LED Label  Name  Color  Description LED 1 Heartbeat Red Identifies functional status. LED 2 Tx Comms Green A blinking green light indicates that the module is transmitting data. LED 3 Rx Comms Green A blinking green light indicates that the module is receiving data. LED 4 Trouble Yellow A flashing yellow light identifies an error condition. LED 5 Not In Use Green Not In Use LED 6 Not In Use Green Not In Use LED 7 Not In Use Yellow Not In Use LED 8 Comms for SPI Bus Green Communication present when flashing LED 9 Full Duplex Yellow Full duplex (on) half duplex (off) LED 10 Ethernet Speed Red 10MHz (off), 100MHz (on) LED 12 Communication Green Communication present when flashing   Refer to ESMI Ultima Networking Troubleshooting for further assistance with network related problems

Issue How is the Otis elevator destination dispatch system configured in Access Expert? Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Otis elevator system Mercury controller LP4502/EP4502 Cause Configuration steps needed for Otis Destination Dispatch in Access Expert Resolution An Otis Elevator Compass Destination Dispatching System model allows the LP/EP4502 to inform Access Expert if a cardholder is allowed and authorized for specific floors.   Elevator Control Types in Access Expert There are 2 main types of Elevator control in Access Expert: Basic - does not track the destination of the elevator and cardholder Destination Dispatch - tracks the destination of the elevator and the cardholder Licensing & Hardware Requirements License required: FN-DEST-OTISRS Controllers: LP4502 or EP4502 Mercury Recommended Adapters: LP4502: Micro-B USB adapter (Pluggable USB2-OTGE100) EP4502: USB 2.0 adapter (Pluggable USB2-E100 Hardware Setup: Connect the USB adapter to the controller and connect the Ethernet cable for the NIC2 to the Otis network. Log in to the controller page and navigate to the Network page Under Interface 2 (NIC2), select Static IP Type 192.168.50.250 in the IP address field. Type 255.255.255.0 in the subnet mask field. Click on Accept at the bottom of the page. Navigate to Apply Settings. The controller should reboot to apply the changes. Mercury Controller Configuration Ensure the following routes are configured in the Mercury Controller web interface. Feenics Setup From the Controller Page in Feenics: On the LP/EP4502 controller page, navigate to the "Destination Dispatch" Tab, located on the bottom of the page. Select Otis. Update the floor offset to reflect your Otis setup. The offset must be greater than or equal to 0. Make sure to take into consideration this offset when assigning elevator floor access. Enable "Has front and rear floors" if your Otis setup has front and rear floors.  Make sure to take into consideration this flag when assigning elevator floors access. Enable the "Primary Otis controller" option. Press Save. Issue a "Push Controller Database" command.   Note: The Otis Destination Dispatch Systems can only support one EP/LP4502. In order to support multiple EP/LP4502’s, a Primary and Secondary needs to be configured. The Primary EP4502 will manage communications to the Otis DDS. Communications between the Otis DDS and the Secondary EP4502’s will have to go through the Primary EP4502.   Reader Page: On the reader page, navigate to the "Elevator" tab and select "OTIS Destination Dispatching" as the Elevator Type. In the Dispatch IP enter the DEC (Destination Entry Computer "Touch screen or Keypad") IP address. For the Elevator Dispatch Mode, select the desired mode. You can hover over the tool-tip to read a description of the mode. If desired, select an Override Elevator Access Level. This will allow a set of floors to be public during defined schedules. Press Save. Look for an "Otis DEC {Reader} is Online" event in Live Monitoring that reports the controller communication with the DEC. The controller will report "Otis DEC {Reader} is Offline" if the communication between it and the DEC drops. Person Page: On the person page, navigate to the "Destination Dispatch Settings" tab. On the "Otis Settings" tab, click on "Add Otis Setting". Select the Otis controller and press OK. Select a Default Floor and Floor side. This floor will be served when a DEC is set to Mode 1. Select User flags. Note that Standard and ADA are mutually exclusive. Cardholder Flag selection descriptions: Standard - Standard access, speed and features. Disability - When checked, this indicates the cardholder has a disability. The Otis system recognizes this indicator and cab be set up to provide special accommodations (such as dispatch an adjacent car, extended time to board an elevator car, provide audible announcements at each floor). VIP - When checked, this indicates the cardholder is a VIP. The Otis system can be set up to dispatch an empty elevator car that runs non-stop to the destination floor. Vertigo - When checked, this indicates the cardholder experiences vertigo. The Otis system can be set up to accommodate this passenger by not dispatching them to a glass elevator. SplitGroup - When checked this indicates the cardholder belong to a split group. The Otis system is set up to recognize this person as belonging to a separate group of passengers who use a separate elevator car(s) that is not used by the general population (such as service elevators where technical or service staff do not mix with regular guests). Vertigo2 - no description  CartSvc - no description CIMOverride - Compass Inter-floor Matrix override. This overrides the segmentation used to place certain tenants into certain elevators. Technical Notes DECs must be represented by readers which can be connected to "fake" downstreams such as the MR52. The Cab used will be sent by the Otis system to Feenics upon access granted and displayed in event data.

Issue Customers using Device Administrator for offline license activation in EBO 7.0.3 face challenges due to changes in how entitlements are delivered via Software Companion. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator (v7) Software Companion Portal FlexNet Licensing Portal Offline systems (no internet access) Cause The current Software Companion tool does not generate an HTML entitlement certificate compatible with Device Administrator. Instead, it provides a PDF summary, which the Device Administrator cannot read or import. Resolution The simplest way is to enable Internet access for Device Administrator and add the entitlement ID. To activate licenses offline in Device Administrator: Do not use the PDF summary generated by Software Companion — it is not compatible with Device Administrator. There are several options available, each differing in complexity and time requirements. Webhelp(Adding an Entitlement without the HTML file when a Field Server is not Connected to License Server (FNO)), users can follow the follwing steps: In Device Administrator, click Entitlements. Click the Add Entitlement down arrow and click Manually Enter the entitlement ID. Click Next. Click Skip. If you know that you do not have any server connected to internet in the list, click Skip. If you do not click Skip, Device Administrator goes through all servers in your list until it finds one that is connected to internet. In the Entitlement Products - Enter Manually list , enter the Activation ID, Description and seat count for the product. Click Add Product , to add more products. Click Add. Note: It is recommended to verify the Activation ID, Description, and seat count in FlexNet Operations End-User Portal before proceeding with the steps. When there is no connection between the EcoStruxure BMS Server and License Activation Server, Device Administrator cannot synchronize the number of licenses in the entitlement that are available for activation. Instead, Device Administrator assumes that all licenses that was purchased can be activated.  Access the FlexNet Licensing Portal: FlexNet Operations End-User Portal Log in using the Entitlement ID. List all Entitlements. Select one Activation ID Use the View Certificate option. Download and save the certificate locally in HTML format. When using Save As - ensure you select the "Webpage, complete (*htm;*html) option  Repeat for each Activation ID listed in the Entitlement Import each HTML certificate into Device Administrator to load the entitlement offline. Create a server list away from the site, using Device Administrator, that has Internet access. Caution: this will wipe the current server list, remove all certificates (if used), and remove all servers added to Device Administrator. If the server list has already been created on site, save and export this list. Off-site or on a PC with Internet access, import (from step 1) or create a new server list in Device Administrator. Add the necessary entitlement IDs. Save and export the server list. Back on the on-site PC, import the exported server list to Device Administrator. If using a new server list (that is, no servers added from Step 1), add the required certificates and servers. Save this new list. It is advisable to export it as a backup in case of any issues. Proceed with the offline activation. EcoStruxure BMS Server Licensing on Servers not Connected to Internet Workflow. Once activated, remember to save and export the list for safekeeping. Comment: Investigation into why Software Companion does not generate HTML certificates is ongoing.  Device Administrator still requires either the HTML certificate or manual entry of activation IDs.

Issue When a Reader Expander is offline from the controller, users with Credential Type-based access are unable to be authenticated. Product Line EcoStruxure Security Expert Environment Security Expert SP-C, SP-AC1, SP-ACX SP-RDM2, SP-MRDM2 Cause Reader Expanders store a limited number of user card records locally, depending on the Offline Operation setting. However, user credentials (such as credential types, biometric or PIN-based data) are stored only in the controller, not in the Reader Expander. It’s important to note that the term "card" in the Offline Operation feature (as described in the online help and the SX-SRVR Security Expert - Operator Reference Guide) refers specifically to the Card Numbers section [1] of a user record, not the Credentials section [2]. User record Resolution The Offline Operation functionality of Reader Expanders supports authentication using Card Numbers only. It does not support authentication using Credential Types when the expander is offline.  

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

Issue Log data is not being logged into SQL. The Reports Server indicates that the database is full.   This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL. Product Line EcoStruxure Building Operation Environment Reports Server Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server. If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.   Resolution To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."   If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.     The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database: Download the latest SBO Reports Agent Config tool from the community. Load the Tool onto the Reports Server PC. Stop the Reporting Agent Using the Tool Press F7 to get to the Advanced Agent Configuration Page Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database. Press Ok Under the Maintenance tab of the tool - there are two options under Events  Delete future events, alarms, and trends  Delete events and alarms older than... Restart the Reporting Agent This will stop any further Events from being passed through to the SQL Database.  

Issue Unrecognized user connection in EBO Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause When browsing through System>Diagnostics>Users in Webstation, an unrecognized "root" user appears in the user session list. Resolution The 'root' user is a built-in system account used to help different parts of EBO—like EC, ES, and AS—communicate with each other. It’s automatically used when the system is not running in standalone mode. This account allows the systems to connect and share data securely in the background.

Issue Panel showing detector Calibration error. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. Cause When the contamination increases significantly and exceeds the sensitivity range for the smoke sensor, it is no longer able to perform calibration, causing a calibration error. Resolution Understanding the Calibration Process: The Esmi Ultima panel performs daily calibration and drift compensation for all addressable smoke sensors at 7 AM by default. Sensitivity and Contamination: Over time, dust and other contaminants can build up in the chamber of a smoke sensor, increasing its sensitivity. Illustration: Left Image: Clean sensor requiring 2.0% per foot of smoke to activate the fire alarm. Right Image: Contaminated sensor with increased sensitivity, requiring less smoke to reach the alarm threshold of 2.0% per foot. Trouble Condition: When the panel can no longer compensate for the contamination, it indicates a trouble condition. The Esmi Ultima panels can compensate for contamination build-up in addressable smoke detectors and addressable multi-criteria detectors. Daily calibration offsets any contamination, ensuring each smoke detector remains within its UL Listed sensitivity range. Recommended Action: Clean or replace the sensor with a new one of the same model. If you have a replacement in stock, replace it immediately.  

Issue Unable to configure reverse proxy for SAML-based Single Sign-On (SSO) in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause Although EBO 7.0 has enhanced reverse proxy support, this does not include SAML SSO and EBO does not support reverse proxy configurations for SAML SSO.  This limitation prevents successful integration when a reverse proxy is used in the authentication flow. Resolution At this time, EcoStruxure Building Operation version 7.0 does not support reverse proxy configurations for SAML SSO. This is a known limitation. An enhancement request has been submitted to the Idea Forum to address this functionality in future releases.   To support this request, please visit the Idea Forum and click the thumbs-up icon on the SAML reverse proxy support idea to increase its visibility to the product management team.

Issue After making changes to object names in the system, outdated or incorrect names may still appear under the Hardware folder in EcoStruxure Web Services (EWS).     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) EcoStruxure Security Expert Smart Connector Integration EcoStruxure Web Service (EWS). Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause When significant changes are made to object names in the system, the Smart Connector may retain outdated data. If a standard Discovery does not update these names, the most effective solution is to clear the Smart Connector database and re-establish the connection.   Resolution To clear the outdated data from the Smart Connector:   Step 1: Access the Smart Connector Portal Open a browser and navigate to http://localhost:8082 (assuming Smart Connector is installed locally). Log in to the Smart Connector Portal. Step 2: Delete the Existing Processor Configuration Go to Configurations → Processor. Locate the Security Expert Discovery Processor. Click the Delete (bin icon) next to it. ⚠️ Do not delete other processors (e.g., Alarm Processor). Step 3: Delete the Existing EWS Server Navigate to the EWS Servers section. Locate the SecurityExpertServer. Click the Delete (bin icon) to remove it.   Step 4: Reconfigure the Processor and EWS Server Follow the instructions in Section 4.4 of the referenced document [1] to: Add a new Security Expert Discovery Processor Configure a new EWS Server Allow 10–15 minutes for the initial discovery process to complete. This will create a fresh snapshot of the current Security Expert database. Once the discovery is complete: Refresh the Hardware folder in EcoStruxure Building Operation. Rehost the new EWS objects as needed. Step 5: Verify Alarm Processor Configuration After re-adding the EWS Server, ensure the Alarm Processor is correctly configured to reference the new server. Refer to Section 4.5 of the same document [1] for detailed steps.   Reference [1] Refer to the official integration guide documentation for more information. Security Expert SmartConnector Version 1.1.0.8 - Installation & User Manual  

Issue The panel displays an Address 1 has a wiring trouble condition. This is accompanied by a General Trouble alert. Product Line ESMI Fire Detection. Environment FFSULH2007. Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Cause The system is showing a wiring trouble condition at Address 1. To view more details, press the “More Details” button on the panel. This issue originates from the Input Module (FFSULH2007). Resolution The Input Monitor Module provides contact monitoring circuits for equipment that uses a dry contact signal. Typical Connection Diagram The diagram below shows a typical connection of the input module with the monitored equipment. The circuit is monitored for wiring faults using an End-of-Line (EOL) resistor, which should be installed at the last point of the circuit. Note: The EOL resistor is supplied inside the module box. Troubleshooting Steps If the EOL resistor is removed or discarded, or if the wiring is broken, the module will detect a loss of resistance and generate a wiring trouble alert. The installer must ensure: The EOL resistor is properly connected at the last point of the equipment. Any broken wires are repaired or rejoined. Once the wiring and resistor are correctly installed, the trouble condition will automatically clear.

Issue The panel displays a Process Watchdog Operated condition. This is accompanied by General Trouble. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Cause The system has reported a watchdog trouble due to a malfunction in the main processor unit located on the LCD backboard. During this condition, the Watchdog LED will illuminate. Resolution Locate the LCD backboard: On the back side of the LCD board, find the reset switch (red-circled area in the reference photo). Reset the watchdog condition: Press and release the reset switch to reset the watchdog condition. Observe system behavior: If the system recovers to normal operation, no further action is needed. If the watchdog trouble persists, proceed to replace the LCD main processor board.

Issue Removal of the Mobile Profile in N4.15 Product Line TAC IA Series. Environment I/A Series N4.15 Jace I/A Series N4.15 Enterprise Server Cause The Niagara Mobile Profile has been removed from Niagara 4.15 Resolution Since the Niagara Mobile APIs were deprecated and replacements provided in N4.6,  Niagara Mobile has been removed in N4.15. The standard HTML5 Hx Profile is mobile friendly and users configured with the BDefaultMobileWebProfile will automatically be switched to the HTML5 Hx Profile. When you start up a N4.14 station in a N4.15 environment for the first time and it was configured for using the mobile profile, you should see this warning:   "WARNING [14:06:11 22-May-24 EDT] [web] Support for the "Default Mobile Web Profile" has been removed. Users with this profile have been switched to the "Html5 Hx Profile".

Issue The panel displays a Low Battery Voltage (No Charger Trouble) condition. This is accompanied by General Trouble and Power Trouble LEDs being ON. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Warning Hazard of Electric Shock: Battery terminals and leads are not power-limited. Short circuits can cause a fire or an explosion. Use extreme caution while connecting or disconnecting standby batteries. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause The issue may arise due to one of the following scenarios: Newly Installed Batteries Battery voltage may be low initially. Allow the system to charge for a few hours. The trouble condition should clear automatically. Panel Running on Batteries (No AC Supply) Extended battery use without AC supply can drain voltage. Once AC power is restored, charge for a few hours. The issue should resolve itself. Panel on AC Supply but Still Showing Trouble Batteries may be aged or degraded. If the issue persists after charging, replace the batteries. After replacement and charging, the panel should return to normal operation.   Resolution Scenario Action New batteries Charge for a few hours No AC supply Restore AC supply and charge Aged batteries Replace and charge

  Issue RP-C contains 2 Modbus devices of the same type on the Modbus interface, one of the Modbus devices reports error 'Value Invalid reference type for HMI' when points with HMI as control mode are downloaded.       Product Line EcoStruxure Building Operation Environment Detected in version EBO 6.0.3.112 and above Cause Modbus point with Control Mode set to HMI will fail to download to RP-C if its reference is invalid. Create a folder in an RP Application folder called 'Test 1'. Create an Analog Value object in the ‘Test 1’ folder. Create a Modbus Device and add a Modbus Analog Output Point to it. Click on the gear to the right of the ‘Value’ property in the new ‘Modbus Analog Output Point’ and reference the Analog Value/Value from step 2. Set the ‘Control mode’ of the ‘Modbus Analog Output Point’ to HMI.   Edit the reference from step 2. so that it manually looks for ‘Test 2’. A warning appears indicating that the reference is invalid and Control mode is automatically set back to ‘Write only’. Change the ‘Control mode’ back to ‘HMI’ and Save, the system displays 'Value Invalid reference type for HMI' error.   Resolution A valid reference must be defined to a Modbus point with control mode set to HMI so that it can be downloaded to RP-C.   From step 4. set the reference back to a valid one ' Test1/Analog Value/Value ' and download the object to RP-C.  

Issue After installing or upgrading the Security Expert SOAP Service to 1.7.0 (or above), the Building Operation EcoStruxure Web Services (EWS) Hardware folder (container) under SecurityExpert appears blank, preventing users from viewing or Not possible to Host EWS Objects Objects in Building Operation no longer update Product Line EcoStruxure Security Expert Environment Building Operation Enterprise Server EcoStruxure Web Services Security Expert SOAP Service: Version 1.7.0.0 or greater Smart Connector Framework Version 2.5.5.108 Security Expert Smart Connector Extension: Version 1.2.0.22 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed correctly. Before beginning these steps, make sure all essential data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This issue typically occurs when: Incompatible versions of SOAP, Smart Connector, or Security Expert are installed. The latest (or higher) Security Expert Smart Connector Extension (v1.2.0.22) is not used. The installation guide referenced is outdated and does not reflect the latest version requirements. Resolution To resolve the issue, follow these steps: If upgrading Security Expert, it is recommended to Uninstall any existing versions of: EcoStruxure Security Expert SOAP Service SmartConnector Framework Security Expert Smart Connector Extension Install the following versions as per the Instructions provided in Step 3: SOAP Interface: 1.7.0.0 or greater SmartConnector Framework: 2.5.5.108 EcoStruxure Security Expert: 4.3.370.1 or greater Security Expert Smart Connector Extension: 1.2.0.22 Follow the instructions in the updated installation manual: schneider-isc.uk/file/  Search for Document name Security Expert SmartConnector Version 1.2.0.22 - Installation & User Manual Download Extension v1.2.0.22 → Using this link schneider-isc.uk/file_download/, navigate to Smart Connectors Security Expert Smart Connector Extension V1.2.0.22.zip Additional Notes The current Security Expert - Smart Connector Extension - Installation Guide on the EcoXpert site does not yet include version 1.2.0.22. An update is pending. Please use the link above. Always verify that all components are aligned with the supported versions listed above.   .

Issue A method is required to purge orphaned ImageData records from the Security Expert database to free up hard drive space. Product Line EcoStruxure Security Expert Environment Security Expert  Microsoft SQL Server Management Studio (SSMS) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause Running the SSMS Disk Usage report indicates what tables are the largest. The ImageData table is often one of the largest in the report and queries are needed to purge records. During transitions from Continuum, if Personnel/User records are removed, the GA_Blob table converts to the ImageData table. However, orphaned records may remain in ImageData because deletions in Continuum or Security Expert do not automatically remove associated image records. Resolution Use the instructions below to identify and select all ImageData records that do not belong to a user, then delete them from the database.   Note: Always validate the results of the SELECT query before running the DELETE command.   ✅ Step 1: Backup the Database In SSMS: Right-click the  SecurityExpert  database Navigate to:  Tasks > Backup Complete a successful backup before proceeding. ✅ Step 2: Identify Orphaned Records Run the following SELECT query in SSMS to identify orphaned  ImageData  records: USE SecurityExpert SELECT dbo.ImageData.ImageID FROM dbo.ImageData WHERE NOT EXISTS ( SELECT ImageID FROM dbo.Users AS T1 WHERE T1.ImageID = ImageData.ImageID ) This query will return all  ImageData  entries not linked to any user. ✅ Step 3: Purge Orphaned Records Run the following DELETE query to remove the orphaned records: USE SecurityExpert DELETE FROM dbo.ImageData WHERE NOT EXISTS ( SELECT ImageID FROM dbo.Users AS T1 WHERE T1.ImageID = ImageData.ImageID ) ✅ Step 4: Shrink the Database After deletion: Right-click the  SecurityExpert  database Navigate to:  Tasks > Shrink > Database ⏳ Note: Depending on the database size and number of records, this process may take several minutes.