Building Automation Knowledge Base

Issue The System License Information screen has a lot of useful data on the status of licenses in the EBO system. Is there a way to export or screenshot the entire System License Information page? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Unable to save or export the System License Information screen Resolution There is no option to print or export the Control Panel System license Information screen. It is possible to get a reasonably close facsimile by viewing the LicenseStatus item in System>LicenseManager and adding columns for Required Licenses, Checked Out Licenses, Installed Licenses, Available Licenses, and License Violation.   This can then be Exported in XLSX format for future reference or if required by Product Support  

Issue When troubleshooting I/NET crashes an error log is needed for further investigation. Product Line TAC INET Environment I/NET Cause Error log feature is not enabled by default in I/NET. Resolution 1. Click on Start--->Run, and type regedit to open the Registry Editor (if Run is not shown, just type regedit in the search bar in Start menu) 2. For 32 bit Operation System, browse to HKEY_LOCAL_MACHINE-->Software-->CSI - Control Systems International-->Host Configuration, and open ErrorLog Key; For 64 bit Operation System, browse to HKEY_LOCAL_MACHINE-->Software-->Wow6432Node-->CSI - Control Systems International-->Host Configuration. 3. Change the Base from "Hex" to "Dec". Then change the value to "1". This will turn on the Error Log Function. Then change the Base from "Dec" to "Hex" before closing out of the Registry Editor. And then reboot the computer. 4. Run I/NET, and if there are errors happened, there will be an Error.txt file under C:\INET Seven Data\  folder. You can see the error about I/NET. If any further help about the issue, please contact Product Support. 

Issue On a Windows 2003 Server or Windows XP, TAC Vista is not able to locate the license server, even though everything seems to be set up correctly. You get the message "-15, 10 System Error: 10061 Winsock Connection Refused" when you try to open any TAC Vista software. Environment TAC Vista Flexnet license Windows 2003 Windows XP Cause The TAC Vista software is looking for the license server on the PC defined, but the license server is running using the TCP/IP v6 address and the software doesn't support that on this operating system. Resolution Uninstall TCP/IP version 6 and reboot the PC. Below is a description on how to do it.   For the IPv6 protocol for Windows XP with SP1 or later or Windows Server 2003, do the following: Log on to the computer with a user account that has privileges to change network configuration. Click Start, click Control Panel, and then double-click Network Connections. Right-click any local area connection, and then click Properties. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or later or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK. Alternately, from the Windows XP or Windows Server 2003 desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt. At the command prompt, type netsh interface ipv6 uninstall. To remove the IPv6 protocol for Windows XP with no service packs installed, do the following: Log on to the computer with a user account that has local administrator privileges. From the Windows XP desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt. At the command prompt, type ipv6 uninstall.

Issue I/NET Seven and Key Card translation What is the Key / Card Translation table and how do I use it? Can I use the Key / Card Translation table for other card types other than I/DISC? Product Line TAC INET Environment I/NET all revisions Cause Need to understand what is the Key / Card Translation table and how do I use it. Resolution As I/NET evolved it first used what might be called a sequential look up table to translate I/DISC keys from number much to big for the DPU / SCU to interpret to one of the 1 to 24,000 (32,000 current) individual numbers permitted in a Tenant. The I/DISCs are shipped in lots from the manufacturer and the container states the starting key number, e.g. 897541, and the number of keys in the container. I/NET has an editor called Key / Card Translation that allows associating those I/DISCs with an individual. The box labeled Source is used to enter the first key/card in a lot of keys (usually read off the container). The Target box is used to assign the key to an individual in a Tenant. The Count box is used to set how many sequential keys will be associated with individuals. There are four card types that can be read directly without a translation table, Wiegand 26 and 32 bit and ABA 115 and 85. On the Wiegand cards the Tenant Code must match the site or tenant code on the cards and the card number must be less than 24,000. For all four types of card Switch 7 on the DPU is set to off. Wiegand 66 bit, Custom Wiegand and Custom ABA must be selected to use a translation table, and Switch 7 on the DPU is ignored. The next evolution involved allowing the “big (large) card number” to be stored with the Individual. This removes the requirement of using the key / card translation editor. Please see the following document for additional details and examples: Card Numbers.doc

Issue Xenta error log - NoLink 29 Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause When checking the error log of an Xenta there is a error "NoLink 29". The error means that the network cable has been unplugged or that the Xenta has lost contact with the host in another way. Resolution 1. Check so that there is no loose ends on the TCP/IP cable connected to the Xenta and the router/switch. 2. Check with IT department to see if there has been any planned or unplanned disruption on the network.

Issue The Object Server is attempting to open a file that is already opened by another application. Error: LNS #10 lcaErrFileOpen Lca : Could not open the specified Application Device load image (*.APB) file. (Subsystem: LNS, #10) Product Line TAC Vista Environment NL220 Vista LNS Cause Trying to load an application image to a Xenta 102-AX from NL220 by selecting the default APB extension may generate this error. Resolution Use the .NXE rather than the .ABP.

Issue Are the RoamIO and RoamIA interchangeable? Product Line TAC IA Series Andover Continuum Environment I/A Series WorkPlace Tech, Continuum Service Tool Cause Need to communicate directly on the field bus wiring to controllers. Resolution There is a firmware difference between the RoamIO and RoamIA, so they are not interchangeable.

Issue CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output, but the Xenta 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller.  If replacing the sensors would be too costly and time consuming, this is a viable option that will allow you to drop the voltage output on the CO2 sensor using 1000 ohm resistors.  Product Line TAC Vista, EcoStruxure Building Operation Environment 102-AX Cause CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output but the 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. Resolution NOTE:  It is recommended that the incorrect sensors be removed and replaced with new sensors that have the proper specifications to match the 102-AX capabilities.  If the sensor replacement is not an option please follow the instructions below. Please see the image below: You will need (2) 1000 ohm (1k) resistors to complete this conversion. Wire one resistor directly to the output wire of the CO2 sensor Land that resistor to U3 on the 102-AX Jump a second resistor from U3 over to M on the 102-AX Land the other output wire from your CO2 sensor on M with the jumped resistor   Also see Using a 4-20mA CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 4-20mA CO 2 sensor input on Universal Input 3.  

Issue Sigma reports no seats available with a registered SigmaX installation SigmaX 4.3 Missing Path Environment Sigma SigmaX Paths   Cause Numerous issues can arise when running the some versions of Sigma and SigmaX. The problems experienced are varied and can affect the operating functions of the programs and communications. Resolution Make the following modification to the PC's System Properties. Note: This addition is only required on machines running SigmaX. Right click the My Computer icon on the desktop and select Properties Choose the Advanced tab and select the Environment Variables button From the System Variables section, highlight Path and select Edit The statement ‘;C:\Sigma\Bin’ must be added to the end of the Variable value line (see below)   To view the PIB document click here. To download the PIB document click here.

Issue Event notification is grayed out in the AS and will not allow configuration.  Cannot add a category within the AS. Product Line EcoStruxure Building Operation Environment SmartStruxure Shadow AS Event Notification Cause The Event Notification in the AS can be locked due to a shadow relationship with an Event Notification in the ES. Resolution Note the IP address of the AS, as the shadow relationship can be re-established after necessary changes are made. Remove the shadow relationship to the ES to allow configuration of the AS. Detailed instructions can be found in Unable to add an Automation Server underneath an Enterprise Server. Re-established the shadow relationship if needed.

Issue Specific Trend log stops working in TAC Xenta Get estimated values in some trend logs; others are working Trend log is not retrieved from TAC Xenta Product Line TAC Vista Environment TAC Xenta 301 TAC Xenta 302 TAC Xenta 401 TAC Xenta 282 TAC Xenta 283 TAC Vista Cause The issue can be that there is a "Non value" in the log. For example, if you are logging an expression block with division in it and there is a division by 0. This seems to lock the trend in TAC Vista, and no other values can be collected. Resolution In the properties for the log, click on erase log. This will delete all values in the device. Open your menta and make sure that there is no possibility of division by 0.

Issue Webclient Pro and Personnel versions support different features and there is a need to understand the differences Product Line Andover Continuum Environment Webclient Cause It is helpful to understand the differences between Webclient Pro and Personnel Resolution Webclient Personnel features WebClient is an application that provides you with web-enabled access everywhere, all the time. By using Internet Explorer, your authorized personnel can access the Continuum facility management system in real-time across your site’s local area network (LAN) or across your wide-area network (WAN). WebClient is either added to a LAN Andover Continuum CyberStation system or installed with a standalone CyberStation on a single PC. With the basic WebClient Personnel Manager option, your users can:    -Create, search for, edit, and delete personnel records -Change employee access privileges -View a person’s access events -View and generate reports of all access events, including area access events, access events by persons, and    distribution-event transactions via the Access Distribution View -Edit and view schedules and calendars. -Change a password.   Webclient Pro features With the advanced WebClient Pro option, your users have all the features of the basic WebClient Personnel Manager option as well as the following additional features:    -Create, run, and view graphical reports (class object Report), including bar charts, pie charts, trend charts, text    reports, and so on.  -List and view graphics and groups -View live system alarms and live events -View live video, as well as search for and view recorded video, via the class object, VideoLayout. -Search for web.Client objects by exploring a folder tree hierarchy or a network/device tree hierarchy, or by using a   text search engine  -Edit and view Loops and TrendLogs.  

Issue How to configure individual alarm viewers for users. Environment StruxureWare Building Operation Workstation 1.3.0 Cause If all users workspaces are connected to the same alarm view then if one user changes the filter the alarmview will change for all users. This is because they are all links to the same object. To have individual filters you have to create multiple alarm views and attach them to the workspaces. Resolution Create a new alarm view by In workstation Right click and select new-view Select Alarm View Type in a name, click create Attach the alarm view to a workspace. Open the control panel in Workstation, click on account management Select the workspace you want to add the alarm view to in the drop down list under Workspaces Click on content. Click on the alarms pane (or add one) and click edit. In the field "initial path" browse to the alarm view you created before. Click close

Issue Get error message, "taclogdata is not a valid TAC Vista logdatabase" at installation of TAC Vista. Environment TAC Vista 5.1.0 and later versions. Cause When installing Vista and using a custom SQL installation a SQL database is specified. If this SQL database is created manually and not by Vista the database will not be recognized as a valid TAC Vista log database.   Resolution Let TAC Vista create the SQL database at the installation or use the Vista server setup to create a SQL database. 

Issue E-mon D-mon Modbus Meter in StruxureWare Building Operation Environment Modbus Cause The Modbus device object in StruxureWare Building Operation requires a single poll to query to get its online status. This device will only respond to polls when 2 or more registers are polled. Resolution Create the Modbus Device Object Edit the Properties Set the poll register to 4001 Set the Poll Code to 03 Please see the attached guide for the complete register list for this device. Please note that this poll register is listed in the manual as 44001

Issue When there are dual NICs on the computer, you will get host number conflicting error. The IP address causes this conflict is just the local IP address. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET prior to Version 2.44a Win 7 or higher OS Cause When there are two NICs on the computer, I/NET needs to know which NIC is used for communication. I/NET support for dual Network Interface Cards (NIC) can be used for dual NIC configuration for I/NET. But under Win 7 and higher OS, wireless NIC can't be recognized in I/NET, which makes it impossible to choose wireless NIC to be used for I/NET. In the I/NET configuration, it just shows 0.0.0.0. Resolution I/NET will fix this issue in the new release. For I/NET prior to version 2.44a, there are two workarounds for this issue currently: Refer to I/NET support for dual Network Interface Cards (NIC) to choose onboard NIC to be used for I/NET communication. Disable onboard NIC or just disconnect it from the network. Then you will see the option for choose NIC for I/NET communication will be grayed out. That will force I/NET to communicate with wireless NIC. Remember to reboot I/NET I/O server after this to make it take effect. 

Issue SmartStruxure Lite provides Script library and Firmware upgrades through a password protected website. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite (SSL) Cause Requesting further documentation, firmware, and login credentials to the SmartStruxure Lite website (SmartStruxure Lite Solutions) Resolution SmartStruxure Lite can be purchased over the counter by anyone. To get access to the SmartStruxure Lite website for downloading firmware,scripts, and further documentation, site engineers will need to go through the training program. Until this is completed, they will need to seek support from a trained SE partner or branch for support.

Issue MicroNet Heat Pump / Fan Coil Controller Diagnostic Table Environment MicroNet 2000 MN-HPFC Cause Quick reference table with corrective action Resolution This table is an excerpt from the MicroNet Heat Pump / Fan Coil Controller Reference Manual (F-26174):

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.

Issue The Lonworks Network has been moved under the LNS Port and no longer resides directly under the Vista Server in the tree structure as it was in previous versions.  This will add a level in the binding path and the old paths are no longer valid. This will impact any binding paths to objects on the root level of the System Tree.  Product Line TAC Vista Environment Upgrade Vista from versions older than 4.5 to newer versions OGC Graphic bindings Trend Log bindings Cause Versions of Vista < 4.5 had the Lonworks Network connected directly to the Vista Server in the workstation tree structure. A revision to this tree structure was made in all versions of vista > or = 4.5. After an upgrade from an earlier version to 4.5 the Lonworks Network is under the LNS port and is no longer connected directly under the Vista Server. This will add a step to the path in your graphic bindings that must be corrected in the OGC Graphic Editor. Example: OLD Binding Path: VistaServer_LonWorksGroup_ControllerName_Point NEW Binding Path: VistaServer_LNSPort_LonWorksGroup_ControllerName_Point Resolution You will need to edit the binding path of graphics at the root level of the System Tree. Follow the steps below to repair the bindings: Right click on the folder that contains the graphics that need to be altered in Vista Workstation (This same procedure can be performed on individual graphics as well instead of an entire folder). Select "Change References". Click Search in the Change references window. This will display all references that are contained in this folder. Select all references (Alt A) in the window and click Replace. Type the OLD path into the "Find what" field (example:VistaServer_LonWorksGroup). Type the NEW path into the "Replace with" (example:VistaServer_LNSPort_LonWorksGroup). Click OK. Verify that the reference path in the New column is correct and then click Save. This will repair all of the bindings in this folder.  You will need to repeat these steps for all folders containing items that reference points below the LNSPort . Note: Correcting this path will fix the graphics bindings in all future releases of Vista.