Building Automation Knowledge Base

Issue Why are only three tabs viewable when the Properties page of a MNB controller is opened using version 5.7.1 (and newer) of the WorkPlace Commissioning Tool? Environment MNB controller WorkPlace Commissioning Tool Cause Beginning with version 5.7.1 of the WorkPlace Commissioning tool, only a subset of the controller configuration data is requested when initially browsing for BACnet devices using the selected communications protocol. Without additional information, the "Device Properties" program module does not know what kind of device (controller model) is being accessed. Without the model information, only the generic "General", "BBMD" and "Advanced" device information tabs are displayed. This is the same information displayed when third-party BACnet controllers are accessed. Resolution There are two options for acquiring the additional "Extended Device Data". Turn on the "Auto Acquire Extended Data" option.  WorkPlace Commissioning Tool will automatically request the extended data for those devices shown in the device list. Right-click the specific device entry in the list and select "Refresh" from the displayed menu.   Once the extended data has been retrieved from a BACnet device, the Properties window for that device will display with all the appropriate property tabs shown.

Issue WorkPlace Tech "Application Menu" and some "Tools Menu" entries are missing or grayed out. 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.  Environment WorkPlace Tech Tool 4.0.x, 5.7.0 - 5.7.3 Microsoft Visio 2002, 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. There are two parts to the procedure to correct the problem, disabling COM addins and deleting the Visio directory cache. The exact procedure 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 Options. 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 all third party add-ins. 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, 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 WorkPlace Tech, all menu items should be there. If some or all of the WorkPlace Tech Tool menu entries are still grayed out, repeat these steps, disabling all COM addins. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" 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, 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. Workplace Tech with Visio 2002 Open Visio 2002 Open the Tools menu. Select Options, then Advanced. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2002. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username >\AppData\Local\Microsoft\Visio\VISIO.BIN If running Windows XP, delete the file c:\Documents and Settings\< username >\Local Settings\Application Data\Microsoft\Visio\VISIO.BIN Open Visio 2002 and wait while Visio updates its directory cache. The process is complete when the "Choose Drawing Type" window is displayed. Close Visio 2002 Open WPT, all menu items should be there. 

Issue Can the Network 8000 Microflo or CVV-80000 series controller be integrated using the Niagara R2 GCM driver? Environment Niagara R2 Network 8000 CVV-80000 Cause Information on integrating Network 8000 Microflo or CVV-80000 series using GCM driver Resolution Yes. Architecturally, it connects to the GCS bus of a GCM-84000 controller. The GCM database will contain VVBOX blocks which interact with the Microflo controllers. The VVBOX block can be read from and written to using GcmGeneric objects in a UNC station.

Issue What's the latest version available in Pocket I/A? What make/model of handheld device was used in testing? Environment Pocket I/A Cause Would like to confirm the device is running the latest version of Pocket I/A. Resolution Pocket I/A Version 4.1 (Release B) is an update to previous versions of Pocket I/A to support the Microsoft Windows Mobile 5.0 Operating System used with newer handhelds. The features and applications in previous versions of Pocket I/A will continue to operate in Pocket I/A Version 4.1 (Release B). This version was tested using an HP IPAQ HX 2490B with MSMobile 5.0 operating system. Pocket I/A 4.1 can be downloaded from The Exchange Download Center.

Issue When "learning" an MNB controller into a Niagara R2 UNC station that has an MN-Sx sensor, a read failure occurs and several WARNING messages appear  in the Standard Output Window. These errors did not occur in uploads with BACnet jar files previous to 527i. Environment MNB controller Niagara R2 UNC station MN-Sx sensor BACnet jar file (527i) Cause A change that occurred in the 527i BACnet jar file. Resolution These messages occur with BACnet jar file 527i and later and are legitimate. They are a result of uploading the S_LK_Display1 object. The read failure for description property occurs because there is no description in this object and the subsequent warnings are because Niagara R2 does not support the files listed. This was true of previous BACnet jars as well but was not reported.

Issue How to export histories from a Niagara G3 ENC to a Niagara G3 Enterprise Network Server (ENS) Environment I/A Series G3 (Niagara) ENC and Enterprise Network Server (ENS). Cause Technical tip. Resolution To export a history to the ENS, expand the ENC's Niagara network and locate the ENS station. Expand the station, right-click Histories, and choose "View > Niagara History Export Manager"  Click the "Discover" button to discover the histories in the ENC station. Highlight the desired histories, and click the "Add" button. Select the desired Execution Time (Daily, Manual, Interval), set the "Enabled" field to True, then click OK.  Send initial history data to the ENS by clicking on the "Archive" button. In the Nav tree, open the ENS station. Expand the server's History folder. Verify that the histories from the ENC station are there.

Issue The Workplace Tech Tool 4.0 Engineering Guide (F-27254), Chapter 3 - "S-Link Sensor Tags", states "PBOccMode" is 0 following a download or reset.  This is incorrect.  Following a download or reset, the PBOccMode tag comes back as NA. Environment Lon and BACnet controllers with MN stats Cause error in documentation Resolution There is a work around if a 0 is required following a download or reset. If the existing logic is not able to handle the "NA", then link PBOccMode into Input[1] of a two input "Priority Object". Set Input[2] to a constant of 0. The Priority object will output a 0 following a download or reset.

Issue When creating piping graphics using the Niagara G3 kitPxHvac palette, how can elbows and tees be lined up exactly? Environment Niagara G3 Cause To line up pipe and elbow, snap option must be turned off. Resolution Turn off “snap” and place the objects close to each other. Then, while holding down the “Ctrl” button, use the arrow keys to move the selected pipe or elbow until it lines up perfectly.

Issue The Niagara G3 Microsmart Driver Installation and Configuration Guide (F-27523) lists "Applicable Documentation" on page iv. Is that documentation available for download? Environment Niagara G3 MicroSmart Drive (Installation and Configuration Guide) Cause Manuals (F-25695, SOFT-MCN-101) are not available. Resolution Two documents in the list are obsolete and were inadvertently listed as available. They are: DCT MicroSmart Reference Manual (F-25695) MicroSmart Application Manual (SOFT-MCN-101). The remaining documents are available in iPortal > Publication Zone.

Issue After creating a new station using the "New Station Wizard" in Niagara G3 Workbench, it fails to copy into the ENC using the "Station Copier". This error message appears: "The local station database file config.bog is currently in use, and cannot be copied". Environment Niagara G3 Workbench Cause It's because a "Save Bog" was not done. Resolution Go back to Workbench and open the station, make a change and do a "Save Bog". The station should now copy without issue.

Issue A Niagara R2 / MicroSmart integration is creating IbsMs invalid condition and receive message entries in the Standard Output Window. Here is an example: ***IbsMs receive message: 454130433130464631433543 ***IbsMS invalid condition received: 28 Environment Niagara R2 MicroSmart Cause When the points are learned into the UNC station, it is in a specific order and the station records this information for making requests. If that order is changed in the MicroSmart, then the mismatch occurs. Resolution The mismatch occurs specifically when a record number is reused (i.e. a point is deleted and a new point created) and the point types are different. For example, an Analog Output point is deleted and a Start/Stop point is created – with the Start/Stop point being assigned the record number that was previously used by the Analog Output point. The UNC is expecting an analog point for that record number but is getting a response from a different point type. There are two choices to fix this situation: The controller is to be re-learned. Unfortunately, this will result in lost links and the need to go back and re-link all bindings done with this controller's database. Re-load the MicroSmart controllers with the original database so that it matches the learned database in the station. To find the offending controller(s), turn on de-bug and see if that will provide pointers to the controller(s) creating the error message. When done, make sure to turn off de-bug as it will create a large amount of entries in the Standard Output Window.

Issue The MNB-1000 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-BASE-1000 UL 864 Cause Information on MNB-1000 compliant with the UL 864 standard. Resolution The MNB-BASE-1000 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue Opening java or TGML graphics is very slow or they don't open at all. You may also have various java error popups. Environment TGML Graphics Cause The Java applet is limited to the amount of memory it is allowed to use. This will also limit how much memory java or TGML graphics are allowed to use, and can slow the rendering. Resolution It is possible to expand the amount of memory the Java applet has access to, and that seems to help in some cases. To increase this memory, do the following: Open the Control Panel in Windows and double click on "Java" Click the tab "Java" In "Java Applet Runtime Settings", choose "View" Find the most recent Java version runtime line (1.6.0_11) and double click on the "Java Runtime Parameters" box and add "-Xmx300m". This sets the Java maximum heap size to 300 MB. For some unknown reason, some computers with large amounts of installed memory are limited to how much memory they can assign to their Java VM. If you experience problems, just reduce the "300" to some smaller number (like 250, 200, 150, etc). However some computers have no problems setting the value to "1000". This procedure must be done to each computer individually. Also, remember to close all Internet Explorer windows for the changes to take affect.

Issue The MNB-300 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-300 mounting base UL 864 Cause Information on MNB-300 compliant with the UL 864 standard. Resolution The MNB-BASE-300 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue What version of Workplace Tech supports Microsoft Visio 2007? Environment Workplace Tech Microsoft Visio 2007 Cause Need WorkPlace Tech to function with Microsoft Visio 2007     Resolution WorkPlace Tech 5.7 supports Microsoft Office Visio 2007, Service Pack 1, and Microsoft Vista Business, Ultimate and Enterprise. WorkPlace Tech 5.7 continues to support Microsoft Office Visio 2003, Service Pack 3, and Microsoft Windows XP, Service Pack 2. Although this release may function with Microsoft Visio 2002, Service Pack 2, and Microsoft Windows 2000, Service Pack 4, this combination has not been tested, and will not be supported by Product Support Services. For further information, review the "Release Notes / Getting Started" document for 5.7.

Issue When using a Niagara R2 Enterprise Server with a "Remote Printer Recipient" on a large network with many printers, the Enterprise Server can take several minutes to complete its station startup following a reset. Environment Niagara R2 Enterprise Server Network printers Cause This situation is possible due to the remote printer recipient object that is attempting to populate its network printer recipient list. This would not be noticeable unless there are hundreds of printers on the network. This is how the remote printer recipient is designed to function. Resolution Possible workarounds for very large jobs affected by this would be to: Re-configure the customer's network so there are not so many networked printers Define local printers (or map network printers as local printers) in order to use the Local Printer Recipient Use the Vykon Alarm client to send alarms to network printers. Be advised printers other than dot matrix types will print one alarm per page.

Issue Defining a device name for each Network 8000 Microflo II controller is possible when it is configured under a GCM.  When defining it via a Niagara R2 UNC station, using the ASD driver, it is not possible. Environment Niagara R2 UNC station Network 8000 Microflo II controller Cause Not a supported feature in the ASD driver. Resolution Due to the maturity of the Microflo II product this is a feature that will not be incorporated into the ASD driver.

Issue Niagara R2 GCM driver version 2.304.522 may generate errors when uploading VEO information. Environment Niagara R2 GCM driver version 2.304.522 Cause This error is generated if there are attributes in VEO## list but there is no LABEL block associated with this VEO. Resolution There is a CreateVeoGxPages button located on the Block List Manager screen. This feature is intended to upload the GCM's View/Edit/Override information and generate the appropriate display screens. This function uploads the VEO information successfully, however it may fail to complete the process and generate a "NullPointerException".  To work around this error, create LABEL blocks in the GCM for each VEO used. Make sure to properly name each LABEL block starting with VEO and ending with 01 to 10. It is also possible a "ClassNotFoundException" will be generated during this upload process. This error is caused by the attribute types found in the VEOs uploaded. The GCM driver can only handle AV and DV types in the list. Any other types in the list will cause this error. To eliminate the error all non AV or DV attributes must be removed from the VEO attribute list(s) in the GCM.

Issue When trying to install Niagara R2 version 2.301.330, the process halts and reports that Java Virtual Machine (JVM) is not installed. What version of JVM is required? Environment Niagara R2 version 2.301.330 Cause All Niagara R2 versions prior to 2.301.514 require Microsoft's Java Virtual Machine.     Resolution All revisions of Niagara R2 prior to 2.301.514 require Microsoft's JVM. To confirm if it is installed, open a Command Prompt window and type "jview" then press Enter. This command will display the current version of Microsoft's JVM (or that it is not installed). Download and install Java_Virtual_Machine_for_WinXP.exe. All revisions of Niagara R2 starting with 2.301.514 and beyond require Sun's JVM. To confirm if it is installed, open a Command Prompt window and type "java -version" then press Enter. Visit http://www.java.com regularly to keep the JVM updated. The Microsoft and Sun JVMs can co-exist on the same Niagara host computer.

Issue How to load the Pocket I/A 4.1 software on a handheld device (PDA) Environment Handheld device (PDA) Pocket I/A 4.1 software Cause An Installation manual for the current version of the Pocket I/A software is not available. Resolution Use the following procedure to install the software:   Open ActiveSync on the computer and establish a connection to the Pocket-PC device.  It is not necessary to create a partnership when making this connection. Copy the CAB file and paste it somewhere on your handheld device, the Storage Card is a recommended location. After copying the file to the device, disconnect it from the computer. Open Pocket-PC's File Explorer, located into the Programs. Browse the storage card or the location used to copy the CAB. Select and run it, and a window will appear, which asks to choose a location to install the program. It can be the Device or the Storage Card, so select either and click below on Install. The process after that is fully automated and after the installation is complete it will show a confirmation screen. Refer to the help file installed with the Pocket I/A software for information on using the program.