Building Automation Knowledge Base

Issue How to configure Xenta 913 to talk to C-Bus devices Environment Xenta 913 C-Bus Cause C-Bus is a public protocol which is commonly used in lighting control. Xenta 913 can be configured to talk to C-Bus devices with proper settings. Resolution A. Device Preparation C-bus 5500PC (PC Interface) RS-232 port        Xenta 913 RS-232A port NOTE: Communication is between Xenta913’s RS-232A port (NOT RS-485A port) and 5500PC’s RS-232 port (NOT C-Bus port).   Communication Cable Xenta913   C-Bus 5500PC, PC Interface RS-232A    <---------------------> RS-232 3(TX) <---------------------> 5(RX) 4(RX) <---------------------> 6(TX) 5(COM) <---------------------> 4(COM) Above number are RJ45 jack (as shown below) pin numbers.   B. Configuration Configure C-Bus device with CBusToolkit. Make sure to write down the Application number and the device’s Group number which Xenta 913 needs to communicate with.   Configure Xenta 913 in Xbuilder. Set Application number to 38 (38 is the HEX value of 56).   In DeviceEditor   The Group number (Hex value) needs to be inputted. Such as ‘01’ in the figure below. Same Group number can be inputted in different lines; however the ‘IO’ type should not be the same, such as ‘R’ and ‘W’ in below figure. ON Only and OFF Only types are NOT applicable to read-only values.   C. Verification In Xbuilder, drag all C-Bus points onto Value page. Download Xbuilder project into Xenta 913. Login Xenta 913 webpage and check if all point are correct and can be modified.   D. Additional Information Since CBusToolkit communicates with 5500PC by 5500PC’s RS-232 port, and Xenta 913 also communicates with 5500PC by 5500PC’s RS-232 port. Therefore, Only ONE device can be connected to 5500PC’s RS-232 port for CBusToolkit and Xenta 913.

Issue Configuring and monitoring the Xenta 102-AX is traditionally done through the LNS Xenta 102-AX Plug-In, but how can it be done in a Vista Classic Network where no LNS plug-ins are available? Environment Vista 5 Classic Network TGML Xenta 102-AX Vista Workstation ONLY -- This plug-in is not compatible with Webstation or XBuilder graphics at this time. Cause LNS Plug-ins are not available in a Vista Classic Network. Resolution All of the values that are written to by the LNS Plug-In are public and available through the Vista front end. So if only one or two signals need to be set for each box, this can be accomplished by locating them in the Vista network and writing the desired values to them.  This does require some fairly intimate knowledge of the Xenta 102-AX and Plug-In. The alternative is: Download the Xenta 102-AX TGML Plug-in by clicking the image below.  Unzip the contents to the hard drive. Open the TGML file. Select File > Save As > Vista Database Object Navigate to the first Xenta 102-AX in the network. Drill down into the 102-AX on the same level with Node_Object and VAV_Controller modules. Give the plug-in graphic a name and save. Right click on the Graphic object in Vista Workstation and select Copy Navigate to the next Xenta 102-AX and select Paste Shortcut. Since all bindings are automatically populated with relative bindings, copying and pasting shortcuts will automatically display data for the associated Xenta 102-AX. Repeat Step 8 for all Xenta 102-AXs in the network.

Issue How to use multiple monitors when working in Building Operation WorkStation. Product Line EcoStruxure Building Operation Environment Multiple Monitors Building Operation WorkStation Cause Need to understand how to utilize multiple monitors with Building Operation WorkStation available as an option from version 1.4.1 and above. Resolution Building Operation Workstation provides the ability to place any pane in WorkStation on a separate monitor including the alarm, watch, and event windows. This can be a very productive feature for a building front-end computer or even in the engineering stages of the system. Versions 1.4.1 and above The multi-monitor display support in WorkStation includes the ability to save and reset workspace layouts. Individual users at a given WorkStation can modify the workspace layout and save it such that whenever that user logs in using that PC the workspace will revert to their modified layout. Included in the modified layout is the ability to move panes to a second monitor and have those panes positioned in the same way whenever that user logs in with that PC. The user can revert to the default layout at any time. How to move WorkStation panes to a second monitor Click, hold and drag the title bar (1) of any pane in WorkStation that is to be moved to another monitor. The pane will appear as a purple shadow (2).  Drag the pane to another monitor, release and re-size as necessary (3).    How to save the workspace layout for the current user At the top of the WorkStation window, click on the View menu (1) and select "Save workspace layout" (2).  When the same user logs out and then logs back in again, the layout will remain the same. To return the layout to the default, go to the View menu and select "Reset workspace layout". Note: When working with a two-monitor layout using a laptop on a docking station, if the laptop is undocked it will no longer be possible to see the panes that were moved to the second monitor.  To correct this go to the View menu and select "Reset workspace layout".     Versions 1.4.0 and prior It is possible to use WorkStation and WebStation on multiple monitors in prior releases: Launch multiple instances of the clients and run them on different monitors. In WorkStation, “Tear off” view windows and position on different monitors. Manual positioning of windows is needed.  To get more automatic behavior at start-up or logon, it is better to run with multiple computers with separate displays or see if a 3rd party window positioning utility can help.

Issue Vista locks up randomly and displays application crashes. Investigating the Windows Event log shows the following errors pointing to tacldv32.dll. For more information on Windows Event Log, see Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Faulting application tacos.exe, version 0.1.0.0, faulting module tacldv32.dll, version 1.0.0.1, fault address 0x00007310 Product Line TAC Vista Environment Vista Server LNS Communication Port Large LNS network, or many smaller LNS networks Orion Stack Cause The DLL file, tacldv32.dll, is responsible for managing communications through an LNS communication port. If that is being overwhelmed with information from too many devices on the port, this DLL will crash. If the number of networks is only one and the database size is reasonable then the problem can be caused by a corrupted and non functioning LNS database.See Also Echelon LNS Utilities LNS Database Validator. Resolution If the number of networks is high then LNS communication must be managed by an Orion Stack, or NIC-852. This does not utilize tacldv32.dll and will stop the application crashes. If the number of networks is low, but the size of the networks is quite large, then it is also advisable to allow the Orion Stack to manage communication and will prevent the application crashes. If the number of networks is low and they are not very sizeable, then ensure that LNS database is working properly independently of Vista Server. If it has problems, investigate the LNS problems further, looking for any errors that can be searched on other articles. *Note that if you receive the tacldv32.dll error and are currently using an Orion Stack or NIC-852. There is a problem with the Orion Stack or NIC-852 installation or configuration. Hovering the mouse over the Communication Port objects in the TAC Vista Workstation should produce a pop-up window stating "Loytec Port". If it says "LNS Port", there will still be a need for using tacldv32.dll resource.

Issue During startup of the Lon FlowBalance software, an error is displayed indicating that the program "cosmo.exe" failed to register Product Line TAC IA Series Environment MNL-FLOW-BAL 3.0 - MicroNet Software Microsoft Vista, Windows 7, and Windows 10 (64-bit installations) Cause The software installer installed the software into the C:\Program Files (x86) folder on the Windows system drive. When the software is started up, it needs to initialize some internal driver and data modules. These modules are expected to be in the C:\Program Files\TAC folder, however, that folder was not created during the installation of the software. The LON FlowBalance version 3 software is not supported on 64-bit versions of Windows because fully-supported Echelon (LON interface) drivers are not yet available. Resolution Reinstall the LON FlowBalance software on a computer or virtual machine running Windows XP, Windows Vista (32-bit) or Windows 7 /10 (32-bit).

Issue Ordering, installing, wiring of CLX LAN Expansion board. Product Line TAC INET Environment I/SITE 7798 CLX Cause There is not any CLX-specific installation guides or manuals. This article is intended to give some basic information about the expansion board and its use. Resolution Part number: CLX Part name: LAN Expansion Option for RS-485 Part description: I/SITE Expansion Board - adds controller LAN communications to network other controllers to 7728 & 7798 - RS-485 CE/EMC Compliant Comments: Plugs on to 7798 base unit, RS-485: 19,200 or 9600 baud, SDLC, token-passing. Wiring: Terminals 1 and 2 on the CLX are Controller LAN +,- respectively. For more information on installing the CLX expansion, see CLX Expansion Card for 7798B .

Issue Would like to change the default Event Description displayed under Monitoring | Status Page View.  Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Would like to customize Event messages by adding or removing text from the Description field for specific Events. Resolution Unfortunately we are unable to modify any Event Description. Changing, or adding to, the event text is not an option. A couple of alternatives could be: Add a descriptive Instruction to an Alarm that you are filtering (with an Alarm Filter) for raw data events and then monitoring the Alarms feed, instead of the Events feed, for those messages. Setup an "Action" to single out and email those specific Events that you want to see.

Issue Xenta 700 System Report shows "Menta: IO error (Error#:62464) Environment Xenta 700, 701, 711, 721, 731 Cause Some of the causes could be following: Might be configured to use wrong I/O Modules Wrong Neuron ID configured Menta program issues Resolution To resolve this error, check the following: Upgrade Xenta Firmware with Latest Version from the Exchange Extranet. Ensure correct I/O modules are configured. Ensure all the controllers and I/O modules are online.

Issue How to generate an invalid attempt alarm. Product Line Security Expert Environment Security Expert Cause It is not clear how an alarm for an invalid attempt at a Door is configured. Resolution The easiest way to setup an alarm to trigger when an invalid attempt is made at a reader is to trigger an Alarm off of the required Event. An example would be: Under Events create a new Event Filter, go to Event Types tab, un-tick "Include all event types" and add the events you want to monitor. In this case "User Door Group Not Valid At Door Using Access Level" should suffice as a start. To ensure you have the correct events you can create the event condition and confirm exactly what the event recorded is. Under Events create a new Alarm and set the Event Filter to the Event filter you created in step 1. Under Monitoring setup a Status Page that includes All Alarms (or alternatively is filtered for the specific alarms you want to see).

Issue Global and indirect points are very useful and are usually a mandatory part of most application programs. It is seen that in the event of a LAN failure or any failure of the indirect point being updated, the indirect point will be flagged as "Old Data." When this occurs any process using the indirect point as a variable, say, calculation extension, event extension will freeze at the last status/value before the old data on the indirect point was detected. Even though other parameters are still valid, the calculation and the event extensions will remain frozen, and some occasion remain in this state even when the old data is cleared from the source. Any subsequent process that uses the calculation or event definition will also be frozen. Any PID DDC Modules, Floating DDC Modules and 2 Position DDC Modules that uses the indirect point that has been flagged as "old data" will force those DDC modules to "Fail Safe" mode. Product Line TAC INET Environment ALL I/NET Software and controller LAN (CLAN) based controllers Cause LAN failure or any failure of the indirect point being updated. Resolution There are various tools available within I/NET to filter "old data" from subsequent control processes.  These include: Filtering by Calculation AVG operator function (including point types AI, DI and DO) Filtering by Direct Digital Control (DDC) Modules using either the Relay or HiLo modules Click Here to download a document which details these methods. For further details and recommendations when using Global and Indirect points, refer to the following I/NET Global and Indirect Points Overview and Recommendations.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. License not found Product Line EcoStruxure Security Expert Environment Security Expert Server Cause This error generally occurs when trying to license Security Expert from a Client machine and not the  Server machine where the Security Expert services are installed. Resolution Go to the Security Expert Server and license/update the license from that machine using the Security Expert client.

Issue Difference found between 2 technical documents regarding the Universal Inputs of the b3810 and b3814 controllers. In the Controller Data Sheet the Universal Inputs are indicated 0-10VDC, 12 bit.  In the Family Controllers Brochure it's indicated Universal Inputs 0-5V, 10bit.  Which document is correct?   Environment BACnet b3810 and b3814 controllers Cause An older revision of the Family Controllers Brochure contains inaccurate / outdated information. Resolution The Universal Inputs for the b3810 and b3814 controllers are 12 bit,  0-10VDC.  The next revision of the BACnet Family of Controllers document will contain the correct voltage. Controllers available with 12 bit A/D Converters 0-10VDC are: i2/b3920 i2/b3810 i2/b3814 Other i2/b3 controller inputs have 10 bit A/D converters.

Issue Configuring the Xenta 102-AX to accept a 4-20 mA CO2 sensor input on Universal Input 3.  A negative value is required on the CO2 offset value, but it is not possible to edit the scaling of the input in StruxureWare. Product Line EcoStruxure Building Operation Environment Xenta 102-AX 4-20 mA output CO2 sensor SmartStruxure Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input.  The best option is to always buy a CO2 sensor that is compatible.  However, if 4-20 mA CO2 sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20 mA CO2 sensor with a 0-2000 ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to None Wire the CO2 sensor and a 250Ω resistor across U3 and M.  This converts the 4-20 mA signal to 1-5V. In SBO WorkStation, create a Function Block program to convert the 0 to 100 % signal to ppm.  (You can import the Function Block program here). Edit Bindings on the CO2 Curve program and bind the nvoUnvInput3/Value.lev_percent from the UnivIn3Sense folder of the 102-AX to the CO2_RAW of the CO2 Curve program. Bind the CO2 from the CO2 Curve program to nviCO2/Value.ppm that is in the UnivIn3Sense folder of the 102-AX. At this point, if you have values entered in for the Airflow Reset or CO2 Low Limit and CO2 High Limit then the Airflow reset will be active and operational. Also, if you have multiple CO2 sensors on multiple 102-AXs then you don't have to have a CO2 Curve Function Block program for each one.  You can just edit the existing CO2 Curve program and copy/paste the exiting Function Block program multiple times in the same Function Block program.  You would just need to rename each public point with a unique name.  Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid).

Issue bCX shows BACnet Network Number zero in the Continuum Explorer Device Editor even though the BACnet Network Id - Comm2 shows value such as 2765 in the bCX configuration web page. Product Line Andover Continuum Environment CyberStation bCX4040 bCX4000 b4920 b3 devices Cause bCX sits on IP level network which Cyberstation identifies as network 0. Resolution The value entered in the bCX's BACnet Network Id - Comm2 from the configuration webpage is the number of the network the bCX will host on its MSTP port.  The bCX itself is located on the IP level network that CyberStation identifies as Network 0. BACnet devices located in the MSTP field bus of the bCX will show their BACnet Network Number as the value configured in the bCX's BACnet Network Id - Comm2 (default value 2765)

Issue A door configured with entry and exit readers using AC1/AC1A will report door switch trouble after controller is reloaded. Environment CyberStation CX9900 CX9680 AC1 AC1A NOTE: There is no problem if AC1Plus modules are used. Cause Configuration issue Resolution Attach resistors to exit side AC1's door switch, the resistor configuration on the exit AC1 must match the resistor configuration on the entry AC1. DO NOT wire the inputs on the exit AC1 to anything. Only the door switch has this requirement, the REX input does not require adding resistors to the exit AC1. See IO System Reference Guide  connecting a dual reader door for wiring information.

Issue Dehumidification using Xenta 121-FC Environment Xenta 121-FC Xenta 121-HP Cause Some aspects of how the dehumidification mode in the Xenta-121 operate are undocumented. Resolution The dehumidification feature of the Xenta 121 can operate either by turning on external dehumidification equipment using one of the digital outputs or, if no external equipment is provided, it will use the cooling for dehumidification. In the latter scenario, the heat continues to be operational when the cooling is forced for dehumidification. Additionally, if there is an outside air damper, it will be controlled to its minimum position before forcing the cooling on. When is external dehumidification enabled? For On/off cooling, cooling is enabled for dehumidification when the nvoDehumidActive value is greater than 10% and is disabled when the nvoDehumidActive value drops below 5%. For all other types of cooling, nvoCoolPrimary is set to match the nvoDehumidActive whenever it is a greater than cooling PID output + 5% or whenever the cooling PID output is less than 5%. The dehumidification feature can be configured using the ZBuilder configuration tool. However, the individual features can also be accessed via the points listed below using either Vista Workstation or another Lon management tool such as LonMaker: Applic UCPTappOptions Bit Usage If FALSE If TRUE Additional notes 5 Dehumidification control enable Not active Active   6 Dehumidification type Internal External Only applicable if bit 5 = true. External control can be hardwired or via SNVT. Internal will force cooling as a dehumidification method. 7 External dehumidification active on Open contact Closed contact Only applicable if bits 5 and 6 are both true. UCPTappOptions2 Bit Usage If FALSE If TRUE Additional notes 7 External dehumidification type Digital Analog If true then the RH reading is mirrored to the analog output (0-100% = 0-10V). Only applicable if UCPTappOptions bits 5 and 6 are both true.

Issue If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Environment CyberStation Network level controllers (CX, ACX, bCX) Cause If a controller will be offline for an extended period of time, is there a way to make it not show up in the Alarm View as offline? Resolution Edit the controller and on the general tab select the "Out of Service" checkbox. This sets the "To State" in the Active Alarm View to "Return to Normal" and the Value to "Out of Service". It also relieves the workstations from the task of probing and looking for a response to a probe until the out of service flag is removed.

Issue MN-LCD Uploading Environment Micronet LCD Display (MN50-LCD, MN50-LCDP, MN-LCD-100, MN-LCDP-100) Cause There are instances where an Micronet LCD has failed to upload a configuration from a MicroNet controller correctly. Resolution The following describes the correct process for downloading an LCD screen to a controller and uploading this to an LCD. If these procedures are followed, no problems should occur. How the LCD upload process works When an LCD configuration is sent to a MicroNet controller it is placed into controller RAM. When an LCD is connected to the controller it looks for the presence of this file and if it exists, this file is transferred to the LCD and stored permanently in EEPROM. This transfer process removes the controller copy of the LCD configuration; this means that should replacement of the LCD be required later the LCD scheme will need to be downloaded to the controller again. It is important to note that because the LCD file is initially stored in the controllers RAM it will be lost if the controller power is cycled or the controller is reset. LCD Download procedure Switch on power to the controller and then use VisiSat to configure and download the LCD configuration to the controller. If the controller is NCP and is to operate standalone, disconnect the communications from the controller before connecting the LCD and ensure that the LCD comms links are fitted to the controller (this is important). If the controller is NCP and is networked an MNN-COM card is required in the controller and the LCD must be remotely mounted. Make sure that the controller power is still switched on. Connect the LCD to the controller and apply power to the LCD. Note: Do not depress or hold any keys when connecting the LCD, this is only required if LCD firmware is revision J or earlier. Wait for the LCD to load its configuration. If the LCD configuration fails to load, check that the controller’s “Configuration Locked” property is not set to ”Yes” in VisiSat. Remove the protective strip from the LCD battery.

Issue Endura DVR missing the Video in I/NET Seven Rev 2.41 Product Line Pelco, TAC INET Environment I/NET Seven rev 2.41 Endura DVR Cause The Endura Workstation software that comes with the DVR (by default) is set to "Multicast". If this has not been changed, then you DO NOT have to change the three I/Net files listed below. If the Endura Workstation software was changed from the default (Multicast) setting to a "Unicast" setting. Then you WILL have to change the three I/Net files listed below. What is the Pelco definition of “Multicast” mode? By default, Endura encoders and Pelco network IP cameras are default to stream live video in Multicast mode. A common symptom of multicast routing issue is where the date and time stamp can be seen on the workspace but the video is black. This symptom is commonly associated in a layer 3 routing network where appropriate multicast routing protocol has not been enabled globally or inside the VLAN. Resolution The resolution is to modify three files that are installed with I/NET Seven rev 2.41. These three files are located in this directory on the PC – C:\Program Files\INet Seven INetAMT.exe.config INetCfg.exe.config INetW.exe.config Note: If the above three files are not in the I/Net folder, then you have not delete the previous SDK driver. You must delete the previous driver thru the "Add and Remove" option in Control Panel. Once removed then go into the I/Net CD and select the "Support" folder and manually load the new SDK Driver. Then proceed with the rest of the process in this article. Use Notepad to open each one of these files one at a time and change this setting from the "default" of "False" to "True." After making all of the changes in the three file, shut down the I/NET and IO Server ICON. Restart the I/NET again, and the Video should show up in the I/NET program

Issue How to create Elevator Access and Floor Override on Version 3 Product Line EcoStruxure Access Expert Environment Access Expert Applet Win 10 and above Cause There is no help or direction on how to perform this task. Resolution In order to do Elevator Controls, here is a link below to a video as well as some screen shots for clarification: Firstly there needs to have a Schedule, Access Level and Elevator Access created based on the application as seen on the screen shots Schedules Access Levels Elevator Access Elevator Reader Settings Elevator Floor Settings Floor Override Settings