Building Automation Knowledge Base

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue Modbus TCP Device (Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus TCP Network Modbus TCP Gateway Cause Modbus TCP Device (Slave) address 248 is reserved and cannot be used. (Modbus TCP Network or Gateway) SmartStruxure supports up to address 247, as per StruxureWare Building Operation - Technical Reference Guide (up to v1.6.1). There was a defect within v1.5.0 and earlier that caused address 250 to be used if the Device address is set to "Invalid." This defect was corrected in v1.6.1. Resolution From v1.9 this is corrected, so it is possible to define addresses for Modbus TCP devices from 1-247 and 249-254 Device addresses 0 and 248 are reserved. Device address 255 is used as the Default address.   For Modbus RTU RS485 master/slave networks, slave device addressing is different, see KB article Modbus RTU slave address.   Further information about Modbus can be found in the KB article Modbus basics.

Issue Input points on BACnet devices displaying in a Graphic show the forced icon on the Graphic when the input is manually forced, not so for value objects such as Analog Value. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause The reason for this is that when a point such as an input is forced StruxureWare Building Operation automatically puts it out of service and when the input is unforced puts back in service, that is not the case for a value object. The screen shot below illustrates the problem, as seen, both the input point under a b3 (Ct1CwSTmp) as well as the analog value (CtCwSSpt) in the AS are forced but only the input is displaying the hand icon indicating the that object is forced. Resolution A work around is to create a PE Script program to set the out of service property to TRUE when the value is forced and to FALSE when the value is NOT forced. Please note that the program uses the value of priority 8 to determine whether the value object has been forced or not, if the Priority 8 is NOT NULL then the object has been forced, note that this presents a problem for binary objects as well as for the case where the analog object is forced to a value of ZERO as PE Script can't differentiate between NULL and zero. In the case at hand, the program is located in the Application folder under the BACnet interface of the Automation Server.

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 When creating an ETL task the "Run Once" option works, but when configured to run as a service, it doesn't work and an error occurs in the error log: 2015-05-22 17:13:59,069 ERROR ETLEngine (TaskName) - Thread ID (119) - Power Monitoring Expert Load Task: Task Power Monitoring Expert Load Task failed System.ApplicationException: Failed to populate the MetaDataSet. ---> System.Data.SqlClient.SqlException: Cannot open database "ION_Data" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'. Product Line EcoStruxure Building Operation, Other Environment Power Monitoring Expert Energy Expert (formerly Power Manager) ETL Tool Cause When testing the ETL task using "Run Once", the Windows account currently logged in, will be used to access the SQL database. However, when the same Task is then configured to run as a service, the account configured on that Service will be used to access the SQL database instead.  By default that account is the built-in account 'NT AUTHORITY\SYSTEM'.   The Position values for all of the mapped trend logs are set to an unreasonable timestamp. The timestamp is either very old or a date the preceeds the oldest values in the database.  Resolution Changing the Windows system account for the ETL service Either give the system account access to the database, or change the account used to run the service. Correct/Adjust the timestamp values in Positions tab of ETL The timestamps can be changed all at once by setting the Initial value field at the top of the "Positions" window in the ETL tool. 

Issue Failed to establish connection with server. (HTTPS) 1.5 Server version not compatible with client (HTTP) 1.5 Failed to establish connection with server. (HTTPS) 1.6 Failed to access the server, a network error occurred. (HTTP) 1.6 Environment StruxureWare Building Operation 1.5 and newer Cause Attempting to log into WorkStation for Project and you either do not have the Project Configuration Server installed or the Project Configuration Server is not running. Resolution Reboot the machine. Check that the Project Configuration server service is running.  Note: One other possibility is that you have a different instance of Projects Configuration server already running from a concurrent installation. (Example: You are trying to log into Projects 1.8.1 but you already have Projects server 1.7.1 running). This will cause a Failed to establish a connection with the server error.

Issue When connecting to a Web Service, the connection is not established and the error "403 forbidden" is shown. A Web Service goes offline after having worked previously and the error "403 forbidden" is shown. Product Line EcoStruxure Building Operation Environment Web Service Generic Consume Cause The generic consume Web Service client in SmartStruxure doesn't have a user agent header defined. Some Web Service providers will not or no longer allow that, and denies the request when it comes from SmartStruxure. If the same URL is entered in a browser, the page is shown. The cause of this issue can also be that the Web Service is being polled too often. Resolution Until it is made possible to define a customer user-agent header, you need to use another application to relay the Web Service request. This can for instance be "SBO - Web Service through a Proxy and JSON conversion" from the Exchange Community.

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 A system Format of the file system will remove all files to return device to a factory condition. Product Line TAC Vista Environment TAC Xenta 5xx TAC Xenta 7xx TAC Xenta 9xx Xenta Server Cause A need to reset to factory defaults exists Resolution These actions clears the filesystem and remove all files and information in it. Make sure you have IP and any other information you need to save from the file system. All files and configurations will be lost. Access Xenta using a serial interface via the RS232 port and a HyperTerminal program. obtain a connection to the dsh> prompt Type format. Wait for formatting to be ready , then enter command setip to enter DHCP enable ,ip-address , subnet mask , default gateway , DNS , local name. Default user/password will then be root/root. Remember to change password. Restart system to accept new ip-address. Install Xenta using the install kit. Use ftp transfer and alternative A (We have just formatted the system). Download WebTool project and user defined files. Update bindings using LonMaker.

Issue A repository of objects available somewhere for sharing TGML graphics such as Smart Widgets (Power Objects), Camera, Door, Lighting, Reader, override, etc. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Smart Widgets. Cause Graphical interface of power object, such as a Power Meter, Power Objects, Camera, Door, Lighting, Reader, override, etc. for viewing in TGML graphics mode. Resolution These objects should appear on the StruxureWare Building Operation Community Site. However, there is an ongoing centralized effort in producing more objects in a uniform way and the developers have not yet seen the devices they developed objects for. One of these developers has made objects for these devices: PM710, PM9, PM800, ION6200, Compact NSX. There are standardized updates in progress for these and also for the PM210. The community is the best place to get these. PSS does not have a repository of these type of objects.  

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue Where can I find help on TGML scripting and advanced features? Which javascript functions are supported and how do these impact performance. Product Line TAC Vista Environment TAC Vista TGML graphics editor 5.1.7 Cause More advanced graphics often require scripting and the engineer needs to know which functions are supported. Resolution In the TGML editor under Help there is a section called TGML Format Specification. Details of scripting methods as well as examples can be found here. Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue In EBO 2022 or higher the "Semantic Engineering View" button is grayed-out in EBO WorkStation and "Semantic DB authentication failure" is shown in Alarm View. "Semantic Engineering View" button is grayed-out and "Semantic DB authentication failure" alarm   Semantic db authentication error   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause  EBO user that connects to the Sparql database has the wrong username and/or password. Resolution Make sure that the user configured in EBO semantic settings matches the user created in the GraphDB web interface. In WorkStation, in the System Tree pane, select the EBO server. Click the Control Panel tab. Click Navigate to Sparql database, this will open the GraphDB web interface. Login with the admin user account.  In the top right corner, make sure that correct repository is selected, default name is "nsp".  Go to Setup -> Users and Access. Edit user "nspService". Set a password for the "nspService" account and make sure it has access rights to the "nsp" repository then click save. In EBO WorkStation control Panel, open Semantic Settings. Set the password for username "nspService" to match the password set in the GraphDB interface. For more information, please refer to the GraphDB help: Secure GraphDB — GraphDB SE 9.10.0 documentation (ontotext.com)

Issue PCT error 'Hardware virtualization is not enabled. Please enable in BIOS before continuing' Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool Windows 10 Cause Windows Hyper-V is enabled Resolution Firstly, in BIOS check and confirm the computer’s Hardware Virtualization is enabled.  See the following article which may provide assistance with this.  PCT Intel Processor Virtualization.   Once confirmed that this feature is enabled within the bios then, within Windows, open Control Panel\All Control Panel Items\Programs and Features, in the left pane select “Turn Windows features on or off” Check to see if Hyper-V is enabled: If it is, uncheck the checkbox next to Hyper-V. This change will require the computer to be restarted for the change to take effect.   If Hyper-V does not deactivate properly and gets launched automatically at startup, you can instead disable Hyper-V through an elevated command prompt with the following command: bcdedit /set hypervisorlaunchtype off  

Issue Having inconsistent results installing PCT on various host platforms. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Having difficulty installing PCT successfully. Resolution PCT "Server Mode" installation Sign in and add the computer to the domain Download and install the PCT Server software with an Administrator account Select the “Server” Setup Type Select the hardware Ethernet Connection for the network adapter Allow the Virtual Box installer to complete Reboot the computer Disable Windows Firewall as needed, or add the required firewall rules to allow connections to the PCT If desired, download and install the EBO License Administrator, and any required versions of EBO Workstation and Server Packages (1.9, 2.x, 3.x). Individual User Laptop Setup Download and install the EBO License Administrator, and any required versions of EBO Workstation (1.9, 2.x, 3.x) Download and install the PCT Client software Individual User Laptop Usage Open the PCT client and connect to the desired PCT server Enter the IP address of the PCT server machine to connect once, or click the “Setup for use with remote server” link to adjust the properties of the PCT client to always connect to the same PCT server Once connected to the PCT server, install all the desired Server Packages for the first use Create a new project, or open an existing project If the project’s servers are not running, start them Once the required servers are running, open Workstation to develop the project   For the purpose of testing the procedures described above, following hardware was used.   OPTIPLEX 7060 Micro XCTO Intel vPro Technology Enabled Dell Data Protection Threat Defense Subscription, 3 Years US Order Standard BIOS - Fastboot - Auto Asset Report Thermal Pad 2 512GB PCIe NVMe Class 40 Solid State Drive 32GB 2X16GB DDR4 2666MHz Non-ECC Shipping Label for DAO Intel Core i7-8700 (6 Cores/12MB/12T/up to 4.6GHz/65W); supports Windows 10/Linux TPM Enabled CMS Software not included MOD,PLCMT,QSG,7060,MFF,DAO1 OS-Windows Media Not Included SW for 7060 with Win10 OS No Integrated Stand option OptiPlex 7060 Micro with 130W up to 87% efficient adapter No Wireless LAN Card No Anti-Virus Software Desktop MFF BTO Standard Shipment No Intel Responsive No Additional Hard Drive Intel Unite Software Not Included Safety/Environment and Regulatory Guide (English/French Multi-language) No Productivity Software No AutoPilot Win 10 Pro 64 English, French, Spanish Ship Material for OptiPlex Micro Form Factor 130W AC Adapter Regulatory LBL for 130W adapter (65W CPU Chassis) No CompuTrace No UPC Label US Power Cord 8th Gen Intel Core i7 vPro processor label No Option Included No FGA Energy Star Dell Developed Recovery Environment Waves Maxx Audio Dell Client System Update (Updates latest Dell Recommended BIOS, Drivers, Firmware and Apps) Dell(TM) Digital Delivery Cirrus Client SupportAssist Not selected in this configuration NO ADAPTER No Cove Black Dell MS116 Wired Mouse Black Dell KB216 Wired Multi-Media Keyboard English No PCIe add-in card 5 Screw for SSD/DDPE ProSupport for Dell Data Protection Threat Defense, 3 Years ProSupport Plus: 7x24 Technical Support, 3 Years ProSupport Plus: Next Business Day Onsite 3 Years ProSupport Plus: Keep Your Hard Drive, 3 Years ProSupport Plus: Accidental Damage Service, 3 Years Dell Limited Hardware Warranty Plus Service

Issue When attempting to add a new Automation Server under an Enterprise Server that already has one or more AS servers attached it results in an "Object already exists" error ERROR Object already exists Domain: Data access Info:~/System/Server Communication/Models/xxxxxxxx/Members/xxxxxxxxx in module Run Db manager xxxxxxxx = Global Unique Identifier (GUID) The GUID underlined in red in the screenshot above is the duplicated Id. Additional error message possible depending on EBO release version. ERROR: Server already part of a multi server system Domain: Invalid data  Info: Attempt_To_Add_An_Object_To_The _System_That_Already_Exists ERROR: Cannot add a server that is a clone of a server that already exists in your system Domain: Startup  Technical Info: An added server with name 'XXXXX' has the same unique id as an existing server with the name 'YYYYY' which is not allowed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server  Building Operation Automation Server Bundled Cause The AS that is being added has been restored from a backup created from one of the servers that are already configured under the ES resulting in a duplicate GUID. Resolution Backup the Server Restore the Server and make sure to select "Restore configuration with new IDs" check box. This will ensure that a new GUID is assigned to the AS. Add the Server from ES Please note that the restore function to re-use configuration data from a backup set is supported for all Building Operation supported protocols, except for BACnet and b3 BACnet.  To read more see Web Help To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7 To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com  

Issue Connecting lines in WorkPlace Tech stay red even when snapped to an object. Product Line TAC IA Series Environment WorkPlace Tech Cause Verify that the Visio "Snap" option has been turned on. Resolution The following procedure can be used to verify this setting. Open the Workplace Tech Tool and open an application file. From the "Tools" menu, select "Snap & Glue" In the displayed window, verify that the following items are checked: Snap (under Currently Active) Glue (under Currently Active) Connecting Points (under Snap to) Connecting Points (under (Glue to) Click the [OK] button on the "Snap & Glue" window to save the changes and close the window. Additional "Snap to" options are normally selected by default. These options should remain selected for consistency of operation. It is suggested, to prevent inadvertent changes to these settings, that the "Snap & Glue" toolbar NOT be turned on.

Issue Does the entire SBO system need to be upgraded to 1.5.0.171xx, 1.6.2.12xxx or 1.7.2.111xx before upgrading to 1.9.1 if the network includes LON devices? Can SBO be upgraded directly to 1.9.1 from 1.5.X, 1.6.X or 1.7.X? Product Line EcoStruxure Building Operation Environment SBO Workstation 1.5.0/1.6.1/1.7.1 SBO ES 1.5.0/1.6.1/1.7.1 SBO AS 1.5.0/1.6.1/1.7.1 SBO AS-P 1.7.1 Cause In systems that have SBO servers that already are hosting LON devices based on LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to be prepared before an upgrade from versions 1.5/1.6/1.7 to version 1.9.1. Even servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no devices or network variables are created yet, the servers have to be prepared before the upgrade. Resolution Please see section 9.2.3 of SBO 1.9.1 Release Notes. Although it says "Steps to upgrade a 1.6.2/1.7.2 multi-server system" you don't have to upgrade the AS or ES etc, even if they run 1.6.1/1.7.1, it's only SBO Workstation that need to be hotfixed. Links to the different Workstation hotfixes can be found Server with LonWorks devices - TPA-SBO-17-0002.00 - Links to hot fixes. If there are no LON devices in the system, you may upgrade directly to 1.9.1 from 1.5.X/1.6.X/1.7.X

Issue When trying to edit or create a new Plain English program the editor fails to open. Environment CyberStation Plain English Editor Cause Corrupted PlainEnglish.ini file Resolution Open Windows Explorer Go to the Windows directory Find the PlainEnglish.ini file and delete it. When the Plain English editor is opened after this file is deleted it will recreate a new PlainEnglish.ini file with all the default settings.

Issue Active alarms are appear stuck in the alarm viewer for objects that are no longer in alarm.   Alarm notifications will not clear from Active Alarm View. How can obsolete alarms be removed from the Active Alarm View Product Line Andover Continuum Environment CyberStation WebClient Cause When a Return to Normal (RtoN) notification is reported by a controller, if Cyberstation is unable to receive the notification due to a loss of communication, the status of the alarm notification will not be updated and the alarm will continue to be displayed as though it were active even though the point alarm state is now inactive. Resolution Method 1 Disable the object and change it's value so that a new alarm is induced. Refresh the object editor until it indicates that the alarm state is active. Enable the object so that it returns to a normal value. If necessary, acknowledge the alarm so that it can be removed from the alarm list. Method 2 Backup the Continuum Database. Edit the object to confirm that it is no longer in an active alarm state. From the Root/ListView folder, open the Alarms_AllActive Listview. Locate the alarm entry associated with the object. Right click on the line and select Delete. Restart Cyberstation to update the Active Alarm View from the alarm log.