Building Automation Knowledge Base

Issue Where is the 0-10 volt control signal connected, on a Forta actuator? Environment Forta M400 Actuator Wiring Connections Cause The customer was uncertain how to connect the M400 actuator. Resolution The general configuration and connection details are the same for all of the Forta range of actuators. All of the range can accept a 0-10 volt dc input or increase/decrease signals. Terminal Function Designation G                  24 V AC Supply G0                24 V AC return X1                 Input MX                Input, neutral VH                Increase VC                Decrease G1                16 V DC Supply for RC Y                   0–100 % Feedback signal The 0-10 volt control signal is connected to (X1) and the associate 0 volt is connected to (MX). If there is not an associated 0 volt available then (MX) should be connected to the (G0) terminal. To download the Forta Handbook please click HERE.

Issue When swiping card, the access is denied. The message shown in AMT is "Bad Card Read". Environment I/NET Cause There may be two causes for this message: The tenant code isn't correct when using Wiegand 26 format in the door parameter. The digit of card number exceeds the setting in the setting of card reader type. For example, the card format is Wiegand 35, but in the door parameter, the card reader length is set to 36 digits. Resolution For cause 1, enter the correct tenant code in the Tenant Editor. For cause 2, set the correct card reader type and digit.

Issue Before installing Access Expert on premise server software, the Mongo DB must be installed and the Mongo service started, this requires creation and editing of a configuration file where the data and log directories are specified. There have been many cases of YAML errors seen during V3 on premise installation when attempting to start the Mongo service. Product Line EcoStruxure Access Expert Environment V3 Mongo DB Cause The YAML parser that reads the "mongod.cfg" file is very sensitive to the format of the configuration file including some very strict rules about spaces, double quotes and back slashes. When editing the file, it helps to setup the text editor to display ALL characters which will show any hidden characters that might be causing a parsing error. Ex. In Notepad++: Select View>Show Symbol> Show All Characters Resolution Space is needed between key and value pair. Enclose paths in double quotes. Double back slash required in Windows systems.

Issue Not possible to get a Xenta Server / 911 online in TAC Vista. It is possible to ping it and connect to it via a Web browser using ports 443, 80, and Port 1068 is open, but it is not possible to get online in Vista. Product Line TAC Vista Server Environment TAC Vista TAC Xenta 911 TAC Xenta Server Cause The problem, in this case, was that another Vista server was connected to the Xenta Server / 911.  This could have been from a technician or the customer who started Vista with this database loaded and had the device online in their Database. The Xenta Server / 911 will only communicate with one Vista Server at a time and will close the connection if another Vista tries to communicate with it.    Using Wireshark it is possible to monitor this scenario as shown below:  Packet number 57439: Vista is trying to establish communication with the Xenta Server or 911( sending an SYN). Packet number 57440: The Xenta sends an acknowledgment on the SYN from Vista, but with the window size set to zero, this is because the Xenta can't buffer information as a computer does. Packet number 57441: Vista  sends an acknowledgment on the message from the Xenta Packet number 57448: The Xenta sets the correct window size. Packet number 57449: Vista starts to communicate Packet number 57452: The Xenta closes the communication to the Vista server  Resolution Ensure only one Vista server is started when the Xenta server / 911 is included in the database.

Issue The need to verify the proper wire positions on a Xenta Server device Environment Vista XBuilder Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Installing a Xenta Server device on a network Resolution Table 2.1: Connections on the Xenta device Position Description 1-2 Power supply. Minimum cross-sectional area 0.75 mm2 (AWG-19). 1 (G) - 24 V AC (or DC+) 2 (G0) - Ground 3-4 LonWorks TP/FT-10 connection 3 (C1) 4 (C2) 5-8 Internal port A RS-485 A connection 5 (RX/TX+) 6 (RX/TX-) 7 (RX+) 8 (RX-) Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 9 Ground 9 (G0) 10 Fail-safe Note Jumping these pins together while cycling power will flash the device and load the minimum amount of drivers necessary for communication. If an IP address has already been assigned fail-safe will NOT remove it. 11-15 Unused 16-17 Ground 16 (G0) 17 (G0) 18 Unused 19-20 Internal port C RS-485 C (SDLC) connection 19 (RX/TX+) 20 (RX/TX-) 21 Internal port A RS-232 A connection. Note that the interface RS-232 A (position 21) and interface RS-485 A (position 5-8) are internally connected to port A on the processor. Only one should be connected. 22 Internal port B RS-232 B console connection 23 Ethernet 10Base-T connection 24 Service pin Caution G0 equals GROUND. Only G0 may be connected to protective ground.

Issue The limits on how many AI/AO/BI/BO/RI/RO, Function Block number, Constant number, public signal number...etc.. one can create in one Functional Block Application? Environment StruxureWare Building Operation site with Functional Block Application Cause What are the limits on how many AI/AO/BI/BO/RI/RO, Function Block number, Constant number, public signal number...etc.. one can create in one Functional Block Application? Resolution There are no limits about how many blocks that could be created, but the Function Block parser has a memory limit. When this limit is exceeded an error text is prompted to the user. There is no way to tell if a site is getting close to that limit.  

Issue The default LED Output names for Reader Expanders (eg. RD Red R1) do not always match the colour of the LEDs on the card reader Product Line EcoStruxure Security Expert Environment Security Expert Controller Security Expert Reader (New version only) Cause The default LED output names/labels don't accurately describe their function. Resolution The "RD Green R1/R2" Outputs represent the reader's LED colour in its "active" state. By default: These outputs are not inverted; (in Programming|Outputs|Options General section, "Invert output" checkbox) When the output is activated, the reader's LED is green; When the output is deactivated, the reader's LED returns to blue; The "RD Red R1/R2" Outputs represent the reader's LED colour in its "resting" state. By default: These outputs are inverted When the output is activated, the reader's LED colour is also green When the output is deactivated, the reader's LED returns to blue To have the Red LED in the active state, you must add the following to the output's command console (found in Programming|Outputs|General Commands section): LEDColour = 1, where 1 is Red.   Here is a list of available colours: 1= Red 2= Amber 3= Orange 4= Yellow 5= Lime 6= Green 7= Mint 8= Turquoise Note: Please refer to AN 270 to identify new from old versions of the reader hardware  

Issue Pins 4 through 7 across the top of the Automation Server are labeled as "Operator Panel" although there is not an Operator Panel part available. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Cause There is no explanation of what the AS Operator Panel contacts are for? On front of AS:  Operator Panel Terminals Term 4 RET Internally connected to ground Term 5 10V 10 VDC max. 120 mA Term 6 Tx/Rx+ RS-485 communication Term 7 Tx/Rx- RS-485 communication Resolution At one time there were plans to create an Operator Panel so terminals were reserved on the Automation Server for local OP connection, however, these plans were not implemented. The next generation Automation Server Premium (AS-P) does not have the Operator Panel label, and today most operators use Webstation or Workstation.

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.  

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM800 Power meters. Cause How can Modbus RTU X-Driver programs be written to poll for the data in a 3rd party Modbus device? Resolution The attached example show how to use the modbus RTU x-driver to read 4 16 bit data values from the PM800 meter, then using plain english to get the values to output to a single infinity numeric the total Power reading in kWH/mWH/gWH depending on the scaling factor of the meter. Create 4 Numerics reading the four registers that are used to store the data. Registers, 1716, 1717, 1718, 1719 are used in the PM800 Then create another numeric and via PE do the following calculation Energy Calc = (Register 4 x 1000000000000) + (Register 3 x 100000000) + (Register 2 x 10000) + Register 1. This will give you the value in wH. Then use a multiplier to give you the final reading in kWH etc.

Issue What is the maximum allowable distance between two Lon devices on a lon network? Environment TAC Vista 5.1.X  Lon devices such as Xenta 2/3/400 FTT10-A either free or bus topology Cause The physical layout of a building may require nodes to be installed far apart. Resolution The maximum distance between two devices (nodes) is 320m. No node may be more than 320m worth of cable from the bus termination (if bus topology is used). More information can be found in the Lonworks Installation Handbook, chapter 5 "Physical Network Structuring".

Issue N4 software installation stops because; azul-zre-compact3-qnx7-arm tridium-qnx7-n4-titan-am335x software is missing Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause A valid license including the features that meet the dependencies is not installed. Resolution Install a valid license containing the jre8J8000Azul, jre8Qnz7Zulu and qnx7, jreQnx7Zulu features before attempting to commission the Jace 8000

Issue Panel layout. Environment  ERG-UNIV-ENC-1 ERG-UNIV-ENC-2 Cause Need to determine panel layout for a project using the universal enclosures. Resolution From the data sheet... Medium Enclosure: Andover Continuum Power Supply and NetController, and up to two I/O modules or up to six I/O modules or CX 9702 SiteController.   Small Enclosure: Up to three I/O modules or CX 9702 SiteController or NetController (without a Power Supply) or VS-8-4 Video Switch Module. Both units are designed to hold two standard 12 VDC 7AH lead acid batteries (not provided). See the full data sheet here.

Issue LonWorks Device is Offline in Vista, but Online in LonMaker. For Xenta Programmable devices refer to Xenta Programmable Device is Offline in Vista but Online in LonMaker. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation LonWorks Device Cause If the Vista database has some LonWorks devices that are not communicating, one cause could be due to changes in the system such as moving controllers to a new channel for example. Updating the Vista database with the system plug-in might not fully overwrite all the node properties causing the device not to communicate in Vista Workstation even though it is communicating in the LNS database. Resolution Delete the LonWorks device from the TAC Network in the System plug-in. "Update Vista Database" in the System plug-in to remove the device or devices from Vista Workstation. "Update TAC Network" to add the devices back to the TAC Network. "Update Vista Database" again to add the devices back to the Vista database.

Issue Licenses for MS SQL Server 2008 are becoming difficult to source, is MS SQL Server 2012 going to be supported? Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Cause As retailers deplete their old stock, it will become harder and harder to obtain licensing for MS SQL Server 2008 which is the most recent version of MS SQL Server that Continuum v1.94 supports. Purchasing SQL Server 2012 licenses to downgrade deployment rights does not seem to be an option with current Microsoft licensing as this option only applies to volume licensing and not retail license packages. (Refer to page 16 of the Licensing Reference Guide from Microsoft here.) Resolution Continuum v1.94 was not qualified with MS SQL Server 2012 at the time of release, this has since been tested and qualified with Service Pack 1 for Continuum v1.94. Please see the Continuum Compatibility Matrix in Software and Firmware compatibility matrix for older versions of the traditional product lines for details of supported environments. To use Microsoft SQL Server 2012 you will need to upgrade your installation to Continuum v1.94 SP1 or higher. You will be able to use MS downgrade rights to downgrade an SQL 2014 license so that SQL 2012 can be installed. See references from Microsoft below. http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx http://www.microsoft.com/licensing/about-licensing/sql2014.aspx For sites using Continuum v1.94 or older that do not wish to upgrade, downgrade deployment rights can be used with volume licenses of MS SQL Server 2012 to deploy an older version of SQL Server (say MS SQL Server 2008 R2 that is currently qualified with the version of Continuum you have). Note: Continuum v1.94 SP1 has been qualified with MS SQL 2012 (SP1) but has not been tested with SQL 2014.

Issue SE7000/SE8000 controllers are randomly going offline or are undiscoverable on BACnet network. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 SSL SE8000 Cause Improper terminations of the BACnet MS/TP communication cable.   Resolution The REF (reference) Terminal is a BACnet Reference which is a voltage reference required by BACnet testing lab (BTL) and it is rarely used in the industry. If not used as a reference, The Ref terminal should be left empty. It is not a terminal to land a shield nor a ground.    At each thermostat (Cable Junction) : Connect the (+) and the (-) wires Twist the shields together Tape around the cable to prevent short-circuit. Ground the shield at one end only (usually on the BAS side) and leave the REF terminal empty Ensure that the shield wire is not connected to the REF (Reference) terminal.

Issue MP/RP-x device is not pushing firmware down to Room Units (RU) when sensors are attached to the sensor bus. Disconnecting and re-connecting the RU does not help Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause The MP-X controller's file system has been re-initialized and the Room Units firmware files deleted. One case under which this will happen is when the MP/RP-X is factory reset.   The Device Report can be used to confirm whether the files exist in the device or not.   If Room Unit files are not shown in the report then no download to the RU will take place. Resolution Perform an upgrade on the MP/RP-X device, upgrading the device to the same version that is already running will resolve the issue.

Issue Need a currently available sensor that is compatible with the MicroFlo II controller. Environment MicroFlo II VAV controller Cause Need a sensor for the obsolete MicroFlo II. Resolution See the Spec Data sheet (F-24314-5, page 3) for a list of compatible sensors that are currently available. NOTE: The MicroFlo II controller is OBSOLETE.

Issue How to use values form a modbus device in a Xenta 7xx menta program Environment TAC Xenta 731, TAC Xenta 721, TAC Xenta 711, TAC Xenta 701 TAC Xbuilder Cause Need to bring in values from a modbus device to a Menta application in the Xenta server. Resolution Create a PVR (or PVB,PVI depending of datatype of the signal you are bringing is) and make it public in the Menta application. Create a connection object in Xbuilder, connect the "from" to the modbus signal, connect the "to" to the PVR block. Now the value from the modbus device will be represented in the Menta application by the PVR block.

Issue What configuration is required for a Multical BACnet heat meter Environment Schneider Electric (Kamstrup) heat meter connected to a Continuum or SmartStruxure system on MS/TP. Multical 61/62/601/602/801 Cause Setup information required Resolution With the BACnet interface card fitted in the Multical meter it is a native BACnet MS/TP device. Connect it to the AS or bCX1 depending on your system and Learn/ find BACnet devices. It should appear online and allow the objects to be uploaded. A typical unit like the Multical 602 will contain 12 Analog Inputs for all of the information from the meter. The Meter will operate at 9600, 19200, 38400, 57600 and 76800 Baud rates and autobaud to the connected system. For the Datasheet  Click Here. For the BACnet PICs statement Click Here. For help with Heat meter selection see the online selection tool: Online Heat Meter Selection Tool - PA-00216