Building Automation Knowledge Base

Issue In Xenta Server's web interface, web pages are displayed incompletely. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 HP and Siemens PCs Cause Hyperthreading has been found to be a problem on some PCs. Resolution Disable Hyperthreading in the PC's BIOS. This issue has been found on some HP and Siemens PCs.

Issue When interfacing Veris pressure transmitters (PXP-xx-02S-T1) with a 0 to 5 vdc output signal to a universal input of a MNL controller instead of seeing 0 vdc with 0 pressure the UI is seeing .5 vdc. Environment Veris pressure transmitters (PXP-xx-02S-T1) MNL Controller Cause This is a compatibility issue with the Veris transmitters. Resolution Veris Technical Support suggests putting a 2.2k ohm resister across the OUT and COM of the transmitter. This has been confirmed to resolve the issue by field personnel.

Issue A Niagara R2 Enterprise Server with a large number of alarms and archived data is no longer needed.  How can all this data be removed quickly? Environment Niagara R2 Enterprise Server Cause Delete unused alarms and archived data on Enterprise Server station. Resolution This data is stored in the "app" folder on the Enterprise Server station. Using Windows Explorer go to Niagara > r2.301.522 > stations > "Station name". Rename or delete the "app" folder and restart the Enterprise Server. When Niagara discovers there is no "app" folder it will create a new, empty one.

Issue A Niagara R2 UNC-520 time clock cannot maintain proper system time.  It is losing approximately 1 hour daily. Environment Niagara R2 UNC-520 Cause Inadvertently calibrated with an incorrect time clock. Resolution This issue can be corrected in the field.  For details, read TPA-RKFD-08-0003.00 "Slow Time Clock on UNC-520-2 and UNC-520-2-N" on The Exchange Download Center.

Issue TAC has discovered an anomaly where R2 BACnet networks operating with the BACnet jar version 523b or earlier may stop updating object values after a period of time, typically over a 24 hour period. In certain large BACnet networks, the polling mechanism in the BACnet service can get into a "deadlock" condition, causing polling to cease. The only way presently to recover from this condition, with version 523b, is to restart the Universal Network Controller (UNC). Environment I/A Series R2 (Niagara) station with the BACnet service, version 523b or earlier Cause Operating with the BACnet jar version 523b or earlier may stop updating object values after a period of time. Resolution Refer to TPA-RKFD-08-0010.00, "Issues with I/A Series R2 BACnet Integrations" for Solution and Action. BACnet jar 527i (along with the revised bacnet.properties file) was recently released to help prevent the "deadlock" condition from occurring, thus ensuring consistent polling and updating. In addition, the new jar allows for composite math precision limitation in rewrite determination. Composite math results in values being sent to BACnet controllers from the UNC being slightly different than those being written to and read from the controller itself. For example, if the UNC writes "50.0," the controller will be "49.99999." Since these two values are not the same, the UNC will attempt to re-send the value. With the implementation of the "MinimumFloatDifference" property in the bacnet.properties file, this difference will now be ignored. In past releases, this has caused extra writes, and more importantly, unnecessarily increased the amount of traffic on the network, resulting on slower polling of other BACnet objects. Our recommendation is to upgrade any UNC with BACnet integrations to the 527i BACnet jar. The files are contained in a .ZIP file - bacnet-2.305.527i.zip. The .ZIP file contains the jar files, the bacnet.properties file, and a READ_ME_FIRST file that has detailed instructions for installing the files.

Issue Can Niagara R2 / G3 operate on Windows XP Service Pack 3? Environment Niagara R2 / G3 Cause Windows XP SP3 is not an approved platform for the IA Series. Resolution The recommendation at this time is to remain with Windows XP Service Pack 2. For more details, read TPA-RKFD-08-0008.01 "Windows XP SP3" on the ExchangeOnline web site.

Issue Where can Microsoft Vista-compliant legacy tools be obtained for use with DMS and NETWORK 8000 products? Environment DMS NETWORK 8000 Cause Microsoft Vista legacy tools for NETWORK 8000 Resolution Microsoft Vista-compliant versions of PSI, XPSI, MN-CI, and OPRIF have been provided for download on The Exchange Download Center site.  The following files have been posted. OPRIF 11.6 for Vista and XP (use with DMS products) PSI 4.1 for Vista and XP (use with NETWORK 8000 products) The PSIv4.1.zip contains XPSI, PSI, MF2 AirBalance, MicroNet-CI and MicroNet AirBalance. Review the readme_psi.doc provided in the zip file for changes and supported RS-485 converters. Direct ASD connection is now supported when utilizing the suggested RS232 to RS485 converter.  

Issue A Niagara R2 Enterprise Server station will only display 5 to 10 web pages before appearing to lock up. This problem may also occur when displaying web pages directly from a UNC too. Environment Niagara R2 Enterprise Server station Cause The Microsoft Internet Explorer Active-X Activation issue was included in Build 522.v1. It has been determined that this solution has caused graphic page display problems on some job sites, especially on web pages containing a frameset. Resolution Upgrade the Enterprise Server and/or UNC system software to Build 522.v2. Download r2.301.522_PatchFiles.zip. Open the zip file and follow the procedure in the file "r2.301.522_PatchReadme.pdf"

Issue What is indicated by the Status LEDs on the MicroNet 2000 ASD Integrator (MN-ASDI)? Environment MicroNet 2000 Integrator Cause Information on the Status LEDs Resolution The MicroNet 2000 Integrator for the ASD bus (MN-ASDI) has three Status LEDs: Yellow RX, Green TX, and Red ON. The LEDs indicate the following activities: Yellow RX LED blinks when it detects receive activity on the ASD bus. Green TX LED blinks when it transmits to devices on the ASD bus. The Red LED indicates processor activity AND communication activity on the U-bus interface. The frequency of blinking is dependent on the amount of activity.

Issue TAC Xenta 120, up to version 1.08, CO 2 input as 2-10 Volt Environment Xenta 121-FC ver 1.08 and earlier Xenta 121-HP ver 1.08 and earlier Cause The input is designed for 0-10 volt signal and will be offset by 20% if a 2-10 volt sensor is applied. Resolution When 0-10V for input is used the 120 will multiply the voltage by the scale factor: V * S = CO 2 reading. When 2-10V for input is used the 120 will multiply the voltage by an adjusted scale factor: V * ((S*10) / 😎 = CO 2 reading. When using a 200ppm Scale factor this results in a reading of 600 ppm when reading 3V on a 0-10V input and 250 ppm when reading 3V on a 2-10V input. This behavior is not correct, and needs to be corrected in a future release.  

Issue How to change the default XBuilder project location. Environment XBuilder Cause The default XBuilder project location is in the hidden Application Data folder. Some would prefer to have this default to their usual projects folder on the hard drive. Resolution Go to Start > Run > and type 'regedit' Go to HKEY_CURRENT_USER > Software > TAC > TAC XBuilder X.X.X >Options X.X.X is the version of XBuilder e.g. 5.0.3 Change the "ProjectLocation" key

Issue Unable to delete disabled alarms that no longer exists in the TAC Vista Db. Environment Vista Workstation Alarm Queue Cause If you delete alarm objects that have previously been disabled in the database these alarms will still be in the Disabled alarm list.  Resolution In the database folder in $thisdb there are 2 files called $this.blk and $this_bp.blk that contain the disabled alarm list. Close TAC Vista server and open these files with notepad. Find the alarm that no longer exists and delete the whole line. Save the files and restart the TAC Server.

Issue When upgrading a Niagara G3 ENC-410 / ENC-520 from 3.0.xxx to 3.3.xx, does the license file need to be upgraded too? Environment I/A Series G3 hardware I/A Series G3 software Cause License compatibility question. Resolution View the ENC license file. The first line indicates the version. If the license version="3.3", then the ENC upgrade can proceed without the need for upgrading the license. If the license version is lower than 3.3, the license file must be upgraded. A license file change can only be done by the factory. Use part number IA-LIC-CHG to order it. After upgrading the license, the licensed version and any previous version of the I/A Series G3 software can be installed and run in the ENC.

Issue Are all four RS-485 ports licensed for use with BACnet/MSTP on a Niagara G3 ENC-520? Environment Niagara G3 ENC-520 Cause Licensing information about the Niagara G3 will help during installation. Resolution Yes.  At any time, any of the four RS-485 ports can be used without the need for re-licensing.

Issue Can the Personnel Manager be launched without using Continuum Explorer? Environment Continuum CyberStation Cause Require quick launch. Resolution Opening Personnel Manager without opening an existing personnel record. Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Start Windows Program Windows Program: C:\Program Files\Continuum\Launch.exe Command Line Arguments: -C –SPersonnel –Offline “-FRoot” If you want to include a Owner folder location use the following arguments Command Line Arguments: -C –SPersonnel –Offline “-FRoot” “-Proot\FolderName” Result: This will launch Personnel Manager from the button on the graphic with no cardholder information configured.   Create a graphic and set it up to launch for the user upon login Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Open object Object: Select a default cardholder to bring up in Personnel Manager Result: This will launch Personnel Manager from the button on the graphic to the cardholder selected.   Create a graphic button from the main menu that launches Personnel Manager to a specific cardholder If you have made any modification to the Main Continuum menu. Make a copy of the file before editing. i.e. the default is c:\program files\continuum\userprofile\continuum.mnu Right click the main page. Create a new hot spot or edit the Personnel hot spot according to instructions in the Configuration manual on Menu Pages. C:\Program Files\Continuum\Launch.exe -O -SPersonnel "-N\Cardholders\Test_Card" (Note:Cardholders is a folder) Result: Personnel Manager will open to that card   Launch the command line and use the Show command This is similar to option 2 except the button config is different In the Personnel button change the parameters to C:\Program Files\Continuum>cmdline Result: This will launch the Command line Type in Show Test_Card (some cardholder the user knows exists) Ex. R> show test_card Personnel Manager will open to that card   Change the Continuum Menu Personnel button that launches a listview to select a cardholder This is similar to option 2 except the button config is different Create a listview called Launch_PM In the listview place the following qualifier. (Name is like Prompt("Name is like", "*")) For the Personnel button configure the command and arguments lines to be: C:\Program Files\Continuum\Launch.exe -O -Slistview "-N\Launch_PM" Result: This will run the listview, the user can then type in the name of the personnel they know exists after the "*". The listview will find the user and then they can double click on the user in the listview to bring up Personnel Manager.  

Issue Priority Value Select object. The output of Instance 31 of Priority Value Select was always 0 in a MicroNet MN 550 controller. All other instances function correctly. Environment MicroNet MN 550 controller Cause MicroNet 50 controller must be upgraded to firmware version 5.     Resolution This has been corrected with MicroNet 50 controller Firmware version 5 released August 2008. Additional information on firmware 5 can be found in TPA-LOND-08-0014.00

Issue Logic Blocks: Instances 29 & 30 of the Logic Block objects, 8-input AND/OR/NOR/NAND, did not function correctly in an MN550 controller. Instance 29 was always OFF and instance 30 was always ON (even with no inputs connected). Environment MN550 Cause Firmware update is required. Resolution This has been corrected with MicroNet 50 controller Firmware version 5 released August 2008. Additional information on firmware 5 can be found in TPA-LOND-08-0014.00

Issue Control loops linked via antlers. Environment Control objects Cause When a number of Control objects are used for multi loop control. The lower stage output antler of Control loop in some cases failed to function correctly; the Antler node connection going to '---'. Resolution This has been corrected with MicroNet 50 controller Firmware version 5 released August 2008. Additional information on firmware 5 can be found in TPA-LOND-08-0014.00

Issue All NPRs on a site are giving 'Host Lost / Host Restore' alarms, but the TCP/IP network is functioning 100%. Environment I/NET Cause Changes to bin file revisions sometimes include updates to communication Resolution This can be caused by a mis-match in .bin file revisions on all downloadable controllers. Verify all the .bin files in each downloadable controller are from the current I/NET revision at the customer's site. The mis-match can come from a tech loading a .bin file from his laptop (with a different rev than the customer). It can also occur when I/NET is upgraded, but the controllers aren't.

Issue Sending a Service Pin message (Neuron id) thru a Micronet S-Link sensor. Environment MN-S2xx, S3xx, S4xx and S5xx MN-S4-FCS sensors MN-S4HT-FCS sensors Cause The Service PIN message is used to identify the device. There is not a visible service pin button located on the device. Resolution A service pin message (Neuron id) can be sent by pressing the override key (button) for more than 8 seconds (on models MN-S2xx, S3xx, S4xx and S5xx). For the MN-S4-FCS and MN-S4HT-FCS sensors, press the fan on/off key for more than 8 seconds(to send a service pin message). The system override/on-off LED will flash one time indicating the message was sent. Additional information is in the WorkPlace Tech Tool 4.0 User's Guide (F-27255) under the compiling and downloading application (and the uploading) section.