Building Automation Knowledge Base

Issue How to add and bind SNVTs to a local node High bandwidth usage on FT10 LonWorks network causing slow system response Product Line EcoStruxure Building Operation Environment LonWorks FT10 network Cause FT10 bandwidth is too high due to a large TGML graphic or lots of Change of value trends set up in the server polling points on the FT10 network.  Resolution The local node resides within the Automation Server so the trend or graphic that is polling every 0.5 to 1-second will only poll the local node and not out on the FT10 LonWorks network. The SNVTs in the field then updates the Local node at a frequency rate setup in the SNVT.   Here is a link to a Quick help Video showing how to set up and bind to a Local node

Issue The BACnet object goes into fault when writing a NaN to an MNB controller. Product Line TAC IA Series Environment I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 Cause Firmware 1.424 and higher responds to receiving a NaN with an Error: "value out of range".  In firmware 1.420 it would accept the NaN and respond with a normal acknowledge message.  This is a result of a change required for BTL compliance. Resolution A slight setup change can accomplish the same result without causing the object to go into fault.  In the ENC edit the properties of the AVSPP object and set the fallback to "null".  Go to the slot sheet of the object being overridden to hide the "Set" option.  This will prevent the operator from attempting to send a NaN that causes the fault.  When a right-click override is performed only the emergency (priority1) and Override (priority8) choices are displayed.  When the override expires or the object is manually put back into “auto” the “fallback” value is output which is “null” and that is accepted at the controller and serves the same function as sending a NaN.

Issue SE7000s (all) and old hardware SE8000 (firmware <= 1.7.4) won't support EBO Zigbee. Product Line EcoStruxure Building Operation Environment SSL SE7000 SSL SE8000 Cause EBO Zigbee has Standard and High-Security levels. The SE7000s and old hardware SE8000 (firmware <= 1.7.4) only supports Zigbee Low Security. Resolution Replace the SE7000s and SE8000s old hardware using SE8000 with the current hardware that supports firmware 2.0.0 and newer.

Issue The bandwidth utilization in the Lon network is high, it is possible to see what Lon device and what objects in the Lon device that is causing the high load on the Lon network. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause When the load on the Lon network is too high (above 50%) you need to analyze the Lon communication to understand what Lon devices and objects in the Lon device that is causing the high load on the network. Resolution Use a Lon Protocol Analyzer to measure the Lon bandwidth utilization on the Lon network if the load on the network is too high (above 50%) analyze the communication. When doing that it is possible to use the trace log in the ES or AS-P, please see attached video of how that is done.    Configure Trace Log to capture Lon Communications Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon Right-click "nsp.pin.lon.comm" and choose Properties Under Level, change from "Information" to "Trace", then click ok Let it run for a few minutes. If there is some user input needed to recreate the lon issue, then perform these steps now Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log Save the log file

Issue EcoStruxure Building Advisor does not connect by default to the Automation Server and the request to EWS returns a HTTP 401 error Product Line EcoStruxure Building Operation Environment Building Operation SmartX Server EcoStruxure Building Advisor Cause Required configuration in EBO to enable EcoStruxure Building Advisor Resolution An EBO connection to EcoStruxure Building Advisor requires MD5 authentication to be enabled, disabling it in EBO will result in EcoStruxure Building Advisor being unable to connect. The “Allow authentication with MD5 hash” can be enabled under the EBO Security manager. During the TLS handshake process, both the EcoStruXure Building Analytics Data Transfer Service (DTS) and EBO negotiate to use Sha384 encryption regardless of whether MD5 is enabled/disabled in EBO. With MD5 enabled, the use of Sha384 encryption works as expected. With MD5 disabled, the use of Sha384 encryption does not work and the request to EWS returns a HTTP 401 error. MD5 is disabled by default in EBO v2.0 and later.

Issue What is the basic steps and workflow when connecting a Zigbee device to an AS-P? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause Zigbee is a communication protocol used to create personal area networks with small, low-power devices Resolution As described in EBO Webhelp the workflow is as follows:   Create a Zigbee interface and network Import Zigbee device files Create a logical Zigbee device in EBO Enable the Zigbee network Discover the physical Zigbee devices Associate the logical Zigbee device with the physical Zigbee device For more details please see video:

Issue What is the proper way to replace AS hardware for an existing node. Cannot get the AS to come online in the Enterprise Server after replacing the AS hardware for an existing node. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server - Classic (AS) Building Operation Automation Server - Premium (AS-P) Building Operation Automation Server - Bundled (AS-B) Cause To replace the AS hardware, a backup must have been made from the original AS while it was online.  Simply changing the controller name, IP information, and domain  information in the AS will not be sufficient for bringing the controller online in the ES. Before the new automation server can be brought online, the backup from the original controller must be restored to the new AS directly. Resolution This procedure assumes that a backup of the original AS is available. From Device Administrator and the USB interface, run the SetIP command to configure the following information in the new AS to match the original AS configuration. Note: You will have to use the version of Device Administrator that matches the replacement AS firmware. If necessary, use the appropriate version of Device Administrator to Upgrade or downgrade the firmware in the new AS so that it matches the Enterprise Server and/or the original AS hardware firmware. Install the AS then backplane. From StruxureWare workstation, log into the AS using the hardware's IP address for the Server field. Right click on the server name and select Restore. If the backup does not appear in the Available restore points window, click on Import Backup Set and browse to the backup file. Select Configuration only or All data in the window on the left. Select restore. Once the restore has completed the AS displays a solid green status light, log off the AS and log into the ES. The controller should now appear online in the ES.

Issue Is it possible to connect eComission SmartX controller mobile application to a SmartX controller with no WiFi available in the building and BLE(Bluetooth) not turned on in the SmartX controller. Product Line EcoStruxure Building Operation Environment Building Operation eCommisioning Tool Building Operation Room Controller (RPC) Building Operation Multi-purpose Controller (MPC)   Cause The eCommission SmartX controllers mobile application supports device connection through BACnet Wi-Fi and wireless Bluetooth connection. Resolution Install eCommission SmartX controllers on a computer, connect to the SmartX controller using an IP cable connected directly from the computer to the SmartX controller and enable Bluetooth on the SmartX controller.   Disconnect IP cable from the SmartX controller if there is one connected. Restart the SmartX controller, since it can’t reach the DHCP server it will get an IP address in the range of 169.254.x.x. Make sure the computer IP address is in the same IP range as the SmartX controller. Connect the IP cable directly from the computer to port 2 in the SmartX controller. Start eComission SmartX controller mobile application and connect to the SmartX controller. For details please see the video.

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 Active Event Viewer contents and column headers are blank.   Product Line Andover Continuum Environment CyberStation Cause Windows registry corruption. Resolution Method #1 Close Continuum and use Windows System Restore to put the system back at a point where the Event Viewer were fine. Method #2 NOTE: Any customization previously done to the event viewers such as column name changes etc  will be lost when this method is used Shut down CyberStation then backup the Windows registry as a precaution Edit the Windows registry and delete HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Access Event View Start CyberStation and open the event viewer which recreates the entry in the registry using default values.

Issue A Log Processing Trend Log created in an EBO server and connected to an Extended Trend Log will not transfer any records even if the Force Transfer command is executed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Log processing trend log records are not saved to database, so they will not be transferred to Extended Trend logs. Resolution In the Basic Properties of the Log Processing Trend Log, set "Persist data" to True to store trend data in the database. This will enable the records to be transferred to the connected Extended trend Log.

Issue The XML Automation Server application on the WebClient Server does not open when a remote WebClient browser tries to access WebClient. WebClient does work from the browser on the WebClient server itself but can't be accessed from another PC. The XM Automation Server keeps closing by itself. Environment WebClient Windows Server 2003, Windows Server 2008, Windows 7 Cause DCOM Permissions have not been set properly to allow access to these WebClient components. Resolution Confirm that DCOM permissions have been set properly. Follow the steps detailed in the section "Configuring DCOM Default Security Settings" starting on page 100 in the WebClient Installation Guide, paying particular attention to the NETWORK SERVICE account. Please see the link below for the relevant section from the WebClient v1.94 Installation Guide. DCOM Permissions excerpt from 30-3001-835 webClient Planning and Installation Guide

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * CPs are available on: EBO Hotfix List Note: Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   Note: RP-C is only supported on EBO 3.0 and later SpaceLogic/EasyLogic versions compatibility SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: Previous to Version 1.0, SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 2.0 (Build 77) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well. Release Notes  Starting with Version 3.1 (Build 85), firmware 6.00.03.03007 CP2 and 7.x RC can be employed. The EasyLogic controllers are supported by the Niagara modules with these releases.  N4.10, 4.13 and 4.14 are the only versions with these modules. Product Annoucement      

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue What is the purpose of the battery/coin clip on some of the I/NET Hardware Product Line TAC INET Environment TAC INET Hardware  7718, 7716, 7798C  Cause The initial development path plan was to include an additional feature to allow communication with Dallas Semiconductor ID tag/coin, similar to that used with the I/NET Access Control I/DISC.  This development was never implemented Resolution This battery/coin tag serves no active purpose or functionality

Issue SE8000 Best Practices Product Line Field Devices, EcoStruxure Building Expert Environment SE8000 Cause Best Practices for commissioning SE8000 room controllers Resolution The following information has been contributed by a field engineer and their experience to assist others in commissioning the SE8000 device. It brings together or provides leads to various articles that can be found on the Download Center. SE8K Programming Tutorial v1.1

Issue What will happen with the EBO license when used with cloned Virtual Machines in a fail-over scenario to another host? Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Cause Even if the Virtual Machines are "cloned" the licensing will show as "Damaged" Since Virtual Machines don't have unique hardware and the software images can be identical, another identifier called UMN3 (Unique Machine Number 3) is provided by the Virtual Machine. This is, as the name indicates, unique for each Virtual Machine. Without this feature, it could be possible to cheat the licensing system and run many instances of software without a license being purchased for each instance.   See the following technical description of the virtual machine image identifier (VMID) that provides the UMN3   A hash of the universally unique ID (UUID or SMBIOS3) that the hypervisor issues whenever a virtual machine is created or cloned. SMBIOS is commonly virtualized by hypervisor providers such as VMware and Microsoft. In addition, virtualization management systems such as VMware’s VMotion ensure that all virtual machines being managed have a unique SMBIOS value. Resolution If Virtual machines are being utilized to provide a fail-over or "hot swap" of the EBO Server then licenses need to be purchased for each Virtual Machine, just as if two physical computers were used. Each Virtual Machine will require its own License Server installation and have the required licenses activated.

Issue During the initial configuration of the Suprema Biometric integration with Security Expert, the existing user information stored in Suprema Biostar is not imported into Security Expert. Only new Users enrolled through Security Expert are available. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Integration Cause The user database in the Suprema Biometric devices is not automatically brought over into Security Expert during configuration of the integration. This database of users needs to be created and biometrics enrolled through Security Expert. Resolution A workaround to getting this user information into Security Expert would be to export the user data from Suprema to a CSV file and then import that into Security Expert.   After these Users have been created in Security Expert the fingerprint enrollment will need to be redone to capture this within Security Expert. To Export from Suprema: Click on the USER menu. Select a user or multiple users to export. If you want to export all users in the server, click on the dropdown button and click Select All. Click on … below the user search bar. Click CSV Export. The csv file is stored in your Windows Downloads folder. To Import User Records into Security Expert from a CSV File: Navigate to Sites | Import Users to launch the Import Users wizard. Browse to and select the CSV File you wish to import the users from, then click Next. Select the line to start importing data from and the text delimiter to use, then click Next. If your CSV file contains a header row, ensure you start the import at line 2 so the header row is not imported. Select each column in the panel on the left and map it to the associated fields you wish the data to be imported into on the right. The data in the top pane is updated as you make your selections. Click Next to continue. Assign the facility number, first card number, and access level if you have not already done so. You can also choose to generate PIN numbers automatically. Click Next to continue. Click Finish to start the import process. The user records are imported and the wizard closes.

Issue When trying to browse for Areas to assign to the Area Inside Door and Area Outside Door fields in Door records, not all Areas are shown or available to be selected. Product Line EcoStruxure Security Expert Environment Security Expert Cause The Programming Mode selector is set to "Local" which is the default value. This will only show objects that are already attached to the controller this record resides in.   Programming Mode Resolution Change the Programming Mode to "Global" which will now show all Area records, including those unassigned or assigned to other controllers.   Programming Mode Global

Issue A Dashboard is created with a couple of widgets in it, the widgets are placed where they should be and the Dashboard looks good. But if the Dashboard is opened in a monitor with a smaller screen, the available work area for the dashboard is smaller and the widgets move around. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause There is no option to lock the widget positions on both horizontal and vertical axis as the screen area available to the dashboard changes when creating the Dashboard. Resolution Set the Maximum column count in the Dashboard Layout setting to the total number of columns of the desired widget layout. For example if widget one has Column span 2 and widget two has Column span 3 then the Maximum column count should be set to 5 for the Dashboard. Then set the Minimum column size to 0. Now the text still scales but the widgets lock in position.

Issue For EBO Active Directory (Windows Domain) integration, do EBO support usage of "nested groups"?. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause EBO are using Windows API and ask if the user is a member of a certain group.  Resolution Windows API should respond “yes” if the user is part of a group that is part of another group, which is configured in EBO. So this is up to how the Windows AD responds to the Windows API and not on the EBO side.   For more information, please see Integrating Windows Active Directory user accounts with EcoStruxure