Issue When viewing the Modbus property in EcoStruxure Building Operation, the status displays "Attention". Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause The "Attention" status is not documented in the Web Help, which can make it unclear what is causing this state. This status typically indicates that there is an issue occurring within the Modbus system. One common cause is an unrealistic poll rate set on a Modbus group. . Resolution If the poll rate on a Modbus group is set too fast for the server to handle—especially in large Modbus networks—this can trigger the "Attention" state. Recommended Action: Review the poll rate configured for the Modbus group. If it is set to a very low value (e.g., 1 second), increase it to a more realistic interval. For busy networks, a poll rate of 5 seconds or more is typically more achievable. Once the poll rate is adjusted to a manageable value, the Modbus status should return to "Online".

Issue When hosting objects from EWS/Smart Connector, such as Security Expert, into EcoStruxure Building Operation (EBO), additional or mismatched object names can result in unresolved bindings and duplicate EWS IDs. Common symptoms include:  - Duplicate EWS IDs with different names - Unresolved or broken bindings - Binding loss after deleting containers   Duplicate EWS IDs with different namesDuplicate EWS IDs with different names Unresolved or broken bindingsUnresolved or broken bindings     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) 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 Typical reasons for this to occur: Hosted object names do not match those in Security Expert. Deleting containers without proper renaming can cause binding loss. Resolution   Best Practices for Future Hosting Always rename the hosted object in EBO before rehosting from the hardware folder. This ensures that existing bindings are preserved. Avoid hosting the entire `SecurityExpertServer` container—only host changed or new objects. For Unbound or Irrelevant Objects: - If objects have no bindings, naming is not critical from an EBO perspective - Delete the container and rehost the object from the **Hardware folder**.   To Retain Existing Bindings  Identify the correct object name in the Hosted Containers folder  Copy the name to avoid typos. Delete the duplicate object with the correct name. Rename the existing EWS ID to match the copied name. Save the rename Verify bindings: Right-click the renamed object Select Delete Click Show References Confirm bindings are still valid. Click No to cancel deletion. Repeat this process for each object (inputs, outputs, doors, etc.) that has existing bindings.  

Issue The internet is not working at the site, so it's necessary to verify that all antenna connections are secure and the SIM card is correctly placed. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal 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. 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 The Flex Server powers up successfully at the site, but the internet connection fails. This issue might arise if the antenna or SIM card was displaced, disconnected, or damaged during transit due to mishandling. Therefore, it's essential to verify that all connections are secure. However, the technician or engineer on-site may not be familiar with the correct slots. Resolution Carefully open the Flex Server top cover. The internal layout will appear as shown in 'Image 01' below: Image 01Image 01 Image 02Image 02 Identify the slots as follows: Slot 1: Indicates the SIM card slot. Slot 2: Located on the GSM Module marked as 'MAIN', indicates the Cellular antenna slot. Slot 3: Located on the Wi-Fi module marked as 'ANT0 WiFi', indicates the Wi-Fi antenna slot. Verify all connections and ensure they are secure. Carefully close the Flex Server cover.

Issue This issue is described in Tridium's internal case NCCB-71360. Users will notice that the default Nrio Device Manager view (Ux/web media) of the NrioNetwork driver in N4.14 looks identical to the previously existing workbench AX view; however, due to this defect, devices discovered and added through the web view will not function as expected.  Product Line TAC IA Series Environment I/A Series N4 Jace 9000 I/A Series N4.14 Framework Version Cause With the release of the Jace 9000, users may notice that the IO-R-16 and IO-R-34 devices will not function properly when discovery and configuration are performed through the web views. Resolution To tell if the device was added through the correct view, there are a few indicators. Malfunctioning devices will not show up with an Installed Version or a Sec version in either view: Working devices will display these values with no issue in either view: The malfunctioning devices' health section will read 'fail' even with a status of ok: Users in N4.14 should only use the Workbench AX Nrio Device Manager view to discover and add devices to a station. This use case is currently not supported in the browser for N4.14. All other use cases function in the UX Web Views, such as viewing devices, adding points, and commanding points.  

Issue Not able to see the network panels status, trouble messages, events, cause and effects etc. 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.   Note: Always completely power OFF the panel whenever inserting or removing hardware in the panel. Cause Networking issues can significantly impact the performance and reliability of the Esmi Ultima system. This article provides troubleshooting steps to resolve common networking problems. Resolution The following network-related troubles can occur on the Esmi Ultima Fire Alarm Control Panel. See the detailed descriptions below for explanations on each trouble message.   Trouble Message Description Network Communications Trouble This event indicates there is no communication between this panel and its neighbor. This could be caused by a configuration error (such as using the wrong baud rate), a wiring error, or damage to the wires connecting the panel to its neighbor. If this trouble occurs on one link on the panel, then the panel is still in communication with other panels on the network. If this trouble occurs on both links on the panel, then the panel is no longer in communication with other panels on the network. Note: make sure remove the 0 ohm resistance from the network card. Unexpected Network Node This event indicates a panel has been detected on the network that is not in the configuration. This is a configuration error and should never occur once the network has been properly configured. Network Card Missing This event indicates that the panel is configured for networking, but there is no network card installed, or it is installed incorrectly. This trouble may also occur if the network card processor fails. Connection Error This event indicates that the panel has failed to get a meaningful result for the link impedance measurement. This may occur if stray leakage current enters the link wiring from elsewhere, or if there is a component failure or missing jumper on the network card. This event may also be shown when the network is disconnected or when the NET OUT + wire is disconnected. Network Panel Missing This event indicates that another panel is configured but has not been found on the network. This may occur if the missing panel is switched off or disconnected from the network. This fault will also occur if there is no communication between a panel and either of its neighbors on both links. In this case, the panel will show multiple instances of this trouble; one for each other panel on the network. Network Node Double Addressed This event indicates that more than one panel on the network has the same node number. This is a configuration error and should never occur once the network has been properly configured. Full Short Circuit Trouble This event indicates that a short circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. Full Open Circuit Trouble This event indicates that an open circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. The following two troubles are optional and are not included in the default firmware build. Partial Short Circuit Trouble This event indicates that the link impedance measurement has detected an impedance below the normally expected range. Partial Open Circuit Trouble This event indicates that the link impedance measurement has detected an impedance above the normally expected range.

Issue After performing server upgrades using Device Administrator, attempts to download the database fail. The server remains in a "Ready for download" state, which cannot be cleared.   Device Administrator Download Fail error Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server. Building Operation 2023 (version 5) and above Cause This happens when a Consolidation Point (CP) or Hotfix has been applied. These updates do not include server packages in Device Administrator, causing download failures during post-hotfix upgrades.  DFU upgrades and base version upgrades of the installed Device Administrator still function as expected. Resolution This issue is cosmetic and does not impact server functionality, there’s no operational need to upgrade servers after applying a hotfix or CP. However, to clear the persistent "Ready for download" state: Navigate to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.0\Device Administrator Locate the folder: Find the folder named tmp[SerialNumber] (e.g., tmpSM22111234) that correlates to the server(s) showing the state "Ready for download" Delete all files inside that folder. Restart Device Administrator if it’s open. This will clear the "Ready for download" status.  

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 Unable to perform AET license registration online Product Line Automated Engineering Tool Environment Automated Engineering Tool Cause If a license file for AET is not found on the computer, the License Registration screen will be displayed when AET is started. By default, the New Registration button launches an online registration process, if the computer is offline or there is a problem contacting the AET License server then Offline registration is needed. Resolution AET Offline license registration process If a license file for AET is not found on the computer, the License Registration screen will be displayed when AET is started. Click the "Offline registration" button. Fill in your name, company, email address and select the license type you want. Then click "Save to file". Select a location to save the license request file, once the file has been saved to the computer, instruction on how to proceed are shown. Click OK and AET will close. Email the saved file to aet.support@schneider-electric.com the AET Support team will respond with a license. Place the supplied license in the C:\ProgramData\Schneider Electric\AET\License File folder on the computer and run AET.

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 What is the password policy for Security Expert operators, and how can it be configured to meet specific cybersecurity requirements? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Cause Some sites require customized password policies to comply with cybersecurity standards. These may include requirements such as: Enforcing regular password changes Preventing the reuse of previous passwords Setting minimum password length Requiring strong password complexity Resolution   Default Password Policy in Security Expert By default, Security Expert enforces the following password policy for operator accounts: Minimum password length: 8 characters Password change required: On first login For more information on Security Expert’s cybersecurity practices, refer to the SX-SRVR Security Expert System Hardening Reference Guide. Custom Password Policies via Active Directory Integration Security Expert does not support advanced password policy configuration directly within the client interface. However, enhanced password policies can be enforced by integrating Security Expert with Windows Active Directory. To implement this: Integrate Security Expert with Active Directory Follow the steps outlined in Option 1 of the How to Integrate Active Directory with Security Expert article or Option 2 for full Active Directory integration. See AN 288 Security Expert - Using Active Directory - Integration Guide for additional details. Configure Password Policies in Windows Domain Once integration is complete, operator accounts managed through Active Directory will adhere to the domain’s password policy. This allows you to enforce: Password expiration intervals Password history restrictions Minimum and maximum password lengths Complexity requirements (uppercase, lowercase, numbers, symbols)

Issue After correctly following the process outlined in Setup External Log Storage using MSSQL., EcoStruxure Building Operation (EBO) server fails to connect to the external database, generating the following System Alarms:  Unable to connect to data source Login failed for user The system alarm specifically details an issue with the ODBC SQL Driver as below: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium (AS-P) External Log Storage [MSSQL]  Cause The system alarm details indicate an issue with the ODBC SQL Driver, specifically: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" This suggests a compatibility or configuration issue with the ODBC driver or connection string.   Resolution The following has been seen to correct the issue: Verify User Credentials Ensure that the username and password used for the ODBC connection are correct. Note: SQL Server credentials are case-sensitive, so double-check for any discrepancies in letter casing. Remove any uppercase for the username. In some cases, using only lowercase letters for the username in the ODBC connection string has resolved the issue, e.g,. Instead of "My_User" use "myuser"

Issue If the flex server is not able to connect to the internet via the SIM card, Ethernet, or Wi-Fi, or is in a hanged state, a phone be used by the Flex server/Gateway for troubleshooting connectivity. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal 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. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work.   Cause USB Tethering may be required at times during provisioning or troubleshooting when the flex server is not able to connect to the internet via the SIM card, Ethernet, or Wi-Fi, or is in a hanged state. Resolution If a a smartphone with data connectivity and a USB cable is available, USB tethering can be used to get a Flex server/Gateway online when a Wi-Fi or Ethernet connection is not established. It essentially turns a smartphone into an external modem for your Flex server/Gateway. This guide will cover both Android and iPhone, since the steps vary slightly. What you'll need: Your smartphone (Android or iPhone) with an active mobile data plan. A USB cable that connects the phone to a computer (the same one you use for charging usually works). A Flex server/Gateway. Part 1: General Preparations (For Both Android and iPhone) Ensure Mobile Data is ON: On the phone, go to quick settings (swipe down from the top of the screen) and make sure "Mobile Data" or "Cellular Data" is turned on. Alternatively, go to Settings > Network & internet (Android) or Settings > Cellular (iPhone) and confirm it's enabled. Important: If the phone has a limited data plan, be mindful of data usage while tethering, as Flex server applications can consume a lot more data than phone apps. Charge the Phone (or Keep it Plugged In): Tethering can drain the phone's battery quickly. It's best to have the phone charged sufficiently or keep it plugged into a power source while tethering. Find Your USB Cable: Make sure you have a working USB cable that connects the phone to the Flex server/Gateway. Ensure the USB cable used is a Data cable and not a charging cable. Part 2: USB Tethering with an Android Phone Video link for Demo (The exact wording of menus might vary slightly depending on the Android version and phone manufacturer, but the general path remains the same.) Connect the Phone to the Flex server/Gateway: Plug one end of the USB cable into the Android phone. Plug the other end of the USB cable into an available USB port on the Flex server/Gateway. Note: there are 2 USB ports in the Flex Server/Gateway you can connect to either port to establish USB Tethering. The Flex server/Gateway prioritizes usb0 (the top USB) interface by default for troubleshooting purpose. USB PortsUSB Ports   Allow USB Debugging (If Prompted): When you connect the phone, you might see a pop-up on your phone asking for "Allow USB debugging?" or similar. If you do, tap "Allow" or "OK." Access the Phone's Settings: Open the Settings app on the Android phone. Navigate to Network & Internet Settings: Look for an option like "Network & internet", "Connections", or "Wireless & networks." Tap on it. Find Hotspot & Tethering: Within the Network settings, you should see an option called "Hotspot & tethering" or just "Tethering." Tap on it. Enable USB Tethering: Inside the Hotspot & tethering menu, you will see a toggle switch labeled "USB tethering." Tap this switch to turn it ON. The switch should change color (e.g., green or blue) to indicate it's active. Check Your Flex server/Gateway is online from the Dashboard. The Gateway Status LED will be Solid Green.   LED patternLED pattern   To Disable USB Tethering (Android). Go back to Settings > Network & internet > Hotspot & tethering on the phone and turn OFF the "USB tethering" switch. Alternatively, unplug the USB cable from the phone or Flex server/Gateway. Part 3: USB Tethering with an iPhone Video link for Demo (The exact wording of menus might vary slightly depending on your iOS version.) Connect Your iPhone to Your Flex server/Gateway: Plug one end of the Lightning (or USB-C on newer iPhones) cable into the iPhone. Plug the other end of the USB cable into an available USB port on your Flex server/Gateway. Note: there are 2 USB ports in the Flex Server/Gateway you can connect to either port to establish USB Tethering. The Flex server/Gateway prioritizes usb0 (the top USB) interface by default for troubleshooting purpose.  USB Port for tetheringUSB Port for tethering   Trust This Device? (If Prompted): The first time you connect the iPhone to a new Flex server/Gateway, the iPhone will ask, "Trust This Device?". Tap "Trust" on the iPhone. You may need to enter the iPhone passcode to confirm. Access iPhone Settings: Open the Settings app on the iPhone. Navigate to Personal Hotspot: Scroll down and tap on "Personal Hotspot." Enable Personal Hotspot: You will see a toggle switch labelled "Allow Others to Join." Tap this switch to turn it ON. It will turn green to indicate it is ON. Important: You might see options for Wi-Fi Password or "USB Only." For USB tethering, you don't necessarily need to worry about the Wi-Fi password unless you also plan to use Wi-Fi hotspot. Check the Flex server/Gateway is online. The Gateway Status LED will be Solid Green. Gateway Status LEDGateway Status LED   Blink pattern for Internet connectionBlink pattern for Internet connection   To Disable USB Tethering (iPhone): Go back to Settings > Personal Hotspot on the iPhone and turn OFF the "Allow Others to Join" switch. Alternatively, you can just unplug the USB cable from the iPhone or Flex server/Gateway Troubleshooting Tips: Restart everything: If it's not working, try restarting the phone and then the computer. Try a different USB port: Sometimes, a particular USB port on your Flex server/Gateway might be faulty. Try a different one. Try a different USB cable: Not all USB cables are created equal. Some are only for charging and don't support data transfer. Try a different cable if you have one. Disable VPN on the phone: If you're using a VPN on the phone, try disabling it before tethering, as it can sometimes interfere. Check data plan: Ensure you haven't run out of mobile data. Contact the mobile carrier: Some mobile carriers have restrictions on tethering or require a specific plan. If you've tried everything else, check with your carrier. By following these steps, you should be able to successfully set up USB tethering and get the Flex server/Gateway online using a smartphone's internet connection!

Issue Fail to apply CP or HF on AS Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Automation Server (ASP/ASB) Cause The Automation Server is not installed next to the Power Supply. The requirement is stated in the Hardware Reference Guide, Position 1 is reserved for a power supply. Position 2 is reserved for an automation server. Resolution When the update process fails, please collect the DebugInformation. Next, check the System.log for the node ID. If the node ID is not  2 , it indicates that the AS is not installed at the correct address. In that case, the physical location of the AS needs to be corrected. Example of incorrect ID location Relevant Resource: Multiple Automation Servers on the same backplane

Issue Programming for the use of Smartware Technologies DUIC-5P-12v input multiplexer Product Line TAC IA Series, EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation RP-V VAV Building Operation Room Controller I/A Series N4 Jace 8000/9000 I/A Series N4 Enterprise Server Building Operation Automation Server Premium Cause Define the application programming and configuration of the DUIC-5P-12V in various enviroments using SpaceLogic contollers Resolution The DUIC-5P-12V Card allows for conversion of a single universal input channel to accept up to five voltage free contacts of any mixture such as mercury wetted, Triac, etc., which may have inherently large and varying resistances. The DUIC-5P-12V on-board circuitry allows the controller inputs to have a consistent input reading, unaffected by long lead lengths, varying resistances, etc.  Smartware Technologies Documents includes programming for use in SpaceLogic devices under an AS-P in the form of a Function Block program. When SpaceLogic controllers are used in the Niagara Frameworks Jace 8000/9000 or hosted directly under a Niagara Frameworks Enterprise Server, the programming is done in a Visual Script Programming format utilizing the Schneider MPX modules in Workbench. The documentation addresses the original use for the I/A Series MNL and MNB contollers as well. NOTE:  The device requires half wave 5 -12 DC or 24 VAC only to prevent damage

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 Understanding common Modbus error codes that appear in Building Operation trace logs. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Modbus Cause Modbus protocol errors are seen when looking at Building operation trace logs. Resolution Below are common Modbus error codes observed in trace logs, their meanings, and example log entries. Error Code 4 – Server Device Failure Message: RESP_DATA_MISMATCH Meaning: This error indicates that the Modbus slave device encountered an unrecoverable internal error while attempting to execute the requested command. This is a problem within the slave device itself, not a communication error on the client side. Possible Causes: Attempting to write to a protected memory area Device in an unsuitable state for the command Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.767 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 4 Error Code 10 – Illegal Data Value Message: Flush buffer. Protocol error code = 10 Meaning: This error suggests the slave device rejected a data value sent by the master. Possible Causes: Value out of acceptable range Attempt to write to a read-only address Example Log Entry: Dec 27 08:15:01 AS-P-18E4A6 nsp_servers[1151]: 2024-12-27 08:15:01.774 [1654641088] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 10 Error Code 7 – CRC Header Issue Message: Flush buffer. Protocol error code = 7 Meaning: This error indicates a CRC (Cyclic Redundancy Check) mismatch in the response message. Possible Causes: Incorrect CRC calculation by the device Incomplete or corrupted packet Example Log Entry: 2025-07-22 10:14:39.636 [1666360064] nsp.pin.modbus.SerTransport Flush buffer. Protocol error code = 7

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 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 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 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.