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 Procedure for changing the name of a FLO2 block in a Network 8000 GCM, and in the MicroFlo II controller Environment Unknown Environment Cause Unknown Cause Resolution The name comes from the FLO2 block in the GCM. Once the block is created and named, there is no direct way to edit the name, either in the GCM or from PSI. The name is saved in the backed-up PSI application file, and when the application is downloaded, the name in the controller changes to the name from the file. Download a different file, and the MFII gets a different name. To keep the programming intact, but change the block name in the GCM and in the controller: 1. Set the physical address of the existing FLO2 block (with the wrong name) = 0. 2. Copy the block, give the new FLO2 block the name you want. 3. Edit the new FLO2 block, set the physical address = the DIP switch setting on the MFII. 4. Reset the new block, created in step 3. This writes the new name to the MF2 controller. 5. Delete the original FLO2 block, that had the wrong name.

Issue Wiring detail for using the B&B Electronics model USOPTL4 converter with PSI / XPSI Revision 4.1 Product Line TAC IA Series Environment PSI (Personal System Interface) Revision 4.1 XPSI (Xtended Personal System Interface) Revision 4.1 B&B Electronics USOPTL4 converter Cause PSI / XPSI Revision 4.1 does not work with the Patton Electronics RS-232 / RS-485 converter, model 2089-bc, that was widely used with earlier versions of PSI (rev. 3.13) and XPSI (rev. 2.0). Resolution One converter recommended for use with PSI / XPSI Revision 4.1 is the B&B Electronics model USOPTL4. To connect directly to the RJ-12 jack on an ASD device, or on a stat: Cut the RJ-12 plug off one end of an RJ-12 cable. Connect Black and Yellow wires and tape back. Connect the Green wire to the RDB(+) on the screw terminal of the USOPTL4. Connect the Red wire to the RDA (-) on the screw terminal of the USOPTL4. All four switches of the DIP switch on the USOPTL4 must be in the ON position to allow it to work properly on the ASD bus.

Issue Menu pull downs missing from WorkPlace Tech 5.7.1 after installing the Belkin Bluetooth adapter. Environment WorkPlace Tech 5.7.1 Belkin Bluetooth adapter Cause For Visio 2007, un-check the box for Send to Bluetooth. For Visio 2003, un-check the box for COM add-ins. Resolution Field offices have reported an issue after installing the Belkin Bluetooth adapter for use with the MNB-ROAM-IA. The problem is that Workplace Tech menu pull downs are missing (Project, Application); additionally, all of the Workplace Tech options are missing from the Tools pull down ( Configure Communications, Browse Devices, WorkPlace Commissioning Tool, etc.) One result of this problem is that the user cannot re-configure WorkPlace Tech for LON communications, or any other BACnet communications. WorkPlace Tech 5.7.1 with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Trust Center Select Add-ins. 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 Send to Bluetooth. Click OK to apply. Close Visio. Open WPT, all menu items should be there. Workplace Tech 5.7.1 with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Click OK to apply. Close Visio 2003. Open WPT, all menu items should be there.

Issue What models of Bluetooth adapters are supported with WorkPlace Tech for use with the BACnet Roam-IA MS/TP interface? Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.7.1 or newer MNB-ROAM-IA BACnet MS/TP adapter Cause Many of the available BlueTooth adapters do not support serial communication emulation at 115,200 baud as is required by the Roam-IA BACnet MS/TP interface. Resolution Approved USB Bluetooth Adapter for systems that do not currently have a Bluetooth facility, can be easily added by purchasing an approved external Bluetooth adapter. At a minimum, the adapter used MUST BE CAPABLE OF serial communication emulation at a rate of 115,200 baud. Some of the less expensive adapters are only capable of 57,600 baud. For use with WorkPlace Tech, the tested and approved external Bluetooth adapter is the Belkin USB adapter (330 Feet), Model F8T012 – UPC Code: 7 22868 61581 2. Although other external adapters may work, use of this adapter is required for resolving product support issues. Update: As of 6/19/2009 The Belkin Bluetooth adapter model F8T012 is obsolete and has been replaced by the Belkin USB Bluetooth Adapter Model F8T017  – UPC Code: 7 22868 67681 3.

Issue What are the proper steps in upgrading an I/A Series WorkPlace Pro site? Environment WorkPlace Pro Cause Instructions on upgrading an I/A Series WorkPlace Pro site Resolution The published upgrade instructions can be found on F-27334 TAC I/A Series® R2.301.522 Installation Instructions. However, there is another method. Using the existing version of WorkPlace Pro backup ALL of the UNC and Server databases into the XML format. Copy the stations containing the XML to the desired WPP revision. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, this will allow you to repair them with out affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This will save you time later if you need to reload the UNC.) Now you can install the new desired revision into the Server, copy all of the stations into the new stations folder. Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC you will be ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. What it will do is backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. The only problem you may encounter would be on old Lon jobs. Some of the enumerated SNVT definitions were change by Echelon about the time we released WPP 431. If you run into the problem, the XML can typically be edited to resolve them.

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 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 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 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.

Issue What is the scan rate for the inputs and outputs of a MNL-20R? Environment MNL-20R Cause Require fast response time for high-speed applications. Resolution Inputs = 220 ms Outputs = 100 ms