Building Automation Knowledge Base

Issue No values in a TAC Xenta Server Trend log in TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Trend Logs Vista Workstation Cause The Xenta Server trend logs have not been enabled in the Vista Workstation. Resolution To be able to view and store TAC Xenta Server trend logs in TAC Vista: Find the trend log in TAC Vista Workstation Right click and select Properties. There are two different control tabs here, Vista control and Xenta control. Xenta control turns on and off the actual log in the Xenta server (same as in XBuilder). Vista control decides if the Log gets stored in TAC Vista's SQL database and if the log can be viewed from Workstation. In the Vista control tab change Activate to manual-on. Now you can see the logs from TAC Vista.

Issue Does TAC Vistas new OPC server (version 1.1.0) that was released with TAC Vista 5.1 only work with Vista 5.1? Environment Vista 5.0 OPC server  1.1.0 Cause Because the new version of OPC comes with Vista 5.1, it may be assumed that it is not fully backwards compatible. Resolution OPC server version 1.1.0 is compatible with all Vista 5 versions.

Issue When trying to access TAC Webstation a message saying 'Service unavailable' occurs. Environment Webstation Cause The problem is that the application pool in the IIS where TAC Vista Webstation is located is closed down when trying to access it. Resolution The workaround for this is: Go to Properties for the application pool which contains TAC Vista Webstation Choose Identity and change the predefined 'Network service' to 'local system'

Issue Getting error message "page cannot be found" when trying to open TAC Vista Webstation. Environment Windows 2003 Server and IIS 6.0 Cause Enable ASP.NET in Web Service Extensions. Resolution Open the IIS 6.0 (Internet information services). Click on "Web Service Extensions" and make sure ASP.NET is "Allowed". http://www.youtube.com/watch?v=r62cbZx4vhQ NOTE: XP Uses IIS 5.1 and Web Services Extensions do not exists in this version of IIS.

Issue How to program a limit block for use in Niagara G3. Environment Niagara G3 Cause Limit are configure using the Reset object in the kitControl palette in the Math folder. Resolution Use the Reset object found in the kitControl palette in the Math folder.  To use it set the "Input Low Limit" and the "Output Low Limit" to the lowest desired output.  Set the "Input High Limit" and "Output High Limit" to the highest desire value. kitControl-Reset This component performs a linear “reset” on the inA value. Reset is available in the Math folder of the kitControl palette. Reset operation is defined by the following four slots: Input Low Limit — must be less than the Input High Limit Input High Limit — must be greater than the Input Low Limit Output Low Limit — may (or may not) be greater than the Output High Limit Output High Limit — may (or may not) be greater than the Output Low Limit For example, a Reset object is used to establish a hot water control setpoint, based on the outside air temperature at inA. When the outside air temperature is 0°F, the hot water setpoint is 200°F. When the outside air temperature is 75°F, the hot water setpoint is 100°F. The Reset object is configured as: Input Low Limit = 0.0 Input High Limit = 75.0 Output Low Limit = 200.0 Output High Limit = 100.0 Whenever the inA value is beyond the input limits, the output is limited by the corresponding output limit (in this case, 200 at 0°F or below, 100 at 75°F or above). When the input is at an intermediate value, the output scales linearly. For example, when the outside air temperature is at 38.2°F, the Reset output is 149.1°F.

Issue Warning - Platform running low on RAM disk space (Niagara G3 Release 3.2.5 and higher) Environment I/A Series G3 (typically embedded ENC/JACE platforms) Cause Low disk warning for history RAM disk A station fault will be generated if the free disk space on the history / alarm RAM disk falls below the minimum percentage specified on the PlatformServices property sheet. Resolution During station startup,  /niagara/bin/ramdisk.sh is invoked to create the RAM disk partition.   The RAM disk is named /aram0 and symbolic links are created from /alarm -> /aram0/alarm /history -> /aram0/history.  After the RAM disk is created it is populated with the contents of the alarm.zip and history.zip files.  During a station save or shutdown, the alarm and history files on the RAM disk are zipped and stored under the station directory in alarm/alarm.zip and history/history.zip.  If this fault occurs, users should take one or more of the following actions to prevent history/alarm data from being lost: Reduce number of histories that you are collecting Reduce number of records in each history Increase history RAM disk system (requires reboot). Action 3, above, will reduce the available system memory and should only be taken if there is sufficient free system memory.  Rather than writing history and alarm records directly to persistent storage, a Niagara G3 station stores history and alarm records in a RAM disk. This approach reduces the number and frequency of writes to flash.  Be careful not to increase too much otherwise you risk consuming all the available JACE free RAM causing the niagarad to crash.  Review the free system memory and make sure to leave a buffer of at least 1 MB of free RAM.  The RAM disk size is stored in /niagara/lib/platform.bog and can be adjusted using Services -> Platform Services. After reducing the number of histories, etc. the RAM disk will still indicate a low warning message until the unused histories are removed from the history storage.  Delete the unused histories using the Database Maintenance view on the history component view within the station.

Issue Configuring the LON Router (LPR-10) within a Niagara R2 System Environment Niagara R2 system LPR-10 Cause Procedure to configure LON Router (LPR-10) in Niagara R2. Resolution Since most LonWorks networks are unmanaged (that is, managed only by the Niagara station's Lon Device Manager), use the procedure beginning on page A-9, of the Niagara LonWorks Integration Guide, to define the LonWorks network.  Before beginning this process, cut the existing LonRouter and Channel1 from the station. Set the status of all of the Lon devices to "Unknown". The most important part of this process is defining the router and associated channels before beginning any of the automated processes using the LonDeviceManager. Ensure four LON-TERM-2 devices (LON BUS Topology Terminators) are installed. One at each end of the trunk and one at the near end of the router and one at the far end of the router.

Issue Is Niagara R2 compatible with Windows Server 2003? Environment Niagara R2 Windows Server 2003 Cause Compatibility Resolution Niagara version 514 and higher was officially certified to operate with Windows NT, Windows XP, and Windows Server 2003. As a side note, if using Windows Server 2003, there are two issues to be aware: Windows Server will use IIS services causing a conflict with TCP port 80. This will have to be addressed when engineering the station database. There is an issue with Niagara and Windows Server 2003. Tridium released a Tech Tip as follows: R2 Web Supervisor on Windows 2003 Service Pack JDE will not start. If fui.exe is run from within the Windows command prompt, the following error is displayed: Error occurred during initialization of VM Could not reserve enough space for object heap. The problem is limited to instances where the user is accessing the computer with a Remote Desktop connection. On 8/8/2006, Microsoft issued an update KB921883 which unintentionally causes problems with applications that use large amounts of contiguous memory on a Windows Server 2003 Service Pack 1-based computer. There is a Hotfix now available to resolve the issues generated by this update. Hotfix KB924054.

Issue Getting an error when adding the ASD service to a Niagara R2 station Environment Niagara R2 ibsAsd driver Cause The error indicates that the serialDriver jar file has not been installed. Resolution The ibsAsd driver will not function without the serialDriver jar file. The serialDriver includes communications class files needed to support ibsAsd. To correct the issue, use the Installation Wizard in the admin tool to install the serialDriver jar. Caution: The station must have the Serial Driver installed. It is recommended that the 516b version released in July 2006 be used. The jar files as well as the ASD driver documentation (F-27429) are available for download from The Exchange Download Center

Issue How can two stations run concurrently on a Niagara R2 computer? Product Line TAC IA Series Environment Niagara R2 Cause Operate two stations by running each station on different port. Resolution In order to run two stations simultaneously, set up one of the stations to run on a different port. By default, the station database is set up to run on port 80. Attempting to start a second station will fail if it finds the port unavailable. Open the second station offline; right click on the station root, and select properties. On the configuration tab, set the httpPort to another value (e.g. 8080). Save and close the station database. The station should now start without conflict. Remember to open the station with the IP address followed by the port (e.g. 10.1.146.25:8080). Also, for live external links to work, the address books would have to match (adding the port number).

Issue Lifecycle margin versus actual station database resource count in Niagara R2. Environment Niagara R2 Cause When pasting objects that are over the maximum allowance size, it will not paste the object because the copy or cut maximum size is depend on the Lifecycle margin. Resolution The UNC-410, UNC-510, and UNC-520 platforms all have a resource count limitation of 600,000.  The TRD-NXT has a resource count limit of 2,500,000. The total number of available resources is the same regardless of support for Web services. The (Search > Resource Count) function under the WorkPlace Pro Search menu item will count the number of resources used. The count is performed from the object currently selected on the JDE tree and includes all child objects. By selecting the station's root name, the resource value for the entire station database will be provided. The dialog box with the information provides the calculated actual Resource count and also will indicate the Lifecycle margin: 20,000. The Lifecycle margin is a JDE term that specifies the maximum size (in resource count) of any “cut” or “copy” permitted in a running station. A cut or copy effectively creates a temporary new tree of objects within the memory of the host. This mechanism is used to support the JDE's “undo” operation (Edit > Undo). As an example, try to cut & paste something and it won't be allowed because of resources.  After checking, for instance, that there is a 43,000 resource count with a lifecycle margin of 20,000, what is happening is that the cut and paste has a total resource count higher than 20,000 which is the max. Perform the cut and paste in smaller portions.

Issue Communications issues with a Niagara R2 UNC-520 and Viconics VT-76xx BACnet thermostats Environment Niagara R2 UNC-520 Viconics VT-76xx BACnet Cause Viconics VT-76xx BACnet thermostats do not support COV. Resolution Use the admin tool servlet to set useCOV to false.

Issue Filter an alarm listview by EventNotification Environment Alarm Listview Cause The way to do this is to create a listview of class AlarmEvents and put the columns you want displayed on the columns tab. Resolution To set up the filtering go to the Qualifiers Tab and under the database section select the checkbox "Advanced Database Qualifier". In the qualifier box you will need to type in the statement below EventNotificationClassID is like (put full path and name of the EventNotification here) id   You need to manually type the above in the qualifier box because if you use the wizard the attribute is not listed correctly.

Issue What do the network mismatch errors in WorkPlace Commissioning Tool mean? Environment  WorkPlace Commissioning Tool Cause Information to troubleshoot network mismatch errors in WorkPlace Commissioning Tool. Resolution These errors are described in the WorkPlace Commissioning Tool and Flow Balance Tool Users Guide (F-27358) page 175.

Issue Connection to a DMS MicroPlex MSC-NC is successful. However, when accessing a networked MicroSmart controller, the connection attempt fails. Environment DMS MicroPlex MSC-NC MicroSmart Controller Cause Flash ROM in the MSC-NC Resolution Reload of the flash in the MSC-NC: Power down Jump J1 (near processor) Power up. Connect with DCT Remove J1 jumper f. Do “Alt-L” as this will start installation of Flash ROM. The above will also take care of these problem issues: Back door password (lack of) "Ghost" controllers that are not there None standard service alarm code (sample: 44+service alarm44144144/144)

Issue After installing Windows XP Service Pack 2 and rebooting, Niagara R2 WorkPlace Pro Admin Tool is not accessible as well as the station via Internet Explorer (browser). Environment Niagara R2 WorkPlace Pro Update to Windows XP Service Pack 2 Cause The upgrade includes Firewall software that blocks the ports that Niagara uses to communicate. Resolution When upgrading to Windows XP SP2, Microsoft introduced a set of security technologies that help to improve the ability of computers running Windows XP to withstand malicious attacks, especially those from viruses and worms. To solve the problem create an exception in the firewall to open the ports that Niagara uses to communicate. At a minimum have TCP 3011 & TCP 80 opened.

Issue How do I configure oBIX (Open Building Information Exchange) to integrate a Niagara R2 station and a Niagara G3 station? Product Line TAC IA Series Environment Niagara R2 version 5.22 and later Niagara G3 version 3.4 and later Cause This document provides an overview of the integration of an R2 UNC to a G3 Enterprise Server using oBIX (Open Building Information Exchange). Resolution The R2 UNC must be licensed for "obix" and the obix jar file must be in the remote library of the UNC. Add the "ObixService" to the Services container of the UNC. Re-boot the UNC. The G3 Enterprise Server must be licensed for obix. Double-click the Drivers Component in the G3 Enterprise Server to open the Driver Manager. Add an Obix Network. Double-click the new Obix Network to open the Obix Client Manager. Click the "New" button at the bottom. Add a new "R2 Obix Client." Double-click the new R2 Obix Client. Enter a name for the UNC. In the Lobby field, enter http://, followed by the IP Address of the UNC, followed by "/obix". Enter the UNC's station username and password. Click OK. After a few seconds the state of the client should be "Attached." Expand the UNC Device in the Nav Tree. Double-click the points component to open the Obix Point Manager. Click the "Discover" button. After the points are discovered, expand "Lobby" and then "Config." (The Lobby is the root of a Server's oBIX object tree.) You can now scroll to see the containers and objects in the UNC's station. You can add UNC points to the G3 Enterprise Server's database in the usual manner. If you wish to have "link control" of objects in the UNC from the G3 Enterprise Server, then add an "Obix Export" object in the R2 Logic. These Obix Export Objects (analog, binary or multistate) are found in the Obix jar file in the remote library of the R2 UNC. Link pOut of the Export Object to pIn (if available) of the object you wish to control. Then link sOut of the R2 object back to the feedbackInput (fIn) of the export object. If no Priority Input is available on the R2 object, simply link the sOut of the Export Object to the sIn of the R2 object. No link to the feedbackInput of the Export Object is required. Return to the G3 Enterprise Server and discover the points in the R2 UNC. When adding the Export Point to the obixNetwork, the Export Objects default to type "Numeric Writable" so they can be commanded from the G2 Enterprise Server.

Issue Can certain Analog Input values be read with up to 3 decimal places in WorkPlace Tech? Environment WorkPlace Tech MNL series MNB series MicroNet 2000 Network 8000 Cause The MNL, MNB, MicroNet 2000 and Network 8000 controllers have the capability of working with values from -163.83 to 16,383 and never use more than 2 digits after the decimal place. This is something that all of the controllers have used for many years. This is documented on page 25 of WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). Resolution In certain applications where it is necessary to read very small values beyond 2 decimals, a work around has been used.  The technique should only be used by those who fully understand the concept and its implementation.  The technique to overcome this is to set the output scaling factors of the Analog Input object (in WorkPlace Tech) to values at a factor of 10 or 100 (or other suitable number) thus giving the resolution and therefore (no loss of) accuracy that is required.  This requires scaling the value down by the same factor at the head-end (or wherever) to get the proper and accurate reading.  Multiply the scale properties by a factor then divide by the same factor for display or logic calculations. Example:  A pressure transmitter that reads a pressure range of -.25 to .25 in. wc at 4 to 20 mA, the Analog Input properties needed for such a transmitter would be as in this table: Input Low Value:     4 mA Scaled Low Value:  -.25 inwc Input high Value:     20 mA Scaled High Value: .25 inwc There is an issue with a device that has such small sampled values.  The controllers can only register at most 2 digits after the decimal.  Therefore the controller can be fooled by setting the properties such that the controller thinks that it has a device transmitter attached that reads pressures from -25 to 25 In. WC.  This is a factor of 100 and all values would be 100 times larger than the true reading.  This of course needs to be accounted for in any calculations and GUIs.  The properties for this would be as in this table. Input Low Value:      4 mA Scaled Low Value:  -25 inwc Input high Value:     20 mA Scaled High Value: 25 inwc In using this technique, remember to factor the number when displaying it or using it with other logic.  Since the controller can use negative numbers no smaller than -163.83, no properties can be entered smaller than that value.  In the table below the same transmitter is used but a factor of 1000 is used for the properties.  This can not work due to the scaled low value being less than -163.83. Input Low Value:     4mA Scaled Low Value: -250 inwc Input high Value:     20 mA Scaled High Value: 250 inwc The workaround is well proven and sufficient to satisfy needs.

Issue What does the ReassertDaemon error in a Niagara R2 UNC Standard Output Window mean? Environment Niagara R2 Cause The UNC station is unable to log into the Enterprise Server station as a client to update the slave schedule information. Resolution ERROR: ReassertDaemon [SubscriptionModule] java.lang.NullPointerException at tridium.foundation.node.Node.set (bytecode 5) at tridium.foundation.node.ExecutableNode.setViaSubscription (bytecode 33) at tridium.foundation.prism.Subscription.updateValue (bytecode 10) at tridium.foundation.prism.Subscription.reassert (bytecode 106) at tridium.foundation.prism.SubscriptionsTable.reassert (bytecode 18) at tridium.foundation.prism.SubscriptionModule$ReassertDaemon.run (bytecode 79) The UNC is unable to subscribe to the server and continues to retry. Eventually, a message indicates too many pending connections. The usual suspect are the firewalls (Windows, anti-virus software, etc.) blocking connections into the Enterprise Server. The server will be able to connect to the UNC but the UNC will not be able to connect into the server. The Enterprise Server needs to have its Address Book updated to include all the UNC’s IP Addresses, Usernames and Passwords.

Issue Is there any way to setup Niagara R2 station passwords such that they expire and must be changed on a periodic basis? Environment Niagara R2 station Cause No settings to define password expiration. Resolution This feature is not available in Niagara R2.