Building Automation Knowledge Base

Issue Getting error "Failed to run: import-VM" when trying to install PCTv2 Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Could install PCTv2 fine but the issue started when going back and forward between PCTv1 and PCTv2 so that might have caused the issue. Resolution Uninstall Hyper V in Windows Programs and Features and restart computer Delete everything in ProgramData\Microsoft\Windows\HyperV Install PCTv2 version 2.0.2.13 or later

Issue The controller installation guides detail how to display the values in Water Column (WC), but how can this be displayed in metric units? Product Line Andover Continuum Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885, i2885-V, i2850 &i2853 ) BACnet controllers (b3865 & b3865-V, b3866 & b3866-V , b3885, b3885-V, b3850 & b3853) Cause A conversion to metric units (Pascals) is needed. Resolution i28xx type of Infinet Controller has 0-2" WC (Water Column) range which corresponds to 0-2V so the input value can be read directly in WC. The 850 has a single airflow sensor on channel 8 The 853 has two airflow sensors on inputs 7 and 8 For 865, 866, and 885 the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 500 The i28xx-V type of Infinet Controller has 0-1" WC (Water Column) range. For 865-V, 866-V and 885-V, the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 250  For controlling the Damper motor output Create an Infinity Output point of type Triac on Channel 1 It can then be opened/closed like any other Triac output with the use of On, -On or Off commands. Also see Setting up the override value to show the damper feedback on an i2/B3 866-V for details on reading the damper feedback on the i2/b3886-V.

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

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 Cybersecurity vulnerability scans are flagging the Building Operation License Server because it is using HTTP rather than HTTPS Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation License Server Cause The Building Operation License Server contains a web portal for diagnostics and administration. By default, the Building Operation License Server Administration web portal is configured to use HTTP Resolution It is possible from the Administration area of the Building Operation License Server Administration web portal to configure HTTPS communications. Note: this does not change how Ecostruxure Building Operation connects to the license server.   The following process configures the Building Operation License Server Administration web portal to use HTTPS   From a web browser open the Building Operation License Server Administration web portal by typing http://localhost:8888 Once the web portal opens, select Administration at the top right. You will be prompted to log on, use "admin" as the user name. If you have logged in before, use the password you have defined. If not, enter "admin" as the password, and you will then be prompted to create a password. Once signed in Select the Server Configuration tab. Under the Secure Web Server Configuration section, select Enable HTTPS Change HTTPS Port to a unique number e.g. 8443 Select Redirect Non-Secure Web Access to Secure Web Access At the bottom of the page click the Save button and close the web browser tab. Restart the Building Operation X.X License Server from the Windows Services app (services.msc) If the license server is opened using http://localhost:8888 it will now redirect to HTTPS using the port specified in step 4 above

Issue Need to upgrade sites with Report Server to EBO 2022 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher. Resolution Since WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher, there is a Data Migration Assistant (DMA) tool available which read data from a WebReports 3.x and write it to External Log Storage. You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature.  When the External Log Storage feature is activated and configured, WorkStation and WebStation display the historical data in the event and trend views from the External Log Storage. Any server in the system can be configured to write historical data to the TimescaleDB database.   Data Migration Assistant (DMA) Tool can be downloaded from here. License required: External Log Storage requires license, refer to Software and Features that Require Licenses and Part Number Summary and Hardware Software Matrix  Hardware and Software requirement for External Log Storage: Ensure that the hardware and software requirements for TimescaleDB (www.timescale.com) and PostgreSQL (www.postgresql.org) are met. High-performance SSD storage is required and additional CPU/RAM capacity is required for larger EcoStruxure BMSs. As an example, at least 64 GB of RAM is recommended for systems with 100 EcoStruxure BMS servers. Refer to: Information Technology System Planning Guide (se.com) Merging Log data: External Log Storage decreases the amount of extended trend logs retained on the EcoStruxure BMS servers. You can merge log data from an extended trend log to the source log in External Log Storage. For more information, see Merging of Trend Log Data. Enhanced Reporting (XLSX Report Templates): The EcoStruxure BMS servers (3.2 or higher) provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there. Refer to: Examples for the new native EBO Notification Reports - Communities (se.com)  

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.

Issue Multiple MP-Vs have SpaceLogic Sensors (formerly SmartX Sensors) connected, all with identical configurations.  Some are missing the Properties, Scene Configurations, Button and Scene Configuration tabs. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Room Controller (RPC)  Building Operation RP-V VAV Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause Delete the sensor and add it back, which takes a long time to execute for all sensors Resolution In WorkStation, in the System Tree pane, expand the BACnet Interface and the IP network. Click the BACnet/IP controller device. In the Actions menu, point to Device, Advanced, and then click Restore optional properties. In the Actions menu, point to Device and click Download all objects 

Issue Unable to back up the Automation Server Unable to retrieve a working backup from an Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Enterprise Central Cause Corrupt configuration.db Network environment issues Power failure Resolution Database Corruption When the server backup process is initiated, the server tests the integrity of the configuration.db.  If the database does not pass the integrity test, the backup process is terminated, and no resulting backup is produced. In this case, an older backup will need to be used.  The backup should be bench tested for integrity before restoring to the production server.   Network Environment In some cases, the AS may produce a valid backup file, but when the backup is saved off of the server the file size is unusually small.  This can happen when network issues interfere with the backup save to disk process.   In such cases, Automation Server backups taken from the Enterprise server will usually be damaged as well.    You can work around this problem by connecting a Workstation laptop PC directly to the AS with an ethernet cable, thus eliminating the network from the process. Backups can also be retrieved in this way using most versions of Device Administrator.    Power Failure The power fails while the EcoStruxure BMS server is backing up and the system displays a “Failed backup” message in the Event view. The solution is to initiate a new backup when the power resumes and the EcoStruxure BMS server goes back online. Power Failure Occurs During Backup     

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source.   Issue STC300 terminal detail is different to Specification Sheet and Installation Sheet and there are several versions of the same device. Product Line Field Devices Environment STC300 Cause STC300 terminal detail is different to Specification Sheet and Installation Sheet and there are several versions of the same device.   Example of incorrectly wired device. Two versions of the STC300 device are shown.   Resolution On each version of the devices, there is a printed termination legend adjacent to the terminals, follow this.   24Vdc from the power supply is wired to 24V Loop+ on the device. Signal to controller is wired to Loop- on the device.   On the controller, the RET is wired back to the 24Vdc supply using the GRD or RET terminal, see power supply specific wiring detail.    

Issue Delete Lonworks Device Templates Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server LonWorks devices Cause Some templates are preloaded with the software; if the particular device does not have a supplied template, you can upload an XIF file. This is done by selecting File/LonWorks import/Device Template and then importing the XIF from the manufacturer. An unused Device Template causes no harm to the system; however, there may be a desire to remove a Device Template. Resolution EBO 3.x and later Device Templates can be added and deleted in all device types using the Resource Manager - Device Templates tab SBO 1.x and  EBO 2.x Device Templates cannot be directly deleted from Building Operation WorkStation, however, they can manually be deleted from the  Enterprise Server file system. When a device template is imported, you should understand if the template should be located in the Enterprise Server or an Automation Server.   If the device template is located in an Automation Server, it can only be removed by upgrading the Automation Server using the Device Administrator (you can stay with the current release). If the device template is located in an Enterprise Server, it can be removed using the following process. Locate the template path in the Building Operation database (e.g., C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.3\Enterprise Server\db\UDT\public\public\lon\devicetemplates) Note: in newer releases, the path has changed slightly, e.g., For V1.8.1: C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.8\Enterprise Server\db\UDT\pu\public\lon2\devicetemplates   Delete the two template files named Pidxxxxx, where xxxxx are the numbers or letters in parenthesis behind the device template's name visible in WorkStation. After deleting the templates, you may need to restart the Enterprise Server.

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. Issue Difficulty getting b3 controller online in order to replace a failed one Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Continuum b3 Controller Cause A b3 controller has failed and needs to replace with the same model. Resolution Remove the failed b3 controller. In EcoStruxure Building Operation Workstation change the serial number of the failed b3 to that of the replacement b3. Install the replacement b3 and ensure the MSTP bus is connected so it autobauds to the correct rate. Then power it up. Remove the battery tab from the replacement b3 (if applicable). In Workstation right-click on the replacement b3 and select Device -> Commission. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Download all objects. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Device -> Backup to flash.

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue Every time an alarm comes in to Workstation, the Alarm View pop up window opens up. Product Line EcoStruxure Building Operation Environment Workstation Alarm View Window Cause This is a setting that can be turned off and on as desired. Resolution Right click anywhere inside of the alarm queue (either on an actual alarm or in the white space below the alarms). Go to "Alarm view settings." Check or uncheck "Display alarm view" to turn on or off the pop-up feature.

Issue The Automation Server is constantly using 100% CPU causing a slow operation Product Line EcoStruxure Building Operation Environment Automation Server Cause Check which process is taking the CPU. Cause 1: The cause was found to be a Function Block Program which was corrupt in some way. When trying to edit, open properties or do anything with this Function Block Program Workstation just hang. The root cause of the problem with the Function Block Program was never found. Cause 2: Some schedules have more than one entry for the same time stamp (likely if the process "CScanner" is taken the CPU) Resolution Solution 1: After deleting the particular Function Block Program (which took over 2 hours) the CPU usage was directly down to 20%. Another solution for an AS with the same symptoms: After downloading a new database to the automation server and then restoring a backup the CPU usage went down to normal levels.  Solution 2: Check all schedules for duplicate entries, especially around the time where the CPU goes to 100%. Also check out the SmartStruxure Quick Help - AS CPU and Memory Loading Quick-Help video on the Exchange.

Issue Can the AS Network 8000 ASD Interface directly override a block output (DO or AO) in a MicroZone II controller on the ASD bus? Environment SmartStruxure, Automation Server, I/A Series Network 8000, ASD Cause The driver is not currently designed to perform direct override of block outputs. Resolution There are a couple of methods to perform a block output override. Directly connect to the ASD bus with XPSI and perform a System - Override to force a MicroZone II block output to a particular value for a designated period of time. Add logic to the MicroZone II application to enable overrides using the devices network control EMS AI and EMS DI inputs.

Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Issue Can the damper feedback function be calculated using Plain English based on the drive time of the damper? Product Line Andover Continuum Environment Continuum i2866-V Controller Continuum b3866-V Controller Cause For this controller application, information about the vav damper position is required.   Resolution Only the i2866-v and the b3866-v provide integrated damper feedback.    When using other controller models such as the i2865 or the b3865, an approximation of the damper position can be calculated by adding the damper pulse value to the drive time.   Whenever the damper output is driven to the closed position, a pulse equal to the full damper drive time should be sent to the output and the damper position is reset to 0%.   Whenever the damper output is driven to the fully open position, a pulse equal to the full damper drive time is sent to the output and the damper position is reset to 100%.   Because this method of calculating the position of the damper is only an approximation, it should not be used for critical applications. 

Issue Depicting the differences between Bacnet points and Central IO points. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and lower Cause Explanation of difference in points Resolution Creating Central IO points When you create inputs and outputs in a non-BACnet SmartStruxure system, you simply create the inputs and outputs and then provide programming to control the Requested value. Trends, alarms and graphics would monitor the value property. In a BACnet SmartStruxure system, the inputs and outputs are created under the IO Module in the same way; however an additional point is created in the Application folder under the BACnet Interface Device. On the property page of that point is a field designating the “Associated Value”. You should browse to the appropriate CIO point and select it. At this point all monitoring, display and control of the object should be accomplished with the BACnet point. (It is also possible to make the link between the associated value and the IO value by using the binding tool.) There is no other binding necessary to make the link between the CIO point and the BACnet “proxy” that is created in the application folder. For SmartStruxure versions prior to 1.4 please see the attached document for some implications and proper method of operation for using the IO associated value property: PSS Building Operation Attachment 14040rev2.pdf For SmartStruxure 1.4 and above see Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above.