Building Automation Knowledge Base

  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 Identifying a potential power supply/source failure to the Flex Server for a specific time period.  Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server went offline for some time and then came back online again. There is a need to identify if this happened due to a power source failure to Gateway.  Resolution Login to the Partner Portal and select the customer from the settings icon in the top right corner. Navigate to the Controller section in the left pane and select the particular Gateway from the dropdown. Navigate to 'Plots' tab and select 'PowerSource' Gateway stream under 'MSP430'. The 'PowerSource' stream value should always be equal to '1' as shown above. If this indicates '0' at any time, this suggests a potential loss of power supply to the Gateway.

Issue EcoStruxure Building Activate Flex Server fails the Wi-Fi Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause If the Flex Server Gateway is configured on Wi-Fi, it must achieve a RSSI value greater than -75 or value does not go below -80 more than 3 times. If these conditions are not met, Gateway will fail the test.   Resolution Below steps should be checked/followed to check the issue: Check Network Type: Ignore this issue if gateway is using a GSM network Verify Wi-Fi Receiver: Ensure the Wi-fi receiver is properly inserted into the USB port of the gateway Optimize Placement: Make sure the Gateway is near or in line of sight with the router to improve signal strength. Restart Router: Restart the router and check with your network provider for any issues.

  Issue While performing the verification tests, an error is displayed: 'error: There is no change in the configurations' as shown below:   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Partner Portal Cause This error occurs under the following conditions: The user made changes in the Partner Portal but later reverted to the original settings/configuration, assuming there should be some changes, and then started the verification tests again. The user chose to perform the test and verification process once post-submission, resulting in this error message. Resolution When the verification process is initiated, it goes through four checkpoints. The user can safely ignore this error message and proceed with the tests directly. Clicking on the 'Load Mapping' button will remove this error message.

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. Issue Access Expert uses Docker containers and images for the Bosch and Schindler integrations and at times the virtual machine image(s) need to be updated. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Feenics updates virtual machine images which requires an update Resolution Feenics may update a Docker image for one of their integrations.  Note: A Docker software update may be indicated in the bottom right of the Docker Window This is only a software update for Docker and will not update the container image. An image update requires a command to Pull the image down from Feenics. The Docker software update is not required to update the Docker Image.  (see yellow highlight in the snapshot below)   Here are the instructions to update the Docker Container Image to the (latest) Open Docker Desktop for Windows 1. Under Containers, make note of the current bosch service name Ex. AX-bosch-service1 2. Stop the container/service using the stop button 3. Click the Red Delete button above the container Click Delete Forever No container after the delete Image still shows 4. Delete the Image by clicking on the Red Delete button under Images Select Delete Forever (Image) Image deleted (See below) 5. Click on the Blue button 'Search images to run' Type in the following to search for Images feenics/keep-bosch:latest   6. Select the 'feenics/keep-bosch:latest' Image and Click PULL You will see the progress of the image downloading 7. Click on Containers on the top left - the container will not be there 8. Click on Images and then Click the Play button on the Feenics/bosch entry 9. On the next screen, after selecting Play, select the down arrow next to Optional settings Enter the original container name that was noted above i.e. AX-bosch-service1, Click Run You will see messages from the bosch service startup Although the image is updated and running, you will likely see an 81 exception error in the startup log (see highlight above). Here are some additional steps to finalize this process.   10. Check in Windows Services> Docker Desktop Service One of the updates along the way may have changed the startup type to Manual Double-click on the service and select Automatic for Startup type Click Start (to start the service) Click Ok.   11. Open Windows PowerShell in ADMIN mode (standard mode will not work) Run the following command   docker run -d --restart unless-stopped --name feenics-bosch-service --env-file C:\ENV\env-us.txt feenics/keep-bosch   If you try to run the command with the same name as the original service, you will receive the following message in PowerShell  Successful running of the Power Shell command This command ensures Docker runs with the parameters that are stored in c:\env-us.txt 12. Click on Containers, and there will be 2 Containers Select the one that is NOT running and click the Red Delete button The Delete Forever prompt comes up, select the Delete forever button One container should remain and should be running The panel should be online and communicating 13. Test and verify everything is working with the Bosch integration

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 How to program the function buttons in Esmi Fire Panel Product Line ESMI Fire Detection Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Customer wants the specific buttons for specific actions. Resolution Up to 24 customer specific, on-screen function buttons may be configured to provide control, disablement and engineering functions. The function buttons can be configured to be either available or hidden for each log-in profile. The following procedure describes how to: Set function button attributes/properties. Allocate function buttons to user groups.  Create password specific user accounts for inclusion within a nominated user group. Setting attributes Function buttons (inputs) may be set to operate by association to output devices with the same properties e.g. a security input will activate any device that has security ticked as part its output properties, or as part of a cause-and-effect rule where the function button is the “Cause”.   With Loop Explorer open, select the Configure menu button and select System Manager to open the function button configuration page. Select the 'Details' button to open the properties section of the function button that you wish to configure. Note: Input Properties The properties page allows the user to configure the input action and associated messages, to set individual colours and either to work as a latched (cleared on user interface reset) or toggled action (press function button to operate and again to turn off). Mapping to zones is optional, and the location text is the name given to the function button when completed. Feature Groups There are 4 default user groups that can be configured with specific permissions for different users.     When configured, the function buttons will be included as selectable options in each of the feature groups. It should be noted that if a function button is allocated to the Logged-out group, then it will be present alongside the User Options button when all other user groups have been logged out. Note that at this level then the user options are limited to system information and basic panel tests such as display colour and LED function. Function buttons allocated to User level 2 and 3 may be accessed using the default login codes. If users are to be allocated unique numerical codes, then it would be advisable to change the panel default level 2 and/or 3 codes where required.

Issue Access to the Platform on a PC without administrative privileges is, by default, not allowed. Product Line TAC IA Series Environment I/A Series N4 /AX Workbench Cause Default Platform access is restricted to persons logging on to the PC with administrative privileges Resolution To run a station on a Workbench, you must open the Platform to install and start the station. Consult with your IT department about getting a temporary local admin account or have them assist you with this process.   Start the daemon you wish to run the station in Open Workbench of the running daemon Open the Platform  Follow the steps in the screen capture Now you can open the Platform and run stations without having administrative rights on your PC.           Notes: This must be done for each version of Niagara Workbench If you have a Schneider Electric laptop with CyberArk EPM installed, obtain a CyberArk JIT for administrative privileges from SE Support. If you have a Schneider Electric laptop, when logging in to the "Update Authentication" in the Platform, use your SESA login.

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. 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 names Unresolved 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) 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 F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Issue After an upgrade the SP-C-WEB is showing "NOT REGISTERED" with the option to register the controller. Attempts to register the controller fail as it is already registered. SP-C-WEB not registered When attempting to create new records their is a "License Limit Reached" message displayed and the new records are unable to be created. SP-C-WEB license limit reached Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Browser has cached settings for this controller that are interfering.  Resolution Use browser incognito mode and/or clear the browser cookies and cache.

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. 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. Issue How are Elsys LoRaWAN sensors configured with a smartphone using NFC Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause All Elsys sensors are equipped with NFC for easy configuration with a smartphone. There is a requirement to configure these sensors using a Smartphone or tablet using Elsys 'Sensor Settings' application. Resolution Download the ELSYS “Sensor Settings” application from Google Play or the IOS App store and install it on a smartphone or tablet.     Ensure the mobile device supports NFC. Enable NFC on the device and start the application. Position the mobile device directly on the NFC antenna of the sensor. Ensure both devices remain close and stationary to maintain optimal connectivity. Remove the mobile device. The current settings will be displayed in the application. Set the 'Timebase' to 120 seconds using the application. Remember to revert it to 600 seconds after commissioning!    Make note of the following sensor keys: DevEUI: The unique ID of the sensor, found in the blue panel at the top. AppEUI: Application ID (8 bytes or 16 hex digits). Default is 0, can be changed if needed for the application. AppKey: Application unique key (16 bytes or 32 hex digits) that is the encryption key used for messages during every over-the-air activation. Tap the sensor's NFC antenna to transfer the new settings after making the desired changes. Ensure the application confirms the updated settings. Wait for the sensor to reboot, indicated by the LED flashing. The sensor settings should now be updated. Validate your settings by reading the NFC data after the sensor has restarted. Verify that settings have been applied by using the ‘Read’ functionality in the app and touching the sensor’s NFC antenna.    Remember to change the 'Timebase' back to 600 seconds after the commissioning is completed!

Issue The SP90 Actuator alarm "BV:22 Temperature Sensors Missing or Interchanged" is triggered. Can we simply swap T1 and T2 in the configuration to fix this, instead of physically swapping the sensors? Product Line Field Devices Environment SpaceLogic SP90 Series Smart Actuator Cause The installer has installed the temperature sensors in the incorrect pipes. Resolution Firmware versions V439 (for actuators products marked V1xxx on the product label) and V539 (for actuators marked V2xx on the product label) introduced MSV:42 (T1 input) and MSV:43 (T2 input) which enable the temperature sensors to be swapped.   You are able to select each as: 1: Disabled 2: Supply temperature 3: Return temperature   If the SP90 actuator is at a lower firmware revision, it can be upgraded. Contact Product Support for the firmware files and upgrade instructions.

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. Issue Not able to see the network panels status, trouble messages, events, cause and effects etc. Product Line ESMI Fire Detection. Environment FFSULH1009. 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 How are user profiles (accounts) configured in Esmi Ultima Fire Panels? Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Access levels allow permissions to be assigned to different user types. Resolution User Accounts Maximum Accounts: Up to 63 user accounts can be created. Permissions: Access group or singular permissions as set out within each user group. Profile Configuration User Levels: The example above shows User Level 2 in Group 1. Group numbers increase as more groups are added. Session Timeout: Range from 1 to 255 seconds for the function button availability after login. Function Buttons: Selected according to users who need access to the group. Panel Permissions: Additional permissions can be set in the User Menu Options section. Event Log: Records individual user activity. User Profile Example Username: Up to 20 characters. Passcode: Should contain 5 or 6 numerical characters. User Level: Mike Allerton is the 4th user, placed in User Level 3. User options Panel Control Interface: User activates the interface and enters their passcode to unlock screen and panel permissions. Function Option Button: Provides access to the buttons as described earlier.

Issue There is a need to identify the Ports and URLs which must be open through the customer's firewall and network security for EcoStruxure Building Activate Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause To ensure the Flex Server operates correctly, specific URLs must be whitelisted within the customer's firewall and network security settings. Resolution Below is the list of URLs which must be open through a site's firewall/network: Domain Name Protocol Description telemetry.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used for sending IoT Sensor Data streams. mender.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used to download firmware update. emqx.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used for communication of Flex-Server with Schneider Electric cloud services such as configuration, data, or alarms. openvpn.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Allows Schneider Electric to remotely access the Flex- Server through VPN. timesync.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Time server allows the Flex- Server clock to remain synchronized. router.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Allows the Flex-Server to download linux updates   Note: For the list of URLs to be whitelisted for the India Portal, please refer to Required list of URLs/Ports to be whitelisted under firewall/network for EcoStruxure Building Activate (India Only) 

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 PCT 2.0 shows "503 Service Temporarily Unavailable" error when trying to reach to PCT server. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The PCT 2 disk has a fixed size limit of 200GB and cannot be expanded by users. Once the disk reaches full capacity, access to PCT 2 becomes unavailable. Resolution Check the size of the "data.vhdx" file: The file resides in the "Virtual Hard Disks" folder. This folder can be found in the path selected during the installation. Folder location: Navigate to the installation path to locate the "Virtual Hard Disks" folder. File location: Inside the "Virtual Hard Disks" folder, locate the "data.vhdx" file. Check the size of the "data.vhdx" file.   If the disk size is over 200GB, contact local support and attach the information.   

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.