Building Automation Knowledge Base

Issue In Niagara G3, how can an objects value be displayed in a graphic and not its status? Environment Niagara G3 Cause Default BoundLabel properties of the object are set to display the value and status. It must be adjusted to display only the value. Resolution In the BoundLabel properties of the object, the default text format is %.% This displays the value and the status of the object. To display just the object's value, edit the format to %out.value% The object will then display only the present value in the graphic.

Issue In Niagara G3, how can a Boolean object's "False" condition be made to disappear? Environment Niagara G3 Boolean Object Cause BoundLabel properties must be adjusted for the desired operation. Resolution In the BoundLabel properties of the object, right-click on the "visible" field, and choose "Animate" In the Animate window, click on the drop-down for the "Converter Type", and choose "I Boolean to Simple" Click the drop-down for the "False Value", and select "false" Click OK to close the Animate window Click OK to close the BoundLabel properties window Save the graphic Now, when the object has a value of "false," it will not be visible in the graphic.

Issue How many histories can be created in a station and how many records are allowed per history? Environment I/A Series G3 ENC, ENS or SoftJace CComTrolCCWEBor CES Cause Technical product information update. Resolution Regardless of platform type, histories are stored under the station's file system (file:^history/). Stations running on a PC-based system (Enterprise Server or SoftJACE) store the histories in subdirectories using segmented files; this provides improved search capabilities over a flat file system. Stations running on a QNX-based system (ENC) store all of the stations histories in a single compressed file (history.zip). A running station opens the history.zip file in the ENC's ram disk space, the histories are compressed and saved to flash whenever the station is saved. Opening the history.zip file to the ram disk eliminates the need to write to the flash drive each time a record is added to the history file.   When the station needs to write a record to a history, it opens the specific history into the running station (either from the file system if PC-based, or from the ram disk if QNX-based). The open history does contribute to the heap.used of the station. The history service has one property 'max open time' (default 5 minutes) which causes the station to close the history from the running station heap if no records have been written to the history for a time period exceeding the 'max open time'.   Each history extension which is added to the station does add slightly to the station resources because the extension is represented in the bog file. When the history is first enabled, the station creates the history file. The initial file includes a 1600 byte header (defines the configuration parameters) and a single page file of 4096 byte size. When triggered by either the collection interval or COV/COS, a record is added to the page file. When the page file becomes full, additional page files are created based on the capacity configuration of the history. History Record Size by Point Type Point Type bytes/record boolean 13 enum 16 single precision numeric 16 double precision numeric 20 string variable length * *NOTE: A single 'string' record cannot exceed one page (4096 bytes)   Since histories count as file descriptors, there is a physical limitation on the number of histories allowed in a QNX-based ENC station. It is recommended not to exceed 800 histories, given the file descriptor limit of 1000. Note: The platform services view of the QNX-based JACE station includes a property to modify the size of the ram disk within defined limitations. Note that the alarm database is also maintained in the same ram disk space. Exercise caution when modifying the default ram disk size; note that allocating additional memory to the ram disk will limit the memory available for other functions by the QNX OS. Reducing the ram disk size too much could result in history or alarm records not being stored properly and erratic station behavior.

Issue When attempting to run the WorkPlace Tech Tool, Application Menu missing or grayed out. All WorkPlace Tech Tool related entries in the Tools menu are grayed out or missing.   Project Toolbars are not displayed. "Unknown error occurred in an add-on to WorkPlace Tech" Environment WorkPlace Tech Tool 5.7.4 and later versions Microsoft  Visio 2003 or Visio 2007 Microsoft Windows XPsp2, XPsp3,  Vista or Windows 7 Cause Various causes beyond the scope of this article. Resolution There are several different reasons why these entries are grayed out or missing and therefore not selectable. The exact procedure for correcting the problem depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for each third-party add-in. Click [OK] to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WPT, all menu items should be there. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Verify that the box for "Enable COM add-ins" is checked. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click [OK] to apply. Open the Tools menu and select Macros then select "COM Add-ins" Uncheck all third-party add-ins shown in the list. Click [OK] to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there.

Issue WorkPlace Tech Tool 5.7.4 causes Visio to crash when attempting to open some MNL-800 applications.   The problem occurs with MNL-800 applications that were created with WorkPlace Tech version 4.x where the application does not use the hardware schedule function.  Environment WorkPlace Tech Tool version 5.7.4 MNL-800 application file created with WorkPlace Tech Tool version 4.x Hardware schedule has never been enabled using an earlier version of WorkPlace Tech Tool version 5.x Cause Required hardware tag "DayOfWk" missing (normally shown on left tag rail, if unused in the application). Resolution This problem is automatically repaired in WPT version 5.7.5 or newer. While we recommend upgrading WPT to 5.7.5 or newer, you can continue to run WPT 5.7.4 and  correct the problem by taking the file to a computer running WorkPlace Tech version 5.7.3 and following this procedure: Open the existing file in the existing project (or in a new project). Run the Hardware Wizard and click [Next] twice to display the Time & Schedule page. Check the box  "Enable the built-in schedule" then click [Finish] to update the application file with the schedule reference tags. Run the Hardware Wizard a second time and click [Next] twice to display the Time & Schedule page. Un-check the box "Enable the built-in schedule" then click [Finish] to update the application file removing the unused schedule reference tags. Close the application.  This will save the changes to the application file.  If prompted to convert the drawing, do not convert it. The saved application file will be usable in WorkPlace Tech Tool version 5.7.4

Issue The short cut created during the installation of DMS OPRIF 11.6 for DCT will not function. Environment DMS OPRIF 11.6 running in a Windows OS. Cause Unknown. Resolution To work around this issue, run the DCT.BAT located in the DCT folder.  The installed desktop short-cut should be modified by editing the installed short cut line “call c350dct” to “call dct.bat”. To improve system performance when running DCT modify the DCT.BAT file in the DCT folder from “dctgl.exe %1 %2” to “start /low dctgl.exe %1 %2”.

Issue DMS OPRIF 11.6 locks up when attempting to tunnel with Niagara R2 or Niagara G3. Environment OPRIF 11.6 with a Windows OS. Cause The file path becomes too long for the Windows OS. Resolution OPRIF 11.6 by default will install in to the following default directory (x = drive letter): x:\Documents and Settings\username\Local Settings\Temp.  To resolve the excessive path length, install OPRIF into the root folder (i.e. x:\  where "x" is the desired drive) on the computer. The path can be specified in the extraction screen provided during installation.

Issue An Internet Explorer ActiveX function involving the running of Java applets used to display the I/A Series R2 graphics prevents the Java applet from executing properly. Environment I/A Series R2 software release 522.v2, 529 or 532 Cause Microsoft changed the procedure by which Internet Explorer handles third party ActiveX applets, including the Java applets used in the I/A Series R2 system.  This change was applied as an update to all older versions of Internet Explorer and is included in Internet Explorer 8. Resolution There was a workaround provided with the R2 522.v2 release that can be used to prevent this Java applet activation issue from happening. The update consists of adding or modifying some of the information in the station.properties files and applies to both ES based stations and UNC based stations. 1. To update the Enterprise Server / WorkPlace Pro, save and backup the station database accordingly. While in the admin tool, open the station.properties file.  Select menu item Admin Tool -> Host -> Edit File -> System Properties.  Edit the file by adding the following text to the end of the file.   Make sure not to delete the # character as this specifies a comment line.  Save and close the system.properties file (File ->Save). # This is used to disable the IE ActiveX activation fix. If set to # to false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false 2. To update the UNCs, log into the UNC using the Admin Tool and open the station.properties file.  Select menu item Admin Tool -> Host -> Edit File -> System Properties.  Edit the file by adding the following text to the end of the file. Make sure not to delete the # character as this specifies a comment line.  Save and close the system.properties file (File -> Save). # This is used to disable the IE ActiveX activation fix. If set to # to false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false

Issue Changing the nci_PowerUpDly value in the MNL-800 has no effect.  With the nci_PowerUpDly set to 120 seconds in the MNL-800, the outputs turned on after 10 seconds, the default setting. Environment WorkPlace Tech, all versions. MNL-800 Cause The nciPowerUpDly provided in the MNL-800 does not function correctly. The design intent of the nci was to determine the time, in seconds, that must expire following a controller reset before the MN 800 hardware outputs (Digital Outputs and Analog Outputs) are activated. Resolution Be aware that the nciPowerUpDly in the MNL-800 does not work properly, and that the outputs are delayed approximately 10 seconds, regardless of the value entered for nciPowerUpDly.

Issue When attempting to open an I/A Series R2 graphics page, the desired page is not displayed.  A blank gray or white page or page with graphic size gray box may be displayed. Environment Niagara R2 software version 522v2, 529 or 532 installed on station being accessed. Microsoft Internet Explorer being used to access the web based graphic page. Cause A Microsoft Internet Explorer security update causes some Niagara R2 ActiveX objects to be improperly handled and therefore not displayed.  This same Internet Explorer security update is included in all newer versions (7  & 😎 of the Microsoft Internet Explorer browser. Resolution Open the I/A Series R2 station using the R2 Admin Tool. Open the "station.properties" file by selecting "Admin Tool" from the menu then selecting "Host" then "Edit File" then "System.Properties". Add the following four lines to the end of the file (do not delete the # symbol from the beginning of the lines): # This is used to disable the IE ActiveX activation fix. If set to # to false, then the user will be required to click on the applet # before he is able to interact with it (only effects IE users). ie.activex.activation=false   After adding the lines, select "Save" from the "File" menu to save the changes. Reboot or restart the station to allow the change to take effect.  

Issue The license form does not show support for the IA-DRV-MOD (Modbus) driver on a UNC-410. Environment I/A Series R2 UNC-410 Cause License request form for I/A series UNC-410 does not list IA-DRV-MOD as an available option The UNC-410 does not support any serial driver such as Modbus or ASD since it's serial ports are not electrically isolated. A UNC-410 will only allow integration to LON and/or BACnet IP or BACnet Ethernet. Resolution If integration to Modbus is required a UNC-520 should be selected rather than a UNC-410.

Issue I cannot find any published instructions giving the procedure to install an updated version of one of the JAR files on my I/A Series (Niagara) system. Product Line TAC IA Series Environment I/A Series (Niagara) R2 software (any version) installed on a Windows computer Cause An updated version of one of the JAR files installed in an I/A Series (Niagara) R2 system has been published.  The updated file has been downloaded to my computer but there are no instructions on how to install it. Resolution For the purpose of this explanation of the procedure, the following steps reference an update to the "programlib" jar file for release 2.301.522.   Substitute the name of the jar file being updated and release number in the following steps. * NOTE: Before attempting to update a jar file, verify that Windows Explorer is configured to display file type extensions. (See * below for more information). The JAR file update is published, currently on the  as a .zip file containing two files.  Copy the file programLib-2.301.522c.v1.jar.emb to the \niagara\r2.301.522\emb folder. Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.emb to programLib-2.301.522c.v1.jar (removing the .emb extension). Copy the file programLib-2.301.522.v1.jar.nt to the \niagara\r2.301.522\nt folder. Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.nt to programLib-2.301.522c.v1.jar (removing the .nt extension). Copy the file programLib-2.301.522.v1.jar.nt  to the \niagara\r2.301.522\nre\modules folder Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.emb to programLib-2.301.522c.v1.jar (removing the .nt extension). To install the new jar file into a UNC, perform the following procedure after completing steps 1 through 9, above. Start the Niagara 522 version of the Admin Tool. Open a connection to the UNC Select the "Installation" tab then click the [Installation Wizard] button. Select the "emb" folder in the "Select Distribution Directory" window then click [Install] In the "Niagara Remote Installation" window, select the "Configure Modules Only" radio button then click the [Next >] button. Verify that there is a checkmark in the "Upgrade/Add" column for the updated jar file. Click the [Next >] button to continue. Make sure that on the "Database Backup" screen that you do backup the existing database. Continue through the remaining steps and allow the upgrade to install and the station to restart.   * To properly rename the files as described in this procedure, Windows Explorer must be configured to show file type extensions.  To configure this setting or verify it, proceed as follows: Open Windows Explorer by clicking on the My Computer (or Computer) icon on the computer's desktop or by making the selection from the Windows start menu. From the Windows Explorer "Tools" menu, select "Folder Options" Select the "View" tab. Scroll down through the "Advanced Settings" list to locate the entry "Hide extensions for know file types".  Verify that this entry is unchecked. Click the [OK] button to save the change, if any, and exit the Folder Options screen.

Issue When polling BACnet points with an I/A Series R2 (Niagara) UNC, a warning frequently appears in the Standard Output Window that reads "Warning: BACnet Read Property Multiple Error" followed by a property name and device or object name. Environment I/A Series R2 (Niagara) UNC or BACnet Server Cause The warning is reported when a UNC or BACnet Server station polls a BACnet device, and that BACnet device does not support the Read Property Multiple" function.  All data will be retrieved because the station will detect the warning and will poll each requested property, one property at a time. Resolution This is not an issue, just normal operation.  The startup warning messages could be suppressed by setting the device's Read Property Multiple property to false.  However, disabling read property multiple will slow the polling of this device. 

Issue Changing between view and edit modes using Workbench after adding a PxInclude object to a parent px file with a schedule causes Workbench to lockup and fail. A restart of the Workbench application is required. Environment TAC I/A Series G3 ENC-410, ENC-520, and Enterprise Network Server Cause Workbench failed to process the scheduler within the PxInclude. Resolution The issue has been resolved in bajaUi module versions 3.3.34.2, 3.4.64.1, 3.5.34.1 and higher.  The files, bajaui 3.3.34.2 is available for download from The Exchange Download Center.  Download the bajaUi version zip file for the required G3 build. Caution: Always backup the station database before performing any upgrade.   If Enterprise Network Server, stop running station and close the Workbench application.  Extract the file and replace the existing bajaUi jar file in the appropriate modules directory of G3. Start Workbench and start station if Enterprise Network Server. Use the Workbench Platform Software Manager to the upgrade the bajaUi module in ENCs as required.

Issue After allowing Mozilla Firefox web browser to automatically install the latest security updates (v3.6.14), I/A Series (Niagara) R2 or G3 graphic screens cannot be displayed. Environment Mozilla Firefox 3.6.14 Graphic pages served by a UNC/ENC or Enterprise Server/ENS with any version of I/A Series R2 or G3 (Niagara) software Cause Known and documented issue with the way Mozilla Firefox 3.6.14 handles the loading of Java applets. The issue has already been documented on the Mozilla Firefox support forum. Resolution Downgrade to an older version of Mozilla Firefox or use a different compatible web browser. Older Firefox releases are on the Mozilla FTP site (Mozilla FTP).

Issue The I/A Series G3 (AX) Lon Tunneling client does not work in Windows 7 Environment G3 Version 3.5.25 and later Windows 7 Professional OS WPT 5.7.5 and later   Cause The G3 Lon Tunnel client is written to run in Windows XP, and is not designed to run with native Windows 7. Resolution Ensure that the NiagaraAX Lon Tunnel Service is started (Control Panel > Administrative Tools > Services) Locate the vlonax.exe file in the C:\Windows\system32 directory. Right-click on the file, and select Properties In the Properties window, click the "Run this program in compatibility mode for:"  box, and select Windows XP (Service Pack 3) from the drop-down box.  Next, check the "Run this program as an administrator" check box Click OK to accept the changes The Lon Tunnel client is now configured to work in Windows 7.  

Issue R2 UNC station fails to start with the following error messages in the standard output window: FATAL: cannot boot station from sns java.lang.JavaClassNotFoundException: tridiumx.londevices.siebe.MNLRV3 Environment IA Series R2 / UNC-520-2-N Cause The UNC was replaced and the existing station was installed into the new replacement UNC. The existing UNC station database uses object(s) from the lonSiebe module but the lonSiebe module is not installed in the UNC. Resolution Install the lonSiebe module into the UNC and restart the UNC. Install / remove modules into the UNC: Use Admin Tool to connect to the UNC. Go to the 'Installation' tab and click on 'Installation Wizard'. In the Select Distribution Directory dialog, highlight 'emb' and click the 'Install' button. In the Niagara Remote Installation dialog, select 'Configure Modules Only' and click 'Next'. In the Configure Modules dialog box, select the modules to install / remove by selecting in the 'Upgrade/Add' column or the 'Remove' column. Click 'Next when you are finish with the selection. On the Database Backup dialog box, leave the red check mark next to the station database name and click 'Next' to continue. Enter the station user name and password when prompted. In the Niagara License dialog box, click Finish.

Issue Some schedules stop operating correctly after Daylight Savings Time (DST) changeover.  Environment I/A Series G3, all ENS and ENC with builds 3.5.4, 3.4.53.1, 3.3.31.2, 3.2.23.1 or earlier. Cause Any station with a schedule, of any type, with an event set to occur during the "advanced" (missing) hour between 2:00 AM and 3:00 AM on the DST changeover day. The resulting miscalculation of the schedule's "Next Time" or "Next Trigger" time could cause that schedule, or even other schedules in the station, to stop working. This typically affects downstream logic in the station. In some cases it was observed that the CPU usage on an ENC went up to 100% while calculating invalid next event times. Examples A station contains a BooleanSchedule with events at 12:00 AM and then again at 2:05 AM daily. At 12 AM the schedule executes normally and attempts to calculate the next event time. On the second Sunday in March the next event time calculates to a time that does not exist due to the DST change. This causes the Java thread that executes all schedules in the station to become tied up attempting to recalculate the time. A station contains a TriggerSchedule that periodically repeats every 15 minutes, with a range passing through the DST changeover time. On the second Sunday in March the next trigger time calculates to a time that does not exist (say, 2:15 AM). Again, this causes the Java thread that executes all schedules to become tied up attempting to recalculate. Resolution The solution to this issue is to upgrade the schedule.jar file in the platform to one of the versions below, or later. Files are available from The Exchange Extranet.  Release 3.3.31.2 (Download and extract schedule-3.3.34.1) If you are using a build that is higher than the above versions then you will not be affected by this issue.

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue MN-CI revision 4.1 returns an error 511 when sending a “Reset” command to a MicroNet 2000 controller. The controller does reset as commanded. Environment MN-CI rev. 4.1 software, MN-FLO, MN-FLO3T, MN-HPFC Cause The problem is caused because MN-CI rev. 4.1 sends the “Reset” command twice, and temporarily loses communications with the controller. Resolution The error is considered a nuisance and can be ignored.