Building Automation Knowledge Base

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 Do extended logs have accurate entries for the spring and fall time change periods?   Environment CyberStation, all Continuum controllers, extended logs, controller logs. Cause What happens to extended log data during time changes? Resolution When the clocks are turned back, log data in the controllers will not be updated for the time interval of the change and therefore that data will not be collected by the extended logs. When the clocks are turned forward, log data in the controllers is logged twice for the time interval of the change and therefore that data is collected twice by the extended logs.   This occurs due to the fact that each log entry in the controller does not consist of a value and a timestamp. The timestamp we see in a report is calculated by the time of the last log entry (LastLogTime) in conjunction with the configured logging interval (LogIntervalSecs). This mathematical calculation saves memory in the controllers. Extended logging is the mechanism most sites use to store, and report on data that is in excess of the amount of data stored in a controller. The extended log engine automatically collects the controller log data before it is overwritten. An added benefit of using extended logging is that the data can be easily backed up via several strategies such as database backups and/or running extended log archiving applications. In the controllers, not only is the memory limited, but the data is stored in volatile RAM, so extended logging is a more robust and long term strategy of collecting and storing the data. Extended logs can be set up on any of the automatic log types (LogInstantaneous, LogAverage, LogMinimum, LogMaximum).  During a period when the clock is moved forward, (for example, 2:00am Sunday March 11, 2012 on the east coast of the US), reports may display timestamps that essentially never existed (in this example 2:00am to 2:59:59am). It is recommended that these entries are simply ignored or crossed out. The period when the clock is moved backward is more difficult, if it is critical that data be captured for the duplicated time. An example is Sunday November 4, 2012. At 2:00am on the east coast of the US the clock is set back one hour. This means that the times from 1:00am to 2:00am occur twice. However, extended log reports will only show one set of data for the reason described above. The reports will show the first 1:00am to 2:00am data; the second 1:00am to 2:00am data needs to be captured separately.  If point log data must be captured for the duplicated timeframe, additional point configuration and Plain English (PE) programming must be used to capture and timestamp the realtime data values for the duplicated timeframe. This involves creating a numeric with a manual log  for each critical point which mirrors the live data value of the affected InfinityInputs, InfinityOutputs and InfinityNumerics. In addition, an InfinityDatetime point with a manual log must be created, one in each controller for each different loginterval of the points being mirrored in that controller. The PE program(s) capturing the point values will write the controller's date system variable to this InfinityDatetime at the same time it writes the live point value, thereby creating a timestamp that will be used for reporting. The last step will be writing the mirrored points and their corresponding timestamps to a file on disk and then printing and/or backing up that file for redundancy.  Click here to download a zip file containing sample dump files and a readme. This is an example of one way to accomplish the above data capture. 

Issue The Viconics VT7600 (or SE7600 - Schneider-Electric brand) LON thermostat displays a network variable input (nviSetpoint) with both the Niagara R2 and Niagara G3 stations. It is not available on the thermostat's local display. Product Line EcoStruxure Building Expert, TAC IA Series Environment Viconics VT7600 SE7600 Niagara R2 Niagara G3 Cause Add nviSetpoint to a Niagara-based graphic, but it cannot be cross-checked on the local display.  This may add confusion to the end users. Resolution nviSetpoint is, by design, a network variable without local display access.  It is used to calculate the occupied heating and occupied cooling setpoints (in conjunction with the deadband).  The occupied heating and occupied cooling setpoint have local display access. Below is an excerpt from the Viconics LonWorks Integration Manual (page 😎 describing the function of nviSetpoint and how it works with deadband to create occupied heating and cooling setpoints: Parameter Variable Name Function Occupied Cool & Heat Setpoints network Input SNVT_temp_p nviSetpoint This input network variable is used to allow the occupied temperature setpoints only to be changed via the network from a single analog value. (Note: the Unoccupied setpoints are not changed.) The corresponding heating and cooling values are derived from the minimum deadband configuration value Default Null Value: 621.81°F (327.67°C or 0x7FFF) Ex. If the minimum deadband configuration value = 2°F and nviSetpoint = 70°F The resulting Occupied heating setpoint will equal 69°F which is derived from 70°F minus one half the minimum deadband configuration value of 2°F The resulting Occupied cooling setpoint will equal 71°F which is derived from 70°F plus one half the minimum deadband configuration value of 2°F

Issue There's a need for information on the Personnel Import Utility Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Finding the information on the Personnel Import Utility may be difficult to locate. Resolution The information for the Personnel Import Utility can be found in the latter part of Chapter 19 on Personnel. There is additional information in Appendix C related to the tables and XSLT file. Click here to download a copy of just the PIU Manual.

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.

Issue PE program will not compile, due to the following error: Syntax error, unexpected token 'xxxxx' Environment Cyberstation All Andover Continuum controllers Cause Program is using one or more reserved keywords Resolution Remove reserved keywords from program's code. See Andover Plain English Language Reference Guide appendix B for a list of reserved keywords.

Issue There are many existing TGML graphics templates, components and snippets. Many of them have the animation binding with the digital value 0/1. But for SmartStruxure, especially the values from Continuum controller, it will show ON/OFF or ACTIVE/INACTIVE instead of 0/1. If binding these values directly to the graphic, the animation will not work. Environment SmartStruxure Cause The binding text or property should match the real value from the controller. Resolution Instead of modifying the TGML graphic, we have a better way to solve this problem. Double click the value that needs to be bound, and open the property window of the value. There is a property called 'Active Text' and 'Inactive Text' for this value. We can change the 'Active Text' to '1' and 'Inactive Text' to '0', then all the bindings can be used without any modification. But it depends on the workload of the project. If there are many values with a few controllers, maybe modifying the graphics is a more efficient way.

Issue Relay Control With Xenta Analog Output Product Line TAC Vista Environment Xenta programmable controllers Xenta 281, 282, 283, 301, 302, 401 Cause Occasionally installers of Xenta controllers are using the Analog Output (AO) of the Xenta controllers to control one or two external relays. This is being done when the HVAC application needs one or two more points of discrete on/off control and when the AOs are not needed for proportional control. Obviously, this deviation from normal I/O application is being entertained in a effort to avoid additional costs of higher capacity controllers and/or the Xenta I/O expansion modules. Implementation has consisted of a 12Vdc relay connected to the AO output and the AO is directed to 100% output (10V) to energize the relay and 0% output (0V) to de-energize the relay. Resolution While this AO relay control application has not been recommended for typical designs, it should be possible to accommodate it reliably as long as some specific considerations are included in the relay selection and installation. For more information please use the following link: Xenta Analog Output

Issue When downloading a controller in the Vista System Plug-in, messages are received saying the System Plug-in is waiting for the controller to restart, but this never completes successfully. This message may be shown many times. Environment Vista System Plug-in LonMaker Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There may be several different causes including communications errors or a corrupted application. However, by taking the controller offline in LonMaker, any extraneous interaction with the controller is temporarily ignored during the download. Resolution First, please double check the Vista ToolPack version that is installed, and make sure the version matches TAC Vista Server version. If not, please uninstall the Vista ToolPack and install the correct version of ToolPack. TAC Vista ToolPack can be download from Extranet (Software and Firmware > Engineering Tools). In LonMaker force the controller's neuron chip into a configured, bypass mode: Right-click the controller and select "Manage" In the LonMaker Device Manager window click "Offline" Download the controller in the Vista System Plug-in. In LonMaker set the controller's neuron chip back to configured, online mode: Click "Online" in the LonMaker Device Manager window then close window

Issue Following a reboot of CyberStation, alarms continue to be logged but are not displayed in Active Alarm View. Environment CyberStation Active Alarm View Continuum Database Initialization Cause Alarms not being displayed in Active Alarm View. Resolution Performed a Database Initialization with Enhanced Alarm Logging and Enhanced Alarm Delivery selected on the workstation.

Issue Exporting/Importing Configuration Profiles and need to copy CCTV configuration from one machine to another. Product Line TAC INET Environment I/NET Seven Cause When Configuration Profiles are created on one PC and the user wants to copy it onto another PC, there is no easy way to do this even through the SQL database. To accomplish this the user would have to first, Export and then Import the configuration files from the registry. Likewise when setting up a second standalone machine to use the same CCTV interface or similar Host masking settings can take some time. This process will allow you to transfer everything configured under the profile setting to a new machine. Resolution The following step describes how to do this: Caution • Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer. • To open Registry Editor, click Start, click Run, type regedit, and then click OK. • You can use a text editor like Notepad to work with the registry files you create by exporting. • You can save registry files in the Windows format, or as text files. Registry files are saved with .reg extensions, and text files are saved with .txt extensions. • In Windows Explorer, double-clicking a file with the .reg extension imports the file into the computer's registry. To import a registry hive just double click it from Windows Explorer. Open the Registry Editor On the File menu, click Export. In File name, enter a name for the registry file. Under Export range, do one of the following: To back up the entire registry, click All. To back up only a particular branch of the registry tree, click Selected branch and enter the name of the branch you want to export. Click Save. HOST MASK information To share host mask configurations between PCs, browse to C:\I/NET SEVEN DATA and copy the .dat files relevant to the configuration profile

Issue The following issues have been found to occur due to the Windows 7 User Account Control Settings: When starting I/NET, receive an error message indicating, "This is an unregistered version of I/NET.  Please contact TAC to register this copy of I/Net." DBCreate does not accept Windows Authentication login.  It only allows access to DBCreate using the SQL Server authentication login option. Login Issue with SevenReports (Crystal Reports)  Product Line TAC I/NET Environment I/NET Seven 2.4x Windows 7  Windows 10  Cause The User Account Control Settings appears to block access to these files required by the I/NET applications. Resolution Set the User Account Control Settings to "Never notify". Go to Windows Start Icon In the Search prompt, type in User Account - Select the option "Change User Account Control settings" from the Control Panel options shown below: The default setting is shown. Change this setting to "Never notify." You will be presented with the following confirmation - Select Yes Restart your PC Test the issue and re-install I/NET (a repair may be adequate) if the issue remains before contacting support.  This setting is only required to be done once for all users on the PC.

Issue Unable to create a file with a certain name such as "x". Get a message that the object already exists. The object does however not exist in the Vista database when viewed in Workstation. It seems that there are invisible objects in Vista. Product Line TAC Vista Environment TAC Vista Workstation/Server 5.1.X Cause This has been seen in older databases that have been created or edited using older editing tools such as TAMain. These system objects should disappear automatically but if they don't they will cause the error described under "Issue". Resolution This can be removed by starting the TAC Vista Database generator tool from workstation (Tools\TAC Vista Database Generator). Once started, do the following: Select Database\Export from Database. Click on the browse button in the Object field. In the field "Current object ID" type "x" (or the name of your invisible object" and the buttons on the right of the tool should be activated. Click on delete, and the object will be deleted. After this, you can check in workstation that the object has been removed by creating a new folder named "x".  

Issue Communication issues caused by improper grounding of the BACnet MS/TP shield connections to the B-LINK-AC repeater.   Environment BACnet MS/TP installation with B-LINK-AC repeaters. Cause The shield connection on port 1, labeled "(Input)", of the B-LINK-AC repeater is internally wired differently than the four other ports. Resolution Due to the differences in how the shield terminals are wired, the following techniques must be followed when wiring the B-LINK-AC BACnet MS/TP repeater. Port 1, marked (Input), must have its MS/TP bus shield connected to the SHLD terminal, which is isolated from Earth Ground. The incoming MS/TP shield must be grounded at only one point, at a location other than the repeater. Typically this is at the opposite end of the bus, or where the MNB-1000, UNC, ENC or other BACnet parent controller resides. All four of the other repeater ports, # 2 - 5, have their SHLD terminals tied together, and tied to Earth Ground internally, through the power supply's Earth Ground connection. For each MS/TP bus cable connected these ports, the single point of ground for the shield is at the repeater and, therefore, the shield must not be grounded at any other point on the bus. None of the five MS/TP ports on the repeater have internal termination resistors.  If a MS/TP trunk ends at the repeater, a 120 ohm terminating resistor must be connected between the MSTP+ and MSTP- terminals on that port of the repeater.  Likewise, the far end of each MS/TP trunk must also be terminated with a 120 ohm resistor between the MSTP+ and MSTP- terminals of that last controller. None of the five MS/TP ports on the repeater have internal bias resistors.  Standard practices, regarding the biasing of the MS/TP trunks, should be applied, as described in the I/A Series MicroNet BACnet Best Practices Guide, F-27360. Additional information on the use of these repeaters can be found in the "Approved MS/TP Repeaters" section of Chapter 5 of the I/A Series MicroNet BACnet Smoke Control Systems manual, F-27419.

Issue Serial Communication with Xenta Units (511, 527, 911, 913): Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Incorrect cables can cause improper ground references between the PC and the Xenta unit, which will disable serial communication. Resolution The Xenta units that utilize a web interface all have a certain amount of setup that is done with a direct serial connection via HyperTerminal. This communication however can be problematic at times due to grounding between the Xenta unit and the computer. If both devices do not share a common earth ground reference, then communication will not occur at all. There will be no indication that either side is receiving the transmissions from other device. This is most commonly encountered when using the incorrect cable since the proper cable provides a conductor for ground and thus a common ground reference. An OP panel cable is not the proper cable to use in such a situation. Instead you should be using the cables found in the TAC Xenta programming Serial Kit. If you are using a cable made by someone other then TAC the most likely cause is your cable having the improper or insufficient connections. When stuck in a situation where the proper cable is not available and working with a laptop computer we recommend that you plug the computer’s power supply in preferably to the same power supply as the controller to try to establish the common earth ground. Any other attempts to stabilize the differing grounds will be at your own risk.

Issue Understanding how the NPR functions in a corporate WAN / LAN environment NPR network Issues What information can we provide to IT (MIS) departments that will explain what the NPR is doing on their network. Product Line TAC INET Environment I/NET Seven Series 2000 NetPlus Router (NPR) Cause This advisory discusses the interaction of a Series 2000 NetPlus Router (NPR) with a corporate LAN/WAN. It is intended to alleviate any concerns MIS personnel may have regarding Ethernet network loading or LAN/WAN security.  Resolution For information on the Series 2000 NetPlus Router (NPR) when used on a corporate LAN / WAN refer to the attached Customer Advisory CA-2004-01.  This advisory includes more detailed information of the following topics: The NetPlus Router and Dial Security Protocols Packet Routing TCP/IP Communication Network exposure I/NET Ethernet Network Loading Network Utilization The NetPlus Router and Network Configurations Network Configuration for Proxy ARP:

Issue How to Rehost an NL220 Dongle to another PC. Product Line TAC Vista Environment NL220 License Transfer Cause Once an NL220 licensing dongle has been locked to a PC, it cannot be hosted to another computer without Newron's involvement. If you use it on another PC, it will be in "MOVED" mode which allows you to do all engineering tasks except for ordering more credits. Resolution You need to "free" the dongle in order to be able to Rehost it on a new computer. Download the NLDongleUtility from Newron Systems here. A login is required, but it is free to register. Make sure the dongle is plugged into a USB port of the PC Launch the NLDongleUtility by going to Start > Programs > NLSuite > NLDongleUtility > NLDongleUtility At the bottom of the screen is a button that says "Free." Click this button. This generates a code in the green tinted window. Use the "Copy" button to copy the code. Paste this code into a "free request" email addressed to fr-newron-credits@abb.com They will reply with an update key that will unlock the dongle and you will then be able to host it on the new computer. When the software key is sent back from Newron Systems re-open the NLdongle Utility click the Free button at the bottom of the program. Paste the Free Key sent from Newron Systems in the Free Key section and click the "Free" button. Open NL220 and confirm the dongle transfer.

Issue Access Expert is able to communicate down to the SSC (a reboot works) but the SSC won't come online and its status shows as unknown. Product Line EcoStruxure Access Expert Environment SSC Cause In IIS the binding has been configured incorrectly. (On Premise ONLY) Mercury port (3001) blocked.  Resolution This is what a properly configured binding looks like. (On Premise ONLY) Reference How to verify ports needed for AX-SSC communication with the Access Expert server are open from within the AX-SSC itself to check status of the Mercury port, if block work with IT department at the site to have it unblocked.

Issue CSMC 3805 Codes, CSMC User Guide. Environment CSMC3805 CSMC CSMC 3805 Cause There is a code displayed on the controller screen. What does this mean? Resolution The codes display the plant status under certain conditions. They are as follows: L05 = Return Water Temperature Low Limit. F = Water Frost Limit (Flow or Return). L01 = Inside Low Limit (Frost). H4 = Flow Water High Limit. A = Alarm (If alarm display is not required set code B61 to 1). 0 to 9 = Optimiser Status (only displayed if code B49 is set to 1). The User Guide can be downloaded from here.    

Issue Integration of the Carlo Gavazzi EM21 Power Meter with the Xenta 5xx\Xenta7xx Xenta 913 and Modbus RTU Environment Xenta 511, 527, 55, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Carlo Gavazzi EM21 Power Meter Cause Disclaimer:  This device template is intended to provide a starting point for an integrator and is not meant to be a mandatory points list for your integration project. Product Support Services has written this device template in an effort to give our customers a solid example of how to develop a device template for the above product.  The integrator will be responsible for any additions or modifications to this device template.   Please report any problems with this template to Product Support, via the Contact link at the top of this page. Resolution Please use the following dev file as a starting point and a guide to the integration.  This .dev file contains a subset of the registers in the device that PSS considers will be of most use to the integration process.  If any other data is required please see the latest Carlo Gavazzi documentation to make the necessary changes.   To use these files in XBuilder please follow these steps: 1.  Extract the .dev file from the .zip file in the link above and place it in a convenient location on your harddrive. 2.  In XBuilder, right-click on the Modbus Master device and choose 'Add Device'. 3.  Browse to the extracted dev file and choose 'Open'. 4.  Rename the newly added device to a unique name within the Modbus Master network.