Building Automation Knowledge Base

Issue How many imported projects may you have in TAC XBuilder? Environment TAC XBuilder Cause There is a limit set in the software Resolution You can not have more than 10 other projects imported into Xbuilder.

Issue Alarm Message stating "TACSERVER-______: Offline" comes into the Vista server regularly Environment Vista Server Xenta Server Vista Classic network Cause When a site has multiple Xenta Server or Vista Server revisions, this alarm will periodically occur as result. Resolution Upgrade all Xenta controllers to the same revision Ensure that this revision matches the revision of the Vista Server.

Issue IOU module(s) attached to CX9900 or CX9680 keep dying, some with blinking status light others just show online but cannot drive outputs on it. Environment CX9900 CX9680 Lon IOU modules Cause Static electricity discharging on the module via wire of Fan drive controller. Resolution Disconnect offending wire at the source. Re-route wire so it does not cause static discharge on the IOU modules. Make sure the IOU modules are properly attached to earth ground as per the installation instruction.

Issue What was the last version of Windows supported by Wonderware for Intelligent Buildings (WIBS) version 1.1 service pack 3? Environment WIBS 1.1 InVue 1.1 Cause A customer must replace his computer hardware and will make efforts to obtain the operating system supported by WIBS / InVue. Resolution The last operating system supported was Windows 2000 service pack 3.  There have been several instances of it working on Windows 2000 service pack 4 and Windows XP service pack 3. In all three instances, virtual machines were not tested. Windows XP and Windows 7 have not been tested and will not be tested.

Issue What speed and duplex do the DMS and GCM Ethernet NIMs operate? Environment DMS-ETH-001 GCM-ETH-001 Cause Network troubleshooting Resolution Both NIMs (network interface modules) adhere to the IEEE 802.3 standard as written in the early 1990s. The port speed is 10 Mbps at half-duplex.

Issue Can a Netcontroller II be used to communicate directly to BACnet MS/TP devices? Environment BACnet MS/TP RS-485 XDriver Netcontroller 2, NC2 bCX9640 Cause No X Driver is listed for BACnet MS/TP. Resolution There is no X Driver available for the BACnet MS/TP protocol to allow a NC2 to communicate to 3rd party MS/TP devices. However a bCX1 4040 can directly communicate to BACnet MS/TP on its Comm2 and is BTL listed to confirm compatibility. Also a bCX1 9640 can be converted to a 4040 by flashing it with the 4040 flash file available on the Extranet.

Issue Will a M1500 actuator fit onto a V232 valve? Environment M1500 Forta V232 Venta Cause Application assistance on Forta M1500 and Venta series V232 valve. Resolution The M1500 will fit, but since the V232 is only available in DN25,32, 40 and 50 size, we recommend using the smaller M400 or M800 instead.

Issue Replacement for Satchwell DDT0001 Duct Temperature Sensor.  Environment Satchwell Sensor DDT DDT0001 Cause Obsolescence of Satchwell DDT0001 Duct Temperature Sensor. Resolution Replace Satchwell DDT0001 Duct Temperature Sensor with Schneider Electric STD660 Duct Temperature Sensor. The Schneider Electric STD660 provides the same functionality as the Satchwell DDT0001, differing only in its appearance, dimensions and terminal identification. The Schneider Electric STD660 Terminals are not polarised.    

Issue Viewing white screens in R2 when browsing web pages in Internet Explorer 9   Environment R2 and G3 Niagara Cause Java conflict with Internet Explorer 9 Resolution Disable java option next generation plug-in: Open Java console under Control Panel Menu Go to Advance options Tab Expand Java Plug-in Uncheck Enable the next generation Java Plug-in Restart Browser for changes to take effect

Issue Customer does not have Microsoft Outlook/Exchange, only Lotus Notes/Domino. Environment Keywords: Email, Page, Lotus Notes Cause Customer wants email and paging of alarms but does not use Microsoft Outlook and Exchange. Resolution Lotus Notes is not a supported application for emailing or paging of alarms. Microsoft Outlook with Exchange is the only supported program for this application.

Issue When converting a Niagara R2 server station from xml to db, the conversion fails with the following message: ERROR: c:\niagara\r.301.529.v1\stations\PMHBASSERVER\config.xml(865566,98):  Could not create node "tridium.apps.ProgramNode".tridium.foundation.IllegalChildException E_ILLEGAL_CHILD_DUP_NAME {Command}    at tridium.foundation.node.NodeLifeCycle.pasteErrorCheck(NodeLifeCycle.java:153)    at tridium.foundation.node.NodeLifeCycle.paste(NodeLifeCycle.java:68)    at tridium.foundation.prism.Prism.commitTransactionImpl(Prism.java:1484)    at tridium.foundation.prism.Prism.commitTransaction(Prism.java:779)    at tridium.foundation.prism.NodeTransaction.commit(NodeTransaction.java:76)    at tridium.xml.node.NodeHandler.createNode(NodeHandler.java:105)    at tridium.xml.node.NodeHandler. (NodeHandler.java:42)    at tridium.xml.node.NodeHandler.startElement(NodeHandler.java:140)    at tridium.xml.TParser.doSTag(TParser.java:225)    at textuality.lark.Lark.reader(Lark.java)    at textuality.lark.Lark.readXML(Lark.java)    at tridium.xml.TParser.parse(TParser.java:121)    at tridium.tools.DbAdmin.readXml(DbAdmin.java:472)    at tridium.tools.DbAdmin.convert(DbAdmin.java:292)    at tridium.tools.DbAdmin.main(DbAdmin.java:168)    at tridium.tools.DbAdmin.main(DbAdmin.java:122)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)    at java.lang.reflect.Method.invoke(Unknown Source)    at tridium.nre.Nre.mainImpl(Nre.java:663)    at tridium.nre.Nre.main(Nre.java:603) Parse of XML failed.  ----- End of input -----   Environment Niagara R2 Cause The conversion fails due to two program objects having duplicate names. Resolution Open the xml file using a xml editor (like Notepad++).  Navigate to line # 865566, character # 98 and identify the program object's name. Rename the program object by adding an additional character (like a number '1' or a letter 'a').  Save and close. Run the conversion to db again.

Issue A specific license module is required for running reports in Excel from TAC Vista Environment Microsoft Excel 2003 / 2007 / XP Report generator : Report Generator...........................000882231 Report Generator – Upgrade..................000883231 Report Generator – 1 year subscription ..........000884230 TAC Vista version 5.1.X  Cause A separate license module for Vista Reports Generator is included in some license packages, but is sometimes required to be ordered separately if Reports are required as a feature. Resolution Part no 000882231 is for the Report Generator license in Vista version 5.1.X.

Issue Detection of a "security threat" or vulnerability by Microsoft Security Essentials when downloading I/A Series G3 Environment I/A Series G3 (all versions up to 3.6.31) Cause Recently, Oracle(R) has issued a critical patch update to address security vulnerabilities that currently exist within all versions of Java SE (Standard Edition).  Due to this patch update, Microsoft Security Essential scans have been updated to identify this as security vulnerability.  The detection by Microsoft Essentials is not a virus but a warning of a potential vulnerability that could be exploited for malicious use if precautions are not taken (e.g. firewalls, strong passwords, etc.). It is likely that McAfee, Norton, and other antivirus programs will also be issuing updates which identify this as vulnerability.  If the Niagara JRE is identified as vulnerability, it could lock down or quarantine the JRE, thus rendering Niagara unable to operate. Note: Oracle(R) is the owner of Java since 2009, although you still often see "Sun Hotspot" in references. Resolution In most cases, it is not critical that a new JRE (Java Runtime Environment) release be installed for I/A Series G3.  Typically, G3 resides behind a firewall and / or strong passwords are being used however, if required and/or directed by Product Support, the following procedure can be used to manually update the JRE on the Windows based Enterprise Server, Engineering Workstation, or I/A Series G3 ENC (Soft JACE) platforms.  JRE version 6 (update 31 or higher) is required. Note in steps below, / is your I/A Series G3 installation folder.     Download and install the desired JRE version 6 (update 31 or higher) from the Oracle web site.  For example,  Java SE Runtime Environment 6 Update 32 can be downloaded from http://www.oracle.com/technetwork/java/javase/downloads/index.html.  Select and download Windows x86 Offline (32-bit) for 32-bit platforms or Windows x64 (64-bit) for 64-bit platforms. The default installation folder is /Program Files/Java/jre(x) where (x) is the version. Stop all running Niagara stations and exit all Workbench instances. From a Niagara Console window, execute: plat uninstalldaemon Rename //jre to //jre_old Copy /Program Files/Java/jre(x) to / and make sure to rename the copied folder to jre. Copy //jre_old/lib/ext/mail.jar to //jre/lib/ext/mail.jar Copy //jre_old/jreVersion.xml to //jre/jreVersion.xml Update the version="n.n.n.n" string in the //jre/jreVersion.xml file to match the new JRE version. From a Niagara Console window, execute: plat installdaemon Restart Workbench and any stations.      

Issue UNC station is frequently rebooting on its own and occasionally reports "Station Watchdog Timeout" in the error log. Environment I/A Series UNC 510 or UNC-520 Cause System Monitor task is causing the UNC to reboot. Typically this is caused by incorrect information in the drivers.properties file of the UNC. Resolution This issue can be corrected by editing the drivers.properties file in the UNC. To edit this file, Log into the UNC using the Admin tool. Select the Installation tab the select [Edit drivers.properties].  The file will be displayed in the text editor. Look for a line that reads sysmon.enable=true If the line is present, edit the line changing so that it reads sysmon.enable=false If the line is NOT present, add the line sysmon.enable=false at the end of the file. Select Save from the File menu to save the changes. Select Close from the File menu to close the editor. After editing the file, the station must be restarted to allow the change to take effect.

Issue A Programmable object must respond to a DI change in state, and then reset ready for the next change. Product Line Satchwell Sigma Environment Programmable Digital states Status DI Cause The programmable object will monitor the state of a number of other digital objects and if they change state, then an external alarm enunciator via a digital output point, will be enabled. To allow subsequent changes to be seen on the same point, the object value must return to zero, even if the changed state remains on after 60 seconds. Resolution The following object will check the state of four objects, but others can be added if required. Object numbers 33 - 37 are the monitored objects. Timer is set to 60 seconds, but can be set as required. (Line 110) Alarm priority can be set as required. (Line 120) 10 XInt = 0 20 IF POINT 0|33 ON THEN XINT = XINT + 1 30 IF POINT 0|35 ON THEN XINT = XINT + 1 40 IF POINT 0|36 ON THEN XINT = XINT + 1 50 IF POINT 0|37 ON THEN XINT = XINT + 1 60 IF XINT > YINT THEN GOTO 100 70 IF TIME LEFT THEN GOTO 120 80 IF XINT = 0 THEN YINT = 0 90 RETURN FALSE "reset" 100 YINT = XINT 110 SET TIMER 60 120 ALARM 1 130 RETURN TRUE "Alarm"  

Issue Replacement for Satchwell DR2253 Temperature Sensor. Environment Satchwell Sensor DR DR2253 Cause Obsolescence of Satchwell DR2253 Temperature Sensor. Resolution The Satchwell DR2253 Temperature Sensor is replaced with the Schneider Electric STR614 Temperature Sensor. The Schneider Electric STR614 provides the same functionality as the Satchwell DR2253, differing only in its appearance, dimensions and terminal identification. The Schneider Electric STR614 terminals are not polarised.

Issue When using STR101 to STR-107 connected to a TAC Xenta 121-FC, the LED Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC, which is the only analog output on the TAC Xenta 121-FC device. Environment TAC Xenta 120-FC STR-101 STR-102 STR-103 STR-104 STR-105 STR-106 STR-107 Cause When using any of STR-101 to STR-107 connected to a TAC Xenta 121-FC, the LED Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC device, which is the only analog output on the TAC Xenta 121-FC device. Resolution In ZBuilder, it is possible to move the Status LED from the default location at Y1 to K1-4. In this case you also need to have an external power supply with 5 Volt DC for the LED indicator. It is also possible to use 24 Volt AC power supply for the LED indicator, however this will make an incorrect temperature reading of about 0.5 degree C. In this case, add a 5 kΩ resistance (4.7 - 5,1 kΩ) ¼W in one of three possible positions: Between G and KC1 Between K1 and LED 16 Between Mx 15 and M. The resistor must be placed outside the STR device.

Issue In some applications a spring return actuator is requested/required Environment VF208W Cause application requirement Resolution No spring return actuator is currently available for VF208W. However, there is a plan for this in the near future.

Issue Since the M-SM actuator no longer is available, a replacement is requested. Environment M-SM 8700000000 MD20B-24 8751025000 AUX Switches: Old: S1-B 9141000000 S2-BB 9141010000 New: MD-S1 9141060000 MD-S2 9141061000 Cause Replacing obsolete actuator  Resolution The M-SM is replaced by the MD20B-24. If AUX switches are used, S1-B is replaced by MD-S1, and S2-BB is replaced by MD-S2.

Issue Unable to run the  Database Initialization application. Receive error stating that "You must have NT local administrator access...". Even after logging in as a local administrator the same error occurs. Environment Continuum Cyberstation Windows Server 2008 Domain Cause The instances of this that have been reported all seem to be where there has been an upgrade to or new installation of Windows Server 2008 where the system is part of a Domain. It is not entirely understood at this time but something to do with the Domain policies being pushed down to the Workstations is causing problems.   Resolution Until the cause can be properly identified, a workaround that has worked in most cases has been to create/setup a local Administrator account and then run Database Initialization as an Administrator. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator". With the EUR domain in the UK the following has been found - XP                 - "Right click" on the "Database Initialization shortcut" and “Run As” use local admin - Windows 7 - "Shift" & "Right click" on the "Database Initialization shortcut" and “Run as a different user”, use local admin