Building Automation Knowledge Base

Issue Unable to use the "Put" command from the DB Admin tab of the Admin Tool in Workplace Pro.  Cannot select file buttons. Environment Workplace Pro UNC series Cause UNC must be in idle. Resolution The "Put" command can only be used to import a database to an "idle" UNC. To idle a running UNC, uncheck it's "Auto Start" box and reboot.

Issue Clearing IP address in the 527 routing table Product Line TAC INET Environment I/NET TCP/IP Cause Routing Tables build themselves by self discovery. Resolution Routing tables build themselves by self-discovery on the network. If there is more than one device/host PC, similar function(s) may need to be performed on each device. Telnet utility for Host PCs, I/NET NPR2000 are examples. NOTE: Anytime you use the I/NET Command Line: inet(space) and the command you want to use for example; inet ip. Steps to clear a 527 routing table. Log into X527 with your web browser. Select the utilities folder. Select I/NET folder. Select I/NET Command Line. Make sure the word inet is in the command line and press submit. Then type inet delall to delete all the routing tables for the Xenta 527. You can type in inet help and this command will list all the all Web Shell Commands. ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all listsv ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records  

Issue In Niagara R2, device objects are not updating. Bundles were used to speed the linking to graphics. Environment Niagara R2 Cause The device objects are in bundles. Resolution Only native Niagara objects should be placed in bundles. This includes the Niagara AO, BO, AI, BI, and logic (if desired). Due to the nature of bundles they execute at their own rate. This interferes with the normal execution of BACnet, LON, GCM, ASD, DMS, MS and other hardware objects. For additional information on the use of bundles refer to The Standard Reference Manual pages 7-14 through 7-21 and pages 5-1 through 5-6 of the Web Solutions Guide.

Issue Using Vista Classic with the Xenta 121 controller and ZBuilder will not open from Workstation Environment Vista Classic network Vista Workstation ZBuilder Xenta 121 Cause ZBuilder can not open if there are any spaces in the: Vista Server name Port name LonWorks network name LonWorks group name Xenta controller name Resolution Verify that there are not any spaces in any object names within the network. Always use _ (underscore) instead of spaces.  

Issue Where can I find Cyberkeywriter2.exe to upgrade my CyberStation key. Environment Cyberkeywriter2.exe CyberStation Cause There are 3 locations from which you can obtain the Cyberkeywriter2 executable file. Resolution Download Cyberkeywriter2 on The Exchange Download Center Cyberstation CD Do a search of the CD for "Cyberkeywriter2.exe" Cyberstation Workstation From Windows Explorer, search for "Cyberkeywriter2.exe"

Issue Adding a BCX1-CR-32-INF controller into Cyberstation and the drop down list does not show this as an option Environment BCX1-CR-32-INF CyberStation Cause In CyberStation when adding a controller to the system the drop down list will only show Model numbers and will not show the part number. Resolution See below for examples: BCX1 Router Only Model Number = 4000 BCX1 Bacnet Version Model Number = 4040 BCX1 Onsite Version Model Number = 4020 BCX1 Infinet Version Model Number = 9640  8Meg Netcontroller Model Number = 9900 4Meg Netcontroller Model Number = 9940 2nd Gen Netcontroller Model Number = 9680 ACX2 (8 Door) Model Number = 5740 ACX2 (4 Door) Model Number = 5720

Issue Does Windows XP Service Pack 3 (SP3) cause a problem with SIGNAL XP? Environment SIGNAL XP computer Service Pack 3 Service Pack 2 Cause Any known issues with the SP3 helps if updating is necessary. Resolution The impact of SP3 on SIGNAL XP is not known. SIGNAL XP has been field-tested with Windows XP Service Pack 2 and the only issue identified was recognition of the Security Plug (see TA06-03). No other anomalies have been observed. There are no plans to validate SIGNAL XP with this new service pack. It is recommended that all SIGNAL XP computers maintain Windows XP at service pack 2.

Issue Without a Niagara R2 UNC, Enterprise Server, or MNB-1000 on a BACnet/MSTP network, can the MNB controllers communicate reliably peer-to-peer (i.e. sharing outside air temperature between multiple MNB-300 controllers)? Environment MNB-300 controllers Cause Some site would like to avoid the use of Niagara R2 UNC, Enterprise Server, or MNB-1000. Resolution Yes. The implementation of COV subscriptions in the MNB controller line, with the 1.4x (or greater) firmware, allows for every MNB controller to function as both a COV server and a COV client. This allows peer-to-peer communications between all MNB controller models. To create peer-to-peer links, review Chapter 4 in the WorkPlace Commissioning Tool and Flow Balance Users Guide (F-27358) that details how to use Link Builder.

Issue Run to file fails after an upgrade to versions 1.74 and above. You no longer can write to file using the run command. Environment Cause Enable write to file Resolution Instructions to enable write to file: 1. Create a workstation program named "Test1": (Example) Line Here1 Print "Hello There" Print PowerUpTime Stop Open the configuration and make it a fall thru program IMPORTANT check the "Run on any workstation box" The Run on any workstation required is what was changed from prior versions 2.Create another workstation program (Sample Program) Line There2 Run test1 to "c:\TestPEOut.txt" Goto There3 Line There3 If TS > 9 then Goto There2 Line E Stop

Issue How can an existing Enterprise Server station be configured to run the Vykon Alarm Service (VAS)? Environment Enterprise Server Vykon Alarm Service Cause For Enterprise Server to support VAS, check the Enterprise Server shipped date to determine if part number IA-ENT-AS is required. Resolution An Enterprise Server station is already licensed to support VAS. It also includes support for two VAS clients. If additional clients are required, order part number IA-ENT-AS-C for each additional client. If the Enterprise Server was shipped before November 1, 2002, it did not include support for VAS. It must be ordered separately using part number IA-ENT-AS (which will also include support for two VAS clients). The Enterprise Server must also be upgraded to, at minimum, build r2.301.330. For more information, review R2 Worksheet (xlt) tab "ENT SVR Estimator" for additional notes on various part numbers. VAS software can be downloaded from The Exchange. Download VAS v2.4 CD Image.zip and VasPatch.zip. Unzip the CD Image for the Installation Instruction Manual. The VasPatch is installed last.

Issue A Liebert SiteLink panel is not communicating with the Niagara R2 UNC using BACnet/MSTP. Environment Liebert SiteLink panel Niagara R2 UNC BACnet/MSTP communication Cause Termination resistors Resolution When connecting a dedicated Liebert SiteLink module MSTP segment to the UNC, the EIA-485 trunk typically requires 120-ohm termination resistors at each end. Field testing has determined for Liebert Sitelink-4 and –12 modules that the termination resistors have a negative affect on communication even at a low baud rate of 9600. Removing the termination resistors resolved the communication issues.

Issue How can two MicroNet 2000 MN-FLO or MN-FLO3T VAV controllers share data? Environment MicroNet 2000 MN-FLO / MN-FLO3T Cause Sharing data between the devices require MicroNet Integrator. Resolution Sharing data between two (or more) MicroNet controllers requires a MicroNet Integrator. Even if the integrator is not communicating to a GCM/DMS, it is still required to facilitate data sharing on the U-bus. The only system configuration, not involving an integrator, is stand-alone mode. Peer-to-peer data sharing is not possible. See the MicroNet 2000 Family Fundamentals Guide (F-25711) and review the chapter on System Configurations.

Issue Trend Log pages, Time Object pages, Alarm pages and Value pages in a TAC Xenta 721 project. Environment TAC Xenta 721 Cause XBuilder allows for the creation of some additional objects in a Xenta 721 project for use with the OP7, not to be visible in a web browser or Vista Workstation. Resolution In the XBuilder 5.1.0 you can add Trend Log pages, Time Object pages, Alarm pages and Value pages in a TAC Xenta 721 project. These pages are only for use in the OP7. Unfortunately, they are visible in the TAC Vista database and the pages do not work in Vista. If you use IE to browse the Xenta 721, you can not see the pages. These pages should not be visible in TAC Vista. This was reported as a bug and will be corrected in later versions.

Issue With Niagara R2 Status Type objects, what colors are used to represent their different real-time conditions? Environment Niagara R2 Cause Configure the status indicator to turn a different color of an off-normal condition. Resolution Status-variable type objects contain a 'statusInput' (sIn) and 'statusOutput' (sOut) property. These objects are: BooleanStatusType floatStatusType integerStatusType The sOut will change to a different color for the following conditions: orange (dark yellow) -> fault yellow -> down red -> inAlarm cyan (light blue) -> OutOfService magenta (purple) -> overridden clear (grey) -> normal These are the background colors as the real-time text remains black in all cases. These are also the default colors that can be changed by modifying the statusColors.properties file.

Issue If you are integrating LON to I/NET with a Xenta 527 or Xenta 913, you may run into a unit conversion problem in the integration process. Product Line TAC INET, TAC Vista Environment I2V I/NET LON Integration Xenta 527, Xenta 913 System Program Version 5.0.0 or higher XBuilder 5.0.0 or higher Cause When integrating LON to I/NET, all data will make its way to I/NET in SI units. Resolution View the units of the points on the LON side of the connection object in XBuilder. On temperature, for example, XBuilder uses the unit "F" to show Fahrenheit on a temperature signal. However this temperature value will show up in I/NET in Centigrade.  Engineering units on the AO point in the I/NET controller will have to be "F" to mirror the unit on the LON signal in XBuilder. These two units have to match exactly, and they are case sensitive. When the engineering units match on both points, I/NET will convert to the correct value. If the value on the I/NET side is left blank, it will just pass on the Celsius value. There are limitations to this conversion since I/NET has a four-character limit and some units in XBuilder will exceed this. Pressure, for example, will have to be sent in Pascals or PSI. 

Issue What is the preferred architecture with MNB MSTP controllers when an installation has a MNB-1000 and a Niagara R2 UNC?  Hang the controllers on the MSTP bus of the MNB-1000 or the UNC? Environment MNB-1000 Niagara R2 UNC MNB Controllers Cause Prevent any performance degradation by hooking up the MNB controllers in the correct location. Resolution Either way is OK.  If the MNB controllers are on the MSTP trunk under the MNB-1000, then the MNB-1000 acts as a router, and communication is a little slower than if they were directly connected to the UNC.

Issue After upgrading Vista, upon opening reports you receive the error "Report is of a previous format. Please try updating the database again." Environment Upgraded Vista Workstation Reports Cause Version property may need to be set for each report that needs to be upgraded. Resolution Upgrade the current database. You may have to change the Version property for each report that needs to be upgraded. Right-click on the report, select Properties while pressing down CTRL + SHIFT. This opens the 'advanced' properties dialog. If Version is 1 change it to 0. Run regedit to open the Registry Editor. Open 'HKEY_LOCAL_MACHINE\SOFTWARE\TAC AB\TAC Vista\4.2' (Select folder that matches your version of Vista) and locate the key 'UpgradeReports'. Set this value to 1. (0 means do not upgrade.) Start Vista Server and the reports in the database should be upgraded properly. The file UpgradeReportsLog.txt in the database folder $log contains detailed information about the upgrade process.  

Issue Can the profile in a MNL standard LonMark controller be changed in the field?  For example, can a MNL-20RH3 (heat pump profile) be changed to a MNL-20RS3 (satellite 3 profile)? Environment MNL standard LonMark controllers Cause The LonMark Profile is stored in the controller's firmware. Resolution No, the LonMark Profile cannot be modified.

Issue How do I change a CX-9200 or a CX-99xx to a CX-9680 (Netcontroller II) Environment Cyberstation CX-9200 CX-99xx CX-9680 Cause Controller has changed and need to change the controller model number in Cyberstation. Resolution If you are Using Cyberstation V1.74 with SP2, or Cyberstation V1.81 or greater, all you need to do to accomplish this change is to edit the existing controller (CX9200 or CX99xx). In the controller Type dropdown menu, select 9680 and OK the change. When you save the change you will be prompted with a warning that this change is not reversible. Once you OK that, the database will change all the appropriate system objects to be compatible with the Netcontroller II including system variables. The replacement CX9680 can then be reloaded from the Cyberstation and the conversion is complete.

Issue Is there a fix for MN50 Controller Optimisers and the Run-up/down influence node error. PIB 07.11.02-1 Environment MN50 PIB 07.11.02-1 Cause A firmware upgrade is required. Resolution Version 5.02 Firmware now fixes this problem.