Building Automation Knowledge Base

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.

Issue Can the backplane, which consists of the Power Supply, Automation Server, and I/O Modules be installed in the cabinet horizontally or vertically? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation hardware installation in a cabinet with limited space. Cause Customer would prefer vertical installation rather than the typical horizontal installation. More than one Automation Server per Power Supply** Resolution What could happen if you mount the system vertically? Due to the lack of ventilation the temperature will increase, which will have negative impact on component life time. The operational temperature is defined up to +50°C. At this temperature, the horizontally mounted system will fulfill the specified lifetime of the different electrical components. In a vertically mounted system the temperature will be higher inside the modules, having negative impact on the component lifetime. Unfortunately it is not a linear relationship between temperature and lifetime - the lifetime decreases rapidly with increased temperature. Not all modules are generating the same amount of heat, and are therefore more or less sensitive to mounting direction. In my view, the most critical component is the AS. The CPU generates heat (even more important on the coming AS-P). In the AS there are also critical components that maintains power during shut-down. These component's life time is effected if the temperature becomes too hot. These components are, as stated, critical during power-down. How will this be visible to the user? During normal operation, there will be no visible effect. However, after some years when the AS goes through a power cycle, it will not restart. So, what to do if you have a cabinet with the conduits running vertically? The official answer is that the system shall be mounted horizontally. This is how the system is designed and tested. What can you do to minimize the risk you choose to take if not mounting the system horizontally? The key is operational temperature. If you are far from 50°C, then the risk is less. One thing you always should consider is to mount the PS+AS in the bottom of the cabinet horizontally, and then have the CIO modules vertically, connected via an S-Cable. This is even more important on AS-P. If you are close to 50°C operational temperature, you need to consider external cooling or at least ventilation in the cabinet in addition to mount the PS+AS horizontally.** To conclude - the system is designed for horizontal mounting and this is the only supported mounting. If you choose to mount it vertically it is at your own risk. Operational temperature is key - you need to make sure it is far from max to decrease risk. Always try to mount the PS+AS horizontally. Negative effect of not managing operational temperature is not visible short term, but can and will effect the life time of the product. **Ambient temperatures for operating should be taken into consideration. For vertical installations, ambient temperature should not exceed 35 C (95 F) and the load on the power supply should be reduced from 30 watts to 25 watts. Convective Air Cooling is used in the modules anticipating the currents of warm air being allowed to escape the confines of the module casing to be replaced by cooler air from the bottom. Since warm air normally rises, this method usually requires venting at the top and bottom of the casing to be effective. This is why horizontal installations are preferred. **One PS can supply one or more units connected to the backplane, consisting of several terminal bases connected together. At the moment you cannot connect more than one AS to the backplane though, because the backplane provides a path for communication between the connected units, and two AS cannot communicate on the backplane. StruxureWare Building Operation allocates 32 slots for the I/O Bus including the Power Supply and Automation Server. All devices can be installed on one linear section of DIN rail or they can be installed on multiple parallel sections of DIN rail by using connector cables*. Be reminded an empty position (back plane without module) will still keep a position (slot). As a general rule, there are 10 I/O modules followed by a Power Supply, then 10 I/O modules followed by a Power Supply and 8 remaining slots for I/O modules.Please keep in mind the I/O Bus backplane requires a particular order. Position 1 is always the Power Supply, Position 2 is always for the Automation Server, and then up to 30 remaining I/O devices interlaced with additional Power Supply modules.

Issue How often does a Bacnet MSTP B3 controller broadcast alarms? How often is the Bacnet MSTP B3 polled for alarms? Environment Bacnet MSTP Andover Continuum B3 MSTP controller Cause Determining the process of MSTP B3 alarming Resolution The Bacnet B3 communicates on a token passing Bacnet MSTP protocol. When a B3 is configured for alarming and an alarm occurs, it will broadcast the alarm when the controller has the token.

Issue Failure when upreving a Controller to a new flash version. Error window pops up with the error message "This Uprev file does not match this type of controller.". SmartStruxure "Update Failure No b3 controller matches to update" Environment Continuum Controllers b3 Cause The Controller Model has been entered incorrectly or you are trying to load the wrong flash file into the controller, e.g., the Controller Model in the Device object has been incorrectly set to i2810 when the controller is actually an i2814. Resolution Confirm that the correct flash file for your controller model and the Controller Model field both conform to the actual model type of your Controller. In offline editing check that the database also contains the correct model type. For b3s (Notice the 4th digit) The 4.501064 firmware is for the –Vs The B3865B4.500076 is for the non –V

Issue Continuum 1.9x and above will not install correctly on a PC / Laptop that is on a domain, One example: When trying to run the Continuum Database Initialization program the following error message may pop up: You must have local NT administrative privileges to run this application. Environment Windows OS 7 8 10 Continuum 1.9x 2.x Inet SQL 2005 SQL 2008 SQL 2012 Cause Microsoft has introduced the use of a higher level of security in the install of their SQL database software SQL 2005 / SQL 2008 / SQL 2012. When you install Continuum you need to make sure you are logged onto the PC / Laptop as a local administrator, in the case of a lot of a corporate networks, you are most likely logged on as ether a restricted user or a domain administrator, these logons do not have the privileges you need to install an SQL database. Resolution Step by step guide to creating a local administrator user on your PC / Laptop Go to "Start" then "Control Panel" in Windows (Windows 7 and above, top right corner change "view by" to "small icons" this will show all icons) Go to "Administrative Tools" Go to "Computer Management" / "Local Users and Groups" In users, right click on the right panel and add new user Fill in the user name and password, un-tick user must change password Tick password never expires then ok it Now go back into control panel and click on "User Accounts" Click on the name you just created, this will open the properties screen (Windows 7 and above click on "Manage user accounts") Click on "Group Membership" then select others, and highlight administrators (Windows 7 and above double click on name you created, click "group membership" click "other" then in the drop down select "Administrator") Apply this and then ok it. Log off your normal account and log back on as the new user you have just created

Issue Certain values in the Xenta 102-AX can be put into override mode through the Plug-In: Airflow Auxiliary Temperatures 1 and 2 Universal Inputs 1, 2, 3, and 4 CO 2 Space Temp Damper Position Universal Outputs 1, 2, and 3 If the plug-in is not available, they can be overridden through the SNVT input nviRequest (type SNVT_obj_request). Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The plug-in might not be available for a multitude of reasons. For example, if the Xenta 102-AX is being integrated into a third party LON system, or no LNS management tool is being used. The values below can be used to implement an override through the SNVTs. Resolution Signals required to perform external control of inputs and outputs on the Xenta 102-AX: Set the override behavior value signal to 1 (OV_SPECIFIED) Set the desired value in the override value signal Send a SNVT to the signal Node_Object.nviRequest. It is a structured SNVT input with the following members: OBJECT_ID - refer to the list below for the appropriate object ID for each override OBJECT_REQUEST - set to value to 6 (RQ_OVERRIDE) to initiate the override, set to value 0 (RQ_NORMAL) to release the override. The tables below specify all necessary signals for each override. They are displayed in the following format: ID Title Overridden Value Desired Override Value Override Behavior   1 Airflow Reading (CFM, l/s) Airflow_Sense.nvoAirFlow.PV Airflow_Sense.nvoAirFlow.SCPTovrValue.PV Airflow_Sense.SCPTovrBehave.PV   2 Universal Input 1 (%) UnivIn1_Sense.nvoUnvInput1.PV UnivIn1_Sense.nvoUnvInput1.SCPTovrValue.PV UnivIn1_Sense.SCPTovrBehave.PV   2 Duct Inlet Temperature UI1 (°F, °C) UnivIn1_Sense.nvoAuxTemp1.PV UnivIn1_Sense.UCPTovrValueTemp.PV UnivIn1_Sense.SCPTovrBehave.PV   3 Universal Input 2 (%) UnivIn2_Sense.nvoUnvInput2.PV UnivIn2_Sense.nvoUnvInput2.SCPTovrValue.PV UnivIn2_Sense.SCPTovrBehave.PV   4 Universal Input 3 (%) UnivIn3_Sense.nvoUnvInput3.PV UnivIn3_Sense.nvoUnvInput3.SCPTovrValue.PV UnivIn3_Sense.SCPTovrBehave.PV   4 CO2 Reading UI3 (ppm) UnivIn3_Sense.nvoCO2sensor.PV UnivIn3_Sense.UCPTovrValueCO2.PV UnivIn3_Sense.SCPTovrBehave.PV   4 Outside Air Temperature UI3 (°F, °C) UnivIn3_Sense.nvoAuxTemp2.PV UnivIn3_Sense.UCPTovrValueTemp.PV UnivIn3_Sense.SCPTovrBehave.PV   5 Universal Input 4 (%) UnivIn4_Sense.nvoUnvInput4.PV UnivIn4_Sense.nvoUnvInput4.SCPTovrValue.PV UnivIn4_Sense.SCPTovrBehave.PV   5 Setpoint Offset UI4 (°F, °C) UnivIn4_Sense.nvoSetPtOffset.PV UnivIn4_Sense.UCPTovrValueTemp.PV UnivIn4_Sense.SCPTovrBehave.PV   6 Space Temperature (°F, °C) VAV_Controller.nvoSpaceTemp.PV VAV_Controller.nviSpaceTemp.SCPTovrValue.PV VAV_Controller.SCPTovrBehave.PV   7 Damper Actuator (%) Damper_Actuator.nviRelStPt.PV Damper_Actuator.nvoActualValue.SCPTovrValue.PV Damper_Actuator.SCPTovrBehave.PV   8 Universal Output 1 (%) UnivOut1_Object.nviUnvOutput1.PV UnivOut1_Object.nviUnvOutput1.SCPTovrValue.PV UnivOut1_Object.SCPTovrBehave.PV   9 Universal Output 2 (%) UnivOut2_Object.nviUnvOutput2.PV UnivOut2_Object.nviUnvOutput2.SCPTovrValue.PV UnivOut2_Object.SCPTovrBehave.PV   10 Universal Output 3 (%) UnivOut3_Object.nviUnvOutput3.PV UnivOut3_Object.nviUnvOutput3.SCPTovrValue.PV UnivOut3_Object.SCPTovrBehave.PV

Issue What BACnet services and BACnet object types are supported in the AS and ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Automation Server StruxureWare Building Operation Enterprise Server BACnet IP BACnet MSTP Cause PIC statement for supported services and object types in StruxureWare Building Operation. Resolution Page 5 of the AS BACnet PIC shows the columns of the different types of BACnet devices. Whether it is a B-OWS or a B-BC etc… the x's in the columns show the required services for each particular device according to the BACnet Standard. The last green column in the PIC, show the Product Conformance (AS) and what services the AS supports. For instance COV is not a required service, but a optional one and is selected in the last column. Below are links to the AS and ES BACnet PIC. AS PIC statement link ES PIC statement link

Issue Handle id limits on Continuum controllers. Environment All master level controllers (bCX, CX) All b3 controllers All i2 controllers Cause Handle id limits on Continuum controllers. Resolution Field controllers have a total limit of 255 objects, approximately 50 of them are reserved for system variables and other system objects, leaving approximately 200 that can be user created in the field controller. All IP level devices in the Continuum line follow the handle specifications of the Continuum protocol. This includes the BACnet devices such as the bCX-4040. Handle numbers for most object types (including all BACnet types) are in the range 7,000 to 65,535. That allows for 58,536 objects, which is more than the memory can hold. Continuum style alarms (not BACnet alarms) have handles in the range 1,000 to 4,999. Controller will run out of memory before it runs out of handles.

Issue Some b3 system variables have been renamed in StruxureWare as have some of the special labels. Environment StruxureWare WorkStation b3 BACnet devices Cause System design Resolution When programming the b3 devices care should be taken to use the StruxureWare Building Operation name of system variables and special labels to avoid compiler errors. All system variables that in Continuum have the prefix ACC in the name have been re-named to remove the prefix so that ACCStatusBackup is StatusBackup and ACCStatusFlash is StatusFlash. Also all value labels that in Continuum have the prefix ACC have been re-named to remove the prefix so that ACCBackupNeeded is BackupNeeded and ACCBackupNow is BackupNow.

Issue What are the pull up resistors on the universal inputs used for? Environment IOU modules i2 devices b3 devices Cause Information on the pull up resistors selection switch. Resolution The pull up resistors on the inputs are used to configure the input impedance, for example on the 810 series i2/b3 field controllers the input impedance can be 30.1K ohms referenced to 10.000 V or 10 M ohms referenced to ground with the input reference resistor switch set to OUT Pull up resistors are configured via the DIP switch located in the general area of the inputs, each small switch corresponds to the input with the same number. If an input is either a thermistor or a digital input, switch its input reference resistor switch to IN. (switch ON) If you require that the input be high impedance (10 M ohms), set its input reference resistor switch to OUT. (switch OFF)

Issue Average space temperature on TAC Xenta 120 devices. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause TAC Xenta 121 is able to average space temperatures from multiple sensors. For example, it could average two room units, or one room unit and one Lon sensor. It is possible to average up to three different Lon sensors. Resolution Bind a valid temperature SNVT value to the input nviSpaceTemp. The TAC Xenta 120 device will calculate the average between the bound input and the physical sensor.

Issue Function Blocks as object controller Environment StruxureWare Building Operation FB Program at site Cause When commissioning the local node with a LNS tools (NL220), one cannot see the functional blocks as object controller in the LNS tool, but rather have all the SNVT in the static node. Is it normal? The problem is, if one has a lot of SNVT, it is not clear. Resolution Functional blocks created do not have a functional block index to be able to present them correctly. All Functional blocks have same index causing the presentation issue mentioned above.

Issue Binding SNVT to AS-L  Environment StruxureWare Building Operation AS-L site Cause About the SNVT, when one binds a SNVT from the AS-L to the LNS network (nvo in AS-L), the AS-L doesn't propagate the value on the LON network. But, when binding a SNVT from the LNS to AS-L (nvi in AS-L) and when one changes the value, the AS-L receives it well and then can use the value in AS-L. Resolution The problem is that we “own the world” that is StruxureWare Building Operation owns the AS and Local Node, so we don’t know that we need to propagate something to someone. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems this is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue AS-L Loses LON Configuration Environment StruxureWare Building Operation LON environment Cause After commissioning the local node with a LNS tool and if one switches off the power supply of the AS-L, the local node loses the LON configuration and it return in factory configuration 'Domain 18 Subnet 1 node 254'. Now you can just change the domain.  Resolution It seems the local node updates the domain if the domain is updated from LNS. So if you do a Local Node commission than the LNS will not work and if you commission it from LNS local node is not going to update the domain. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems it is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue Need to be able to read and write to a point. Environment StruxureWare Building Operation Workstation ES AS Cause Need to be able to read and write to a point. Resolution Declare the point as Output and bind it. Outputs can be read and written.

Issue Updating firmware from StruxureWare Building Operation and the still be usable with other BMS such as Continuum, I/A Series, I/NET, Sigma, and Vista Environment Site with more than one Building Management System  Cause Implications of updating firmware on a controller from the StruxureWare Building Operation side and still compatible with existing Resolution For the controllers available on the StruxureWare Building Operation network that have been configured, take precaution when updating the firmware and still expect compatibility with other systems. For example, at a Continuum site, with a b3 and the option to update of firmware from StruxureWare Building Operation, there are a couple of things to keep in mind. When selecting the b3, and the Update Firmware, it will ask you for the *.udp file. This can be downloaded from the extranet. The thing to keep in mind here is if you are using this controller in conjunction with Continuum, then pay particular attention to the Compatibility Matrix and the firmware which is compatible with the version of Continuum you are running. Updating a firmware that is not in line with the version of Continuum will create problems for the site. So when selecting the firmware *.udp, be sure of which firmware file you are selecting. The operating system in the b3 controller is no different between StruxureWare Building Operation and Continuum. The PE code may be different though, so he should be able to learn these controllers into Continuum as long as they have their user memory cleared out.  

Issue Audible alarms and the DefaultAlarmView vs. new workspace with new alarmview Environment StruxureWare Building Operation site Cause Audible alarms and alarmview, Using the predefined alarmview we get the audible alert for this alarm. Create a new workspace with an alarmpane with a self defined alarmview we do not get the audible alert. Steps to reproduce problem: I created a digital value and one alarm connected with this digital value. I the settings of this alarm I checked the box audible. Then created a new alarmview without any filter. I created a new workspace (named ws01) with a system tree and one alarmpane. For the alarmpane I selected my created alarmview. Selected the workspace Engineering and triggered the alarm. Expected result: Alarm is in the alarmview Audible alarm This works Then logout of the workstation and login again. Now using the workspace ws01: trigger the alarm Expected: Alarm is in the alarmview Audible alarm Actual result: Alarm is in the alarmview No audible alarm.   Resolution Audible alert, works only in the DefaultAlarmView. Expected fix to be in 1.3 release of StruxureWare Building Operation. Work-around: None known

Issue WorkPlace Tech version 5.7.2 menus do not appear when the StruxureWare Building Operation workstation is installed on the same computer. Environment Computer with both WorkPlace Tech version 5.7.2 and StruxureWare Building Operation workstation installed. Cause WorkPlace Tech 5.8.2 and later support coexistence with SmartStruxure. Resolution Install WorkPlace Tech 5.8.2 or later. The proper procedure for performing this upgrade is: Uninstall StruxureWare Building Operation Install the latest version of the WorkPlace Tech Tool software. Reinstall Building Operation.

Issue Can we integrate 3rd party LON devices Environment StruxureWare Building Operation AS or Enterprise Server Cause Integrating third part LON devices allows the system to take full advantage of the open protocol. Resolution We currently support 3rd party Lon devices in Version 1.0 and 1.1, but some large devices are too big to be configured in quantities according to specifications. No major change regarding this is scheduled until earliest 1.4. In 1.3 we will change the numbers that we support to configure but this will mainly be runtime improvements. Some devices can only be configured with Lonmaker which is an extra step during the engineering process.