Building Automation Knowledge Base

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.

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 During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue Where can I find information on EWS? 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 SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Want to change the sound that is played in Workstation when an audible alarm is triggered Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Need to attach individual alarm sounds to different alarms. Resolution EBO V2.0 or higher: You can add a custom audible alarm alert to EBO, which is an audio file that is played when an alarm is triggered. Refer to: Custom Audible Alarm Alert Workflow   SBO V1.9 or lower: The alarm sound is hard coded to the file C:\Windows\Media\notify.wav, and can't be changed from Workstation. The solution is to replace the notfify.wav file with another wave file. Please be aware that if the file is deleted, Workstation will crash when an alarm triggers. To change the file, you need to take over the ownership of the file as described here. The procedure is also described below. Browse to the folder C:\Windows\Media Right click the file "notify.wav" and click "Properties" Click "Advanced" Click "Edit" Select "Administrators" and click "Save" You get the following dialog. Click "OK", and close the properties. Open the properties again, and set the "Administrators" group to have full control Now rename the "notify.wav" file, and paste the wave file you want into the Media folder and rename it to "notify.wav"

Issue Is it possible to monitor the status of a Modbus interface/device from within a TGML graphic? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Building Operation Server Serial Modbus device Cause It's a very common requirement to monitor Modbus devices and interfaces and show this value on a TGML graphic page. Resolution The attached TGML graphic gives a simple example of how to do this. The screenshot below shows the property to bind the TGML binding to. To see the property "NetworkStatus" for the Modbus network in the binding view double click on Modbus Master Network. To see the property "Status" for the Modbus device double click on the Modbus device in the binding view.   

Issue Is it possible to have different stop bit settings in different Serial Modbus devices on the same bus? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus serial communication Cause In Building Operation there is an "Auto" setting for the Serial Modbus communications "Stop Bit" setting. This could be interpreted as "automatically" detecting the Serial Modbus devices stop bit setting. Resolution The "Auto" setting is only designed to detect how many stop bits are required in certain circumstances, such as when the parity setting is set to none and therefore 2 stop bits must be used. The settings used are the Serial Client settings for the entire bus and all the Modbus devices have to be set to match the Serial Client.

Issue The Modbus Server / Client is unable to read the values from address of a 32 bit Modbus register in a Building Operation server Product Line EcoStruxure Building Operation Environment Building Operation server Modbus Cause The original Modbus/JBUS protocol specifies the use of 16-bit integer registers for Analogue Inputs and Analogue Outputs. The number range able to be represented in 16-bits is: Unsigned: 0 to 65353 Signed:     -32768 to 32867    In order to represent larger numbers, it is common for 16-bit registers to be combined to represent 32-bit or 64-bit numbers. When a Modbus Client or Server reads a 32-bit Modbus value, it will be reading two consecutive 16-bit registers. An error will occur if  two 32-bit Local Modbus registers are created in Building Operation using consecutive register addresses since only the starting modbus register address is used for the request.  Resolution When configuring 32-bit Local Modbus registers in Building Operation, the next register address should not be used. Create the next Local Modbus register using the 3rd available Modbus register address.