Building Automation Knowledge Base

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

Issue When importing an XIF into SmartStruxure, errors can be generated that vary in nature. Product Line EcoStruxure Building Operation Environment SmartStruxure Enterprise Server SmartStruxure Automation Server Building Operation Workstation Cause The XIF does not import successfully for a variety of possible reasons: There exists a device template in the server already that contains the same device ID as the XIF that is being imported.  The XIF does not comply with the LonMark Device Interface File Reference Guide published by LonMark. Resolution Before performing any of the steps below: Import the XIF file provided by the manufacturer of the Lon controller - if the manufacturer did not provide a XIF, try searching the LonMark product catalog If the provided XIF does not work, upload the XIF from the device to ensure that it is the correct file by following How to extract an XIF out of a Lon controller. Use the SBO SNVT Support tool found on The Exchange to identify unsupported SNVT's. Work through the troubleshooting steps below.   Device Template Fails without an Error This issue has been seen in some of the older versions of SmartStruxure (1.5 and older) and upgrading to the latest version will resolve the issue in many cases. If the issue occurs at the latest version of SmartStruxure: Use the SBO SNVT Support tool located on The Exchange to identify unsupported SNVTs. If the SBO SNVT Support tool does not identify any unsupported SNVTs, then send the XIF in to Product Support for further investigation.    Device Template Already Exists In order to complete the import of the XIF, follow these steps. Delete all controllers in that database that are using the device template that has the same device ID as the XIF file you are trying to import.  Now import the XIF again. Select the server in the system tree on the left and go to File > LonWorks import > Device Template. Click the Browse button and select the XIF you want to import. Click Import. Note: When the import is complete it will have overridden the old device template with that device ID. Two device templates with the same device ID will not be able to reside in the same database. For more information about device templates see Delete Device Templates.   Detailed Error Prompt with Specific Fields Listed Some examples of the detailed errors include but are not limited too: "Field X has error(s). The string must between X and X characters. nvoActualCapacity has X characters" on row X. "Field X has error(s). The number must between X and X. Field X has value X." on row X. "Field X has error(s). The value must be X but was X." on row X. Space or tab are not allowed in field 0Node Object on row X.   To Address these issues: Download Notepad++ to be able to better navigate the XIF by row number. Using Notepad++, open the XIF. NOTE: Backup the original XIF just in case there is a mistake when modifying. Find the row and field number prompted by the error messages and modify them accordingly. All the rules can be found in LonMark Device Interface File Reference Guide published by LonMark. Import the XIF again to verify whether it works. If not, contact Product Support for further investigation.

Issue When discovering the SLP Series Living Space Sensors they show up in the BACnet discovery summary as Non-conformant. Attempting to add this non-conformant sensor results in a WorkStation error similar to the following:  Validation Error Workstation Error in "~/BACnet Interface/MSTP Network/Living Space Room Unit 4E5932F5_«1»_07/ForeignAddress". Property value "<device, 10000>" already assigned to "~/BACnet Interface/MSTP Network/SLPSTC2/ForeignAddress". COML Validator0 Product Line EcoStruxure Building Operation Environment BACnet MSTP Living Space SLP Series Air Quality Sensors Living_Space_REV2.05.21 Cause Building Operation does not allow duplicate BACnet IDs and hence, during discovery, if a device is found with a BACnet ID (Object Identifier) the same as an existing device it shows as a non-conforming BACNet device. The default device ID for SLP devices should be equal to (Vendor ID * 1000) + MAC Address. Where vendor ID is our Schneider Electric BACnet vendor ID = 10 and the MAC address is unique to each devices MAC address DIP switch setting. This will be corrected in a future release of the Living Space firmware.  Until corrected, and since the Device ID is a read/write attribute the customer is able to change it to avoid duplicates on the bus. Unfortunately, Building Operation does not currently have a method to write a new device ID. Resolution The current workaround is to use a third-party BACnet Explorer such as Yet Another BACnet Explorer (YABE) to write a new device ID value. Once the new ID has been updated the SLP device can then be rediscovered within Building Operations'. 

Issue When using the 20k (Honeywell) thermistor type on an EcoStruxure IO Module, the temperature value does not change and reads an inaccurate value. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server IO Module Cause The 20k (Honeywell) thermistor type does not work properly in Automation Server IO module firmware versions 2.009 and older. Resolution Check and upgrade the Automation Server IO module firmware to the latest version. Follow the steps below: Select the module in the System Tree (1) and on the Properties tab (2) check the Firmware version (3) If the firmware requires upgrading the latest version can be downloaded from The Exchange Download Centre.  For instructions on how to upgrade the firmware see Upgrading Automation Server IO Module Firmware.

Issue How to upgrade Automation Server IO module firmware. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation I/O Module  Cause Occasionally new firmware builds will be released for the Automation Server IO Modules to address issues or add enhancements to the products. These firmware builds must be downloaded to the modules through Workstation. Resolution Upgrading IO Module Firmware The latest version can be downloaded from The Exchange Download Centre.  Once the firmware is downloaded right click on the IO module in the System Tree and select "Update IO module firmware..." The "Update IO Module File" browse window will automatically open.  Browse to the new firmware file and click "Open". The latest IO firmware files can be downloaded from The Exchange Download Centre.  Once the IO module update is complete, click "Exit". To check the firmware version in the IO module, select the module in the System Tree (1). Click on the Properties tab (2) and check the Firmware version (3). For additional information refer to Updating Central IO Module Firmware

Issue IO module status shows 'Bootloader' Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server IO Module Cause The most likely cause is a failed upgrade process.  During an upgrade, the IO module's firmware is deleted allowing it to be replaced with the new firmware.  If the process fails before completion the module will be left without the application and in bootloader mode. Resolution Upgrade the firmware by following the instructions at Upgrading Automation Server IO Module Firmware. The operation takes less than a minute and the Module status should show status 'Configured' or 'Unconfigured' depending on whether points have been created on the module.

  Issue Cannot communicate to an ADV3 connected to the USB port of an AS-P or AS-B. The error message “Website not available” is displayed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display v3 (AD v3) Cause The AS-P or AS-B’s USB port uses a IP network connection to the ADV3 that defaults to 192.168.42.116. If the AS-P’s primary port is in the same range, for example the main LAN network range is 192.168.42.* there is a conflict with the USB IP network. Resolution Change the sites main LAN, which the AS-P or AS-B primary port connects too, to another network range.

Issue On a system requiring Semantics after adding Enterprise Servers to an Enterprise Central alarms are generated that cannot be cleared.  Changing the password for the Servers does not fix the issue. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Cause Incorrect method used when setting up Semantics during installation, Semantics were enabled on the Enterprise Server as well as the Enterprise Central.  After adding to the Enterprise Central the Enterprise Server points to a different address where the alarm is for the original Enterprise Server address.   Resolution On the Enterprise Server the alarm needs to be verified against the original connection, this involves removing the lead object link and changing the settings to look at the original Semantic Database.   On the Enterprise Server Semantic Settings remove the lead object entry pointing to the Enterprise Central.  Open the Services Manager and Stop and Re-Start the GraphDB service, if stopped start it. Additionally, Stop and Start the Enterprise Server service, this can also be done in the Services manager using Software Administrator to stop and start will show any errors if evident. Log back into the Enterprise Server and the password alarm should be cleared, this may take a minute or so but not any longer.  This is only if the password has been changed, please see Semantic DB authentication failure" alarm. Also, in the EC the password alarm should have cleared. Once the alarm is cleared the GraphDB service can be disabled from within services as it is not required. Re-instate the lead object entry pointing to the Enterprise Central that was initially removed. For more information on Semantics please see Semantic Overview

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. Issue How does one get a clean database for the Enterprise Server or Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need for clean database either for testing or start from scratch.  Resolution Stop Enterprise Server or Enterprise Central using Software Administrator Go to the location of your database using Windows Explorer. In EBO V3.2 or higher, software administrator has a shortcut button for the databse folder. For this example it is C:/ProgramData/Schneider Electric EcoStruxure/Building Operation 2.0/Enterprise Server/db Delete the following folders if (some might not exist): Configuration, Historical, Persistent, System, UDT Start Enteprise Server or Enterprise Central using Software Administrator, the system will create a new folders and files as needed. Note: Restoring a different database over the current database does not require the clean database state. Using the backup and restore procedure allows you to switch databases.

Issue Users may want to know how to perform the online activation of an embedded license  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause From Building Operation 2022, the Automation Server (Classic/Secure boot AS-B or AS-P) and features like Smart Drivers, SNMP notifications, Personalized dashboards, TimescaleDB, MQTT Publish/Subscribe, Modbus, Serial MS/TP, ES Connection, Server I/O, Field Devices, SAML Authentication, Zoning, and BACnet IP require a license. Customers need to know how to activate their embedded licenses to enable these features. Resolution This video will demonstrate how to Find the list of supported features by each activation ID. Activate an embedded license on an Automation Server Verify the embedded license status via the Device Administrator, Workstation, and the Flexnet operation license portal. Notes Check each activation ID's supported features using the part number or license description through the Features and Licensed Products Table.  The Flexnet operation license portal is a public FlexNet Login (flexnetoperations.com) accessible from anywhere with an Internet connection.  The Automation Server and the PC running the Device Administrator must have outbound connectivity to the license activation server over the Internet. Check the resolution section of this article Could not establish contact with License Server using SmartX Server - Communities to verify if the Automation Server has access to the Flexnet license activation server. For troubleshooting, refer to Embedded license activation fails. Web helps:  Assigning Licenses and Activating Licenses Online. An Embedded DEMO license is available for temporary use during project engineering and installation until you know each device's specific licensing needs. Please visit How to activate a demo license on an Automation Server at EBO 2022. If the Automation Server does not have access to the Flexnet license activation server (no Internet connection), you can perform the steps in the following article Offline activation of embedded licenses.  Please take note that starting from Building Operation 2023 version 5.0.3 and higher, Automation Servers are no longer required to be connected to the Internet. The Device Administrator can access the internet and manage communication and license activation for the 'offline' Automation Servers.   A shorter version of the Online Activation of Embedded Licenses for Automation Servers-Digital Job Book (nampss.com). is available on the NAM PSS site. (Note: Registration for access to this site may be required.)  

Issue ODBC used with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause ODBC (Open Database Connectivity), a standard C programming language middleware API. is used to access database management systems (DBMS). Resolution ODBC is not supported with the current or previous releases of EcoStruxure Building Operation.

Issue How can I insert the points name or path into the alarm text? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Building Operation WorkStation Cause Require dynamic text insertion in the alarm text. Resolution The following substitution codes exist for alarm messages: All SBO/EBO versions:  @(F) – The path of the monitored variable.  @(O) – The monitored object name.  @(P) – The monitored variable. In addition to the above, Version 1.2 also includes: @(V) - Displays the value of the monitored variable at the time of the state change. e.g. If you create an alarm that is monitoring a temperature object named Room1Temp and write an alarm message that says: “The point @(O) is too hot.” When the alarm is triggered it will display: “The point Room1Temp is too hot.” Refer to: Alarm Messages  

Issue Summary view for Forced Value on I/O 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 Automation Server or any of connected devices can potentially have many points or values. Need to discover which ones are in Forced state. Examples: A Digital Output with default value: Digital Output with Forced value and ON: Digital Output with Forced value and OFF: Resolution You can search for forced values using the search function in WorkStation. Enabling In device option will enable finding forced values on devices hosted under EBO, as SpaceLogic and EasyLogic devices, MP and RP controllers, IP-IO modules and RP-IO modules. For more information, see Searching for Forced Values . You can also view the search in WebStation:   In EBO 2023 or later, You can search for forced values in WebStation using Diagnostics. For more information, see Displaying a List of Forced Values in WebStation .  

Issue When an attempt is made to activate a License, the following error is displayed, and the license is not activated.   Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In this case the Entitlement was inactivated due to a double registration made by mistake by the Orders Dept.  Resolution Used the second active Entitlement ID to activate the license.   For more information, refer to WebHelp articles 6367 and 7440.

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.     Open Windows Command Prompt Enter :telnet <address_of_remote_server> <port_number>" - telnet 192.168.1.2 443 Result if Port open: blank window with blinking cursor Result if Port closed: error message displayed similar to "Connecting To 192.168.1.2…Could not open connection to the host, on port xx: Connect failed" The example above test for connectivity against the remote server that has the IP address of 192.168.1.2 over port 443

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 Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue 3rd party BACnet Gateway can be seen  and points found when performing "send to database" but the Life Safety points do not show up. Product Line Continuum BACnet Environment Andover Continuum, EcoStruxure Building Operation Cause We do not currently support the BACnet Life Safety objects with the Andover Continuum or EcoStruxure Building Operation product lines Resolution Use an object that we do support, either an AV (Analog Variable) or MV (Multistate Variable) would probably suffice as long as the 3rd party Gateway can provide this instead of the Life Safety objects. See our BACnet PICS statements at the link below that show what BACnet objects each of our products support. https://www.bacnetinternational.net/btl/index.php?m=20

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. Issue Require a method on how to apply individual setpoints in EBO when Users are granted access at a Security Expert  Door. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause An example of this would be to have room temperature setpoints, or other specific settings, be changed when specific Users are granted access to a room or area. One method on how to do this would be to create a separate Access Level and Access Level Output for each user. When the User with that Access Level is granted access the associated output will be enabled. Using the EWS integration, the states of these virtual outputs can then be monitored within EBO and action were taken when they change state. Resolution Perform the following steps to configure this: Create an Access Level for each User object. Create a virtual output for each User object. A virtual output is an output object that is not assigned to an output expanders physical outputs. You could create outputs on existing expanders above the maximum output channel that you will be using but it is recommended putting these virtual outputs on a completely different module address outside the range that will be used for any physical modules. Module address = 32 would be a recommended starting value. Steps would be: Under Programming | Outputs create three new outputs. Set Module Type to "Output (PX)" Set module address to "32" or greater. Set Module Output to "1", "2", "3", etc... Save the changes. For each of the Access Levels add the corresponding virtual output to the Access Levels Output tab. Access Level Outputs Ensure the Access Level has access to the Door(s) in question. Set the Time to Activate (seconds) in the Access Level | General tab to something appropriate such as 5s. The output will disable after this time period. Set the Reader Access Activates Output on the Access Level. Set Activate Access Level Output on the Reader Expander | Misc Options.    

Issue How to subscribe to a topic in Azure IoT hub via MQTT protocol. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can subscribe to MQTT messages from Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure MQTT data values Create and configure a data group Configure the subscription parameters Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code