Building Automation Knowledge Base

Issue How to Discover devices on the LonWorks network. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When adding LonWorks devices to the network, it is possible to let the SmartX server scan the LonWorks network. Resolution Open Workstation and locate your SmartX server. Left-click on the SmartX server to select it. Select the "Discovery Devices" tab. In the "Select device Type" drop-down list, click to expand the options and choose "Lonworks". Right-click on the "Devices" folder. From the context menu, select "Scan network for devices". Drag from the discovered devices and drop them into your Lonworks network under the SmartX server. Commission the devices. Following these steps should initiate the device scanning process and help you discover Lonworks devices on the network.   This video will show how to discover lonworks devices on a lonworks network.   At the end of this session you will be able to: Discover devices on the LonWorks network Add the discovered devices to your system  

Issue Which Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell Sigma Environment Sigma controllers Ethernet New Hardware. ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) Old Hardware V53  (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause The newer ARM-7 controller hardware supports more Ethernet connection speeds than the older V53 controller hardware. Resolution Most Ethernet hubs or switches autoscan to find the best connection speed.  For Sigma device hardware types, the supported Ethernet speeds are as follows: ARM-7 (New hardware): 100Base-T (and supports port auto-scanning on connection) 100M Half Duplex 10M full/half duplex V53 (Old hardware): 10Base-T (does not support port auto-scanning) 10M half Duplex Additionally, for direct connections to a Sigma controller: ARM-7 Ethernet connection supports both straight and cross-over Ethernet cables. V53 hardware only supports cross-over cables.

Issue What is the benefit in having separate MPM monitor and coordinator? Product Line EcoStruxure Building Expert Environment MPM Cause In smaller networks, it is acceptable to have the monitor function as the coordinator. However, in larger networks, the monitor becomes occupied with managing the traffic of all the remote MPMs, resulting in significant CPU usage. This applies to zigbee, UDP, and CANbus networks. Making the monitor a coordinator does not provide any advantages; it only introduces disadvantages. Resolution In smaller networks, it is acceptable to have the monitor act as the coordinator. However, in larger networks, the monitor's workload increases as it manages the traffic of multiple remote MPMs, consuming a significant amount of CPU resources.

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps from WebHelp topic Repairing an EcoStruxure Building Operation Software License. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all files:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue Which SpaceLogic Sensors could be used with the TAC Xenta 100 series controllers? Product Line TAC Vista Environment ZBuilder Xenta 122 Cause The STR100-series sensors will be withdrawn, and SpaceLogic Sensors have been identified as suitable replacements. Resolution Only TAC Xenta 122 controllers can be configured to use 10K Type 3 Thermistor.   To integrate SpaceLogic Sensors with the TAC Xenta 122 controllers, follow these steps in ZBuilder: Access the Configuration tab. Navigate to the Room unit settings. Locate the checkbox labeled "Use STR-5xx series" and select it.   Please note that only the SLASXXX, SLABXXX, and SLAWXXX models are compatible with the TAC Xenta 122 controllers. These sensors, however, do not feature buttons for setpoint adjustment or fan control.  

Issue What is the minimum pulse duration for the digital inputs (X1 - X3) on the TAC Xenta 121-FC? Product Line TAC Vista Environment Vista Server Xenta 121 Cause The device requires a certain pulse duration to be able to register the feedback signal from another device, such as a fan running signal. Resolution The minimum pulse input duration is 250ms. Click here to open the datasheet for Xenta 121-FC

Issue TAC Vista Error Codes in Plain Text Product Line TAC Vista Environment Vista Server Vista Workstation Cause Vista will sometimes give an error code. This list decodes the TAC Vista Family Error Codes. Resolution For a list of TAC Vista Error Codes in plain text click here.

Issue nvoSpaceTemp from TAC Xenta 100 series used with the room unit STR150 does not read temperatures greater than 33.4 °C (92.3 °F). Product Line TAC Vista Environment ZBuilder Xenta 121 Xenta 122 STR Sensor Cause The STR150 and the Xenta 100 line of controllers are capable of displaying temperatures greater than 33.4 °C (92.3 °F) or less than 8 °C (46.4 °F). However, the communication protocol between the STR150 and the Xenta 100 series is limited and thus restricts the temperature that the TAC Xenta 100 can read from the STR150 device. Resolution The STR150 data sheet states that temperature range transferred to a TAC Xenta 100 device is limited to 8 °C through 33.4 °C (46.4 °F to 92.3 °F). If temperatures outside of that range are needed an STR100 (simple 1.8k thermistor) or an STR-350 (communicating Lon stat with display) could be substituted. The ranges of those devices connected to a TAC Xenta 100 device are as follows: STR100: –10 °C to +50 °C (14 °F to 122 °F) STR350: 5 °C to 45 °C (41 °F to 113 °F)

Issue Error message in Platform Application Director; SEVERE [00:25:32 08-Feb-21 EST][sys] Cannot boot Product Line TAC IA Series Environment I/A Series N4.9 and later I/A Series N4 Enterprise Server I/A Series N4 WorkBench Cause In 4.9.1.30 and later, the JDK distributed with Niagara was upgraded to 8u271. Starting in JDK 8u261, the target Visual C++ version was changed. While the updated libraries are available in the jre/bin folder, this folder is not on the PATH for NRE binaries. This can cause Niagara to fail to launch on Windows if another copy of the Visual C++ Redistributables is not present. Resolution Install the Visual C++ 2017 Redistributables. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads At the time of this article, Microsoft packages the 2015, 2017, & 2019 redistributables together. Select and install the x64 version.      https://aka.ms/vs/17/release/vc_redist.x64.exe    

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Issue Using Xenta Controllers with a Tridium Jace Product Line TAC Vista, TAC IA Series Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Tridium AX / N4 Jace Cause By default, the Tridium Jace acts as a network manager which will disrupt controller addresses, SNVT bindings, and Group bindings previously set up in LonMaker. Resolution  To disable this feature provide these steps to a Tridium Integrator: Use Niagara WorkBench Connect to Jace Under the Services Folder, find "LonNetwork" Go to  "Local Lon Device" Set the "External Config" property to "true" Hit "Save"  

Issue How can the AS-P be used as an LPA interface? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium. Cause Working with Loytec LPA in  Building Operation and needing a remote interface for connectivity. Resolution To configure the AS-P as an interface in Loytec LonWorks Protocol Analyzer (LPA), follow the steps below: Ensure that you have the Loytec LonWorks Protocol Analyzer (LPA) software installed and licensed. Activate the AS-P as an LPA interface: Access the Loytec LonWorks Protocol Analyzer (LPA) software. Locate the settings or configuration section. Enable the option to "Activate AS-P as LPA" to designate the AS-P device as the interface. Add AS-P as a remote network interface in LPA: Within the Loytec LonWorks Protocol Analyzer (LPA) software, navigate to the network interface settings. Look for the option to "Add AS-P as Remote Network Interface" and select it. Keep in mind that by using the AS-P as the LPA interface, you will only be able to capture and analyze the traffic addressed to or from the AS-P device itself. Network traffic between other devices on the LonWorks network may not be captured using this configuration.   It's important to have the Loytec LonWorks Protocol Analyzer (LPA) software installed and properly licensed to perform these steps.  

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. 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 Making up battery cables and need to know the part number of the 2-pin battery connector. 2-pin battery connector Product Line EcoStruxure Security Expert Environment Security Expert SP-PSU-4A SP-PSU-8A Cause Parts not listed in documentation. Resolution The part number for the 2 pin connector is: 2114H-02 The part numbers that make up each of the battery cable types are: CABLE-BATT-SINGLE 2114H-02 x 1 2114T x 2 D70400BS-2 x 2 CABLE-BATT-DUAL (This is an extender for the single cable) D70400BS-2 x 2 A27740CT-ND x 2

Issue The Conversion Settings guideline is not documented. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 Cause Lack of information on "Conversion" column in Conversion Settings for B3 and I2 Resolution The Conversion column has the highest priority in the setting. If a formula exists then the setting below will not affect the Value.   Example The ElecValue is set to 10 for the following examples. 1. The Conversion field is empty, the ElecValue = 10 which corresponds to 100 on the Engineering scale. The Input Value = 100. 2. The Conversion field is set to ElecValue, and the ElecValue = 10. The Input Value = 10. 3. The Conversion field is set to ElecValue - 7. The Input Value = 3.  

Issue These LED light sequences are not found in the documentation Solid White Flashing White Alternating Blue and Amber Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Not yet added to current documentation Resolution Solid white forever is either no firmware in the controller or the controller is running UBoot and not launching the firmware. Solid white, transient, and followed by yellow/amber, is UBoot running. Perform a factory reset and attempt to upgrade the firmware to the latest revision allowed based on the version of EBO used on site Flashing white would indicate a defective board requiring RMA or a power supply problem (It was seen on one site the 24Vdc power supply had been damaged and was only supplying 12 to 14Vdc. Thus replacing the power supply solved the problem) Alternating Red/Blue happens during an up rev of the firmware. It specifically happens when the EFR32 (the Bluetooth chip) is being upgraded. Generally, power supply problems can cause various issues with RPx and MPx controllers, including partial corruption of the firmware/application. A recent case had transformer secondary circuits linked that cause Red/Blue flashing and 'untranslated BACnet errors’ following a site wide power cycle. Always ensure the RPx power supplies are within tolerance and fully compliant to Grounding and Power for Systems WebHelp has been updated to include more information see RP Controller Status LED

  Issue When attempting to add a new user to the system in EcoStruxure Building Operation, a workstation crash occurs upon selecting the Create button. The crash dialogue shows: parsing "[]" - Unterminated [] set Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The workstation crash is triggered by a misconfiguration in the password policy settings. Specifically, the Special Character field has been unintentionally deleted, resulting in it being left blank. However, the password policy still requires a minimum number of special characters to be entered (set to 1 or more). Resolution To resolve this issue, follow one of the two options below: Restore the default special characters: Access the password policy settings in the control panel. Locate the Special Character field. Click on the "Default Characters" button to add the default special characters back to the field. Disable the requirement for special characters: Access the password policy settings in the control panel. Locate the option for "Minimal number of special characters". Modify the setting to "0" (zero) to remove the requirement for special characters. By implementing either of these solutions, the workstation crash issue should be resolved when creating new users in EcoStruxure Building Operation.

Issue Deleting BACnet objects using a BACnet Operator Workstation (BOWS) can permanently remove those objects from the BACnet device.  The effected devices can be Building Operation BACnet devices, e.g. Automation Server or third party BACnet devices. Environment Building Operation Enterprise Server Building Operation Automation Server 3rd Party BACnet Controllers Cause The BACnet controller(s) in question support BACnet create and delete services on the specific objects.  Resolution Functions as Designed If the device supports create and delete services for the object it is designed to function this way. In general the BOWS should provide as much as possible a complete and accurate image of the contents of the device.  For example using the Enterprise/Automation server as a BOWS:  Creating new objects will automatically send a create-object request and attempt to create the object in the device. Deleting objects will automatically send a delete-object request and attempt to delete the object in the device. Upload and Download of object commands attempt to synchronize the database with the actual contents of the device.  Download will attempt to create any objects that are in the database (but not in the device), and also attempt to delete any objects from the device which are not in the database. Upload adds or removes objects from the BOWS database. Please see Protecting EBO/SBO BACnet objects from being deleted by 3rd party BOWS for a method of preventing BACnet points being deleted from an Enterprise/Automation Server.  Consult third party documentation to identify preventing creation/deletion.   Offline Workaround If the device supports the Device Communication Control service, and allows disable, a work around is to make changes to the database while the device is offline. For example, using the Enterprise/Automation server as a BOWS, right click the device and select Device->Communication->Disable.    Open the property grid for the device and it should take about 12 seconds before the device is reported as offline.  Any other break in communication should also work to get the device offline.  Once offline, objects can be deleted from the database without affecting the device.  But, after changing the database this way, the device's "upload" or "download" commands should not be used, as it will re-synchronize the device and database (either deleting objects from the device, or adding them back to the database).  It is important to note using this method the BOWS will not fully represent the objects in the device and also remember to re-enable the communication to the device.

Issue BACnet objects that are deleted from the BACnet side keep coming back. Product Line Andover Continuum Environment Cyberstation BACnet IP devices BACnet MSTP devices Cause Require to be able to find all the BACnet devices, delete the ones not required, and not have them reappear in Continuum Explorer. Resolution When BACnet is enabled, Cyberstation will automatically add devices into its database when it hears an “I-Am” message containing a Device Identifier it does not already know about. There is no way to disable this behavior without shutting BACnet off completely. I-Am messages are typically sent in response to Who-Is messages, but not always. Sometimes devices send I-Am messages when they start up for example.  Also, since I-Am’s are typically broadcast across the entire BACnet internetwork, the Cyberstation is likely to hear I-Am messages for lots of different reasons, like in response to Who-Is/I-Am sequences it’s not directly a part of.

Issue Is it possible to prevent a 3rd party BACnet Operator Workstation (BOWS) from deleting the BACnet objects in an Enterprise/Automation server? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Current version of EBO/SBO puts the responsibility of creating & deleting BACnet objects to the site administrator.  The enhanced security on this issue will be added in the later version. Resolution The following video demonstrates how to protect the BACnet objects in ES/AS by utilizing shortcut objects.