Building Automation Knowledge Base

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

Issue b3 controllers sometimes get stuck in bootloader mode (refer to Why do Continuum controllers go into bootloader mode). In b3 devices, this is indicated by the CPU LED blinking at at about half the rate of normal CPU LED blink rate. Product Line EcoStruxure Building Operation,Andover Continuum Environment All b3 devices Cause Need a way to recover b3 stuck in boot loader in the field. Resolution Disconnect the b3 device from field bus and connect RoamIO directly to device. In the BACnet Service Tool, de-select the view by Networks option then click the green 'Connect' icon Observe the RS-485 LEDs, both on the b3 device and the RoamIO, if the connection is established the green connect icon on the service tool will have changed to red but no device will be shown since the application is missing in the device, the TD and RD LEDs will be blinking rapidly indicating the RoamIO is communicating with the boot loader in the device, if this is NOT the case then stop, recovery will not be possible, otherwise proceed to next step. In the 'Tools' menu, select 'Update all B3s', then send the appropriate firmware file for the device. After the update operation is complete, re-start the b3 device  

Issue b3/i2 885, 885-V,, 887 and 887L needs Internal Resistance values for voltage inputs but some devices like SpaceLogic SLA do not publish these values Product Line Andover Continuum, EcoStruxure Building Operation Environment b3885, b3885-V, b3887 and b3887L i2885, b2885-V, i2887 and i2887L Cause These controllers have a pull up resistor that cannot be disabled, unlike most of the i2/b3 range The below is taken from the b3 technical manual. Resolution Not all devices publish the Internal resistance,  for example the SpaceLogic SLA, this device has a varying Internal Resistance, but using a value of 25 Ohms, will ensure the maximum error is less than  0.3% of full scale (5ppm for CO2, 0.15 degC) Generally for most devices, where the internal resistance of a device is not available, it can be calculated by noting the voltage on the output device unconnected, then connected to the i2/b3 device and also noting the actual reading (Temperature, CO2 level, Humidity)

Issue Need to use Mobile Apps to access EBO. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation Commission mobile application Building Operation Engage mobile application Cause What are the mobile apps available to use with EcoStruxure Building Operation sites? Resolution WebStation: WebStation is a web-based user interface for day-to-day operation in an EcoStruxure BMS. WebStation, V2.0 or higer, improves user experience by automatically adapting the user interface to the resolution of the device being used: desktop, laptop, tablet or smartphone, using Windows, Linux, Android or iOS, out-of-the-box using standard web browsers, without the need to install additional applications.  WebStation replaces the obselete Technician Tool app. Refer to: WebStation Overview Building Commision: EcoStruxure Building Commission mobile application (requires EBO V2 or higher, formerly eCommission) is designed to help airflow balancers, electricians, and technicians carefully and quickly pre-commission and commission SpaceLogic BACnet/IP devices and RP controller expansion modules. The Commission mobile application does not require a license for activation and is available at no cost to the user. It is designed for use with Android, iOS (Apple), and Microsoft Windows 10 and Windows 11 devices, and is available for download from Google Play, Apple App Store, and Microsoft Store. Refer to: Commission Mobile Application Engage: The Engage mobile application (requires EBO V3.1.2 or higer) enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. The Engage mobile application connects easily via BLE (Bluetooth Low Energy) to the RP-C controller. The application is compatible with RP-C (HVAC) and RP controller expansion modules (lights and blinds). The Engage mobile application is free and available for download from Google Play and Apple App Store.  

Issue How to create a workspace with a banner and a TGML graphic as the home page.  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A graphical overview of a building or area containing a number of buildings can be a logical way for a customer to navigate around a site in Workstation. Resolution Preparation Create a folder to contain the graphics and banners to be used. Create a Panel object Right-click the folder and select New->Panel. Set the initial path (ie. the home page) to the desired graphic.   Add a graphic pane to the panel. Edit the graphic pane and select the banner graphic to be used. Set the desired layout settings such as Default dock position to Top.   Create a workspace Click on the control panel icon. Select User Accounts - Account Management and then under the Workspaces section click on Add. Select the desired security and authority settings. Add a Panel Pane to Workspace. Edit the Panel Pane and set the initial path to the Panel object created in step 2.   Assign the workspace to a user group Under the Select User accounts - Account Management menu in the control panel select the User Group that is to use this workspace. Edit the User Group and go to the Workspaces tab. Highlight the appropriate workspace and add it to the Select Workspaces pane by clicking on the arrow.   Test the workspace Log in with the appropriate user and confirm the layout is as desired.

Issue Using a Lon Binding in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause Binding LON objects to LON objects using the SmartStruxure Variable Connector can cause increase traffic on the LON FT-10 network. Resolution To correctly Bind the LON objects: Edit this bindings of the node object, (not the SNVT object) Use the binding Browser to navigate to the appropriate node/SNVT to bind to Drag and drop the object to create the bind When you are finished you will see a Hexagon button, which will allow you to edit the Lon Binding Properties. This is the indicator that you are using a LON binding and not a Variable Connector object, which would be represented by a gear and pencil icon. Click the Hexagon to edit the Lon Binding properties Do not use the default of Acknowledged Profile.  Unless the device has a specific reason not to, the best option is to use Unacknowledged Profile.  Please see below for the explanations of the LON Message ServiceTypes. Message Service Type You can specify one of the following message service types for each connection description. The message service types vary in reliability and resources consumed. • Acknowledged - means that the sending device expects to receive confirmation from the receiving device or devices that a network variable update was delivered. The sending application is notified when an update fails, but it is up to the developer of the sending device to handle the notification in the device application. While acknowledged service is very reliable, it can create excessive message traffic, especially for large fan-out or polled fan-in connections. When acknowledged messaging is used, every receiving device has to return an acknowledgment.  Acknowledged messaging can be used with up to 63 receiving devices, but an acknowledged message to 63 devices generates at least 63 acknowledgements—more if any retries are required due to lost acknowledgements. • Repeated - means that the sending device sends out a series of network variable updates, but does not expect any confirmation from the receiving device. Repeated service with three repeats has a 99.999% success rate in delivering messages. Repeated service provides the same probability of message delivery as acknowledged messaging with the same number of retries, with significantly lower network overhead for large multicast fan-out connections. For example, a repeated message with three retries to 64 devices generates four packets on the network, whereas an acknowledged message requires at least 64 packets • Unacknowledged - means that the sending device sends out the network variable update only once and does not expect any confirmation from the receiving device. This message service type consumes the least amount of resources, but is the least reliable.

Issue License requirements for standalone Automation Server at a site Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Question on License requirements for standalone Automation Server at a site Resolution EBO 2022 or higher: Standalone Automation Server need software bundle license in addition to add-on option license if required, check Part Number Summary and Hardware Software Matrix. Webstation license is included in the embedded server license. EBO 3.2 or lower: A standalone Automation Server where no web services, Technician Tool (discontinued), SNMP, MQTT, Personal Dashboards and TimeScale DB  are used does not require a license. Use of one of these features requires license which means the use of a single Automation Server or multiple Automation Servers without license is a legal breach.

Issue Unable to log in to the report server via a web browser after successfully installing the WebReports package. No explanation is given as to why the login was unsuccessful.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Report Server Cause The most probable cause is that there is no connection with the ES. Without a connection to the ES, the Web Reports Server cannot confirm the account being used to log in is valid. Resolution Note: Report Server (WebReports) is not supported in EBO 2022 or higher.   Test the connection with the ES On the same PC as the ES is installed on, try logging on via Building Operation Workstation. If this is successful, try logging on to the Enterprise server from the same server as the Web reports server is installed on. To check the URL and port settings, open the Software Administrator on the ES server PC. If step 2 (above) is unsuccessful, go to step 3. Otherwise, go to step 4. Check the firewall setting on the 2 PC,s. Ensure that the ports used by the ES (Check the Software Administrator for information about ports) and the Web Reports Server are not blocked. Re-run the WebReports Installer (link to documentation). Pay particular attention to the Reporting agent section. Make sure that the Enterprise Server URL and port number are the same as that shown in the ES' Software Administrator. Once installation is complete, logging in to the WebReports web server should be possible. If there is still no contact with the ES the network should be checked. A network protocol analyzer (such as Wireshark) can be used to identify the cause of the problem.

Issue Unable to activate the AD-Link on a SmartX Advanced Display Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V1 Building Operation Advanced Display V2 Cause Changes to the license server made current AD-Link software inoperable Refer TPA-SBO-17-0009.00 for details about the issue Resolution Note: Advanced Display V1 is discontinued. Effective July 31, 2023, Service Support for Advanced Display v2 will also be discontinued. The licensing server responsible for activating AD-Link and Kiosk features will be decommissioned. After this date, no new Advanced Display v2 could be commissioned as the mentioned server will be decommissioned. Advanced Display V3 can replace it. Refer to: PA-00923   The issue is solved in a new version of AD-Link To install a new version of AD-Link, there is a need to first uninstall the old version of AD-Link Go to the settings page on the SmartX Advanced Display Tap on "General" Tap on "Security" tab Tap on "Device administrators" Un-tick the AD-Link Uninstall the old AD-Link app   You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app

Issue It is unclear if the included client licenses work the same as WorkStation Standard or WebStation licenses when adding an Editors license (SXWSWEDIT00001). Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Cause It is unclear if the Editor license can work with the included licenses that come with Enterprise Server or Enterprise Central. Resolution The Editors license can be added to the included licenses and allow programming and graphic editing feature.  

Issue Belden Cables for LonWorks Networks Approved LonWorks cables Product Line EcoStruxure Building Operation,Satchwell, MicroNet,TAC IA Series,TAC Vista Environment LonWorks networks TP/FT-10, TP /XF-78 and TP/FT-1250 Cause The Echelon document 'Junction Box and Wiring Guideline for Twisted Pair LonWorks Networks' indicates Belden 8471 and Belden 85102 as the recommended cables from Belden for LonWorks networks. These may not be available from the local Belden office or the Belden distributor. Resolution Refer to Belden Technical Bulletin TB 102E 'Belden Cables for LonWorks Networks' for a list of Belden cables suitable for LonWorks communications. Take note of the difference in cable drop length and total cable bus length for the various cable models listed.

Issue Where to find the domain ID of a LonWorks Network underneath a LonWorks Interface in a Building Operation network. The domain can also be changed in this same location. Product Line EcoStruxure Building Operation Environment Building Operation workstation Cause If the domain ID of a LonWorks network needs to be changed or known for some reason it can be done through the properties of the LonWorks Network. Resolution Right click on the LonWorks Network underneath the LonWorks Local Interface. Click Properties. Click on the Advanced tab and look at the Domain table for Network Interface. The value in the first row of the ID column is the domain ID in decimal form. In order to change the domain ID, use the Addressing entry field "Domain ID Length" to enter the new Domain. Click OK.

Issue After importing a new template into AET, the different folders and objects are all different colors. What does each color represent? Product Line EcoStruxure Building Operation Environment AET Folder View Cause Each color indicates a different status for the object. Some must be resolved before proceeding and others are information only. Resolution Below is the list of the different status colors and their meanings:  Red – Duplicated object. This must be corrected. Green – Existing folder. Orange – Folder with duplicated object below. Black – New object or folder. Blue – Existing object in EcoStruxure system tree Brown – Device that will be created automatically by AET Light Blue – Empty IO Channel

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue When adding Server Packages to a new PCT install, the installation process does not complete.    Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Some security policy is interfering with the PCT installation process. The VirtualBoxDisclamer.log shows the following error     Could not add PCTService to BUILTIN\Administrators.   The lack of the PCTService could be responsible for a range of issues including the failure to install Server Packages. Resolution To learn what is preventing the creation of the PCTService, try manually adding the user to the Administrators group to see what errors might be presented.  Open Windows event log and look for errors that occurred during the same timeframe noted above. 

Issue PCT fails to open, presenting four 'could not connect' error messages.   Product Line EcoStruxure Building Operation Environment Project Configuration Tool Windows 10 version 1909 Windows 10 version 2004 Cause The cause maybe a firewall, scripts or group policy not allowing PCT to install correctly. Resolution First: check the VirtualBox Host-Only Network has the correct IP address. This can be found under: Control Panel\Network and Internet\Network Connections\VirtualBox Host-Only Network #?\Properties\Internet Protocol Version 4 (TCP/IPv4).   Raise a case with your region's IT2929 (UK = 020 7660 2747), requesting IT install the patch to correct the issue. IT2929 have a knowledge base article on the IT2929 system to help their representatives with this issue (KB0014074).   IT2929 will advise you to take a backup of your PCT projects, uninstall PCT and Oracle VM VirtualBox. IT2929 will then install the patch. Re-boot the laptop. Install PCT and Oracle VM VirtualBox (run as administrator). Restore your PCT projects. Re-boot the computer. If PCT still does not work after this, update the CCC case you have or create a new case with Product Support, providing your IT2929 KSR number is you do not have a case.

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.