Building Automation Knowledge Base

Issue The Momentary Start / Stop (SS) object in a MNB-1000 controller is not working.  The OutStrt and OutStp outputs never pulse on as programmed.  The OnPulse and OffPulse times are set to 1 second each. Environment MNB-1000 with firmware 1.501 or newer Cause The On and Off times for a Momentary Start/Stop object fails with a start time or stop time below 2 seconds. The Plant and Remote I/O Module can't do accurate timing below 2 seconds or so by design. Resolution Release 1.501 firmware for the MNB-1000 controller allows the Momentary Start / Stop (SS) object to be used with OnPulse and OffPulse intervals of 2 seconds or greater.  This is described in the Release Notes for WPT 5.7 / MNB-1000 1.501 Firmware (F-27526).     On and Off Pulse timing wrong for Momentary Start/Stop.     PRN 4677     Issue:     The Momentary Start/Stop times in the MNB-1000 are not accurate     when set for small second increments (1 to 12 seconds)     Resolution:     This has been partially fixed in the MNB-1000 firmware.     Small increments greater than 2 seconds are now accurate.     See the note on PRN 5011 describing limitations on increments     less than 2 seconds.     On and Off Pulse timing wrong for Momentary Start/Stop.     PRN 5011     Issue:     The On and Off times for a Momentary Start/Stop object fails with     a start time or stop time below 2 seconds. The Plant and Remote IO     Module can't do accurate timing below 2 seconds or so by design.     The object still works, but the timing is inaccurate.     Resolution:     A note has been added to document F-27356 (revision 3) "WorkPlace     Tech Tool 5.7 Engineering Guide Supplement" to warn of the     limitations of this object in the MNB-1000.  

Issue Trying to talk to Trane Controller (MP580) and will not update. (LON) Environment G3/R2 Niagara Cause Run Frequency is a property that defines how often the program executes. If set to 0 values will not update in LON shadow object. Resolution Run frequency to a value other than 0.

Issue  Is it necessary to commission an MNB series controller if it is being used in a standalone application?   Environment Single standalone MNB series controller Cause Using an MNB-300 controller to control a small RTU via an attached MN-sx sensor during construction.  Resolution No. Commissioning is needed only when the device is being configured to communicate via its BACnet interface.

Issue What are the part numbers to order the back plate and controller separately for an MNB-1000? Environment MNB-1000 Cause MNB-1000 part number break down. Resolution The MNB-1000 controller breaks down as follows: MNB-1000 - Controller and Base Assembly MNB-CNTLR-1000 - Controller only, less Base MNB-BASE-1000 - Base only, less Controller  

Issue The Platform Software Manager indicates the Report module is installed on the ENC, but ReportService cannot be added to the Services container of an ENC. The following error message is displayed in the Program Director window: WARNING [22:25:05 12-Jan-12 CST][sys.xml] Type "report:ReportService" not found: null [3:55] javax.baja.xml.XException: Error parsing value [4:4] at javax.baja.io.BogDecoder.err(BogDecoder.java) at javax.baja.io.BogDecoder.decode(BogDecoder.java) at javax.baja.sync.AddOp.decode(AddOp.java) at javax.baja.sync.SyncBuffer.decode(SyncBuffer.java) at com.tridium.fox.sys.broker.BBrokerChannel.syncToMaster(BBrokerChannel.java) at com.tridium.fox.sys.broker.BBrokerChannel.circuitOpened(BBrokerChannel.java) at com.tridium.fox.sys.BFoxConnection.circuitOpened(BFoxConnection.java) at com.tridium.fox.session.SessionCircuits$ServiceThread.run(SessionCircuits.java) at java.lang.Thread.run(Thread.java:823)   Environment Niagara G3 all versions, ENC-410, ENC-520 Cause The ReportService Module in the ENC Platform may have become corrupted. Resolution Uninstall and reinstall the module in the ENC, making sure the module content filter is set to ui+runtime.

Issue Browser locking up with blank screen after viewing several graphics.  Java console says java.lang.OutOfMemoryError: PermGen space. Environment IA Series Niagara G3 Cause This can occur when viewing graphics screens from different ENC stations that have differing versions of modules. The browser will load the modules it needs from each ENC which can eventually use up all the available PermGen memory. Resolution Make certain all ENC stations are using the same version of the modules needed.

Issue Getting the following error message when attempting to open a Niagara R2 Enterprise Server station: ERROR: Cannot open web server socket. [ServerLoop.run] java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket.(Unknown Source) at tridium.nre.drivers.SocketDriver$TcpSocketFactory.createServerSocket(SocketDriver.java:681) at tridium.nre.drivers.SocketDriver.createServer(SocketDriver.java:203) at tridium.foundation.net.TWebServer$ServerLoop.run(TWebServer.java:754) at java.lang.Thread.run(Unknown Source) Product Line TAC IA Series Environment Niagara R2 Enterprise Server all version Cause Windows IIS is enabled on Enterprise Server PC. IIS and WorkPlace Pro (station database) have a conflict issue related to Port 80. By default, IIS connects and utilizes Port 80 when installed and running. This directly conflicts with an Enterprise Server’s station database running on the PC which also uses Port 80 by default. Resolution Most times, users do not require IIS on the Enterprise Server or WorkPlace Pro PC so IIS is disabled. If IIS is required, users typically change the port used by the station's database to another port (e.g. 8080, etc.). If this change is made, all other settings that access this IP for the station (address table entries, web browser pages, etc.) must append the port number to the IP address (e.g. 192.168.1.142:8080). Disable the IIS if not required by some other application on the Enterprise Server PC. Select Start and open the Control Panel Double-click add remove program Click on “Add/Remove Windows Components on left side on screen Scroll down and deselect Internet Information Services in the Components window Click next and Finish The Enterprise Server station can now be opened. Note:  On Windows 7 host computer, the World Wide Publishing Service may be linked to IIS.  Go to 'Services' in Windows 7 and modify its startup to 'Manual' so that it does not start automatically.  If IIS is needed on the Enterprise Server PC, then change the port used by the Enterprise Server. Open WorkPlace Pro Admin Tool and stop the Enterprise Server Open the Enterprise Server offline Right-click on the Enterprise Server station and open its Properties sheet Click on the Config tab Change httpPort to the desired port number and click Apply Right-click on the Enterprise Server and Save Close the Enterprise Server station Open Admin Tool and start the Enterprise Server station  Once the station starts you should now be able to access it. Please note that the port number must now be included in the station's address when accessing the Enterprise Server.

Issue Is there a setting that will retransmit a BACnet point in case a BACnet device goes offline? Environment Niagara G3 ENS, ENC-410, ENC-520 Cause Points go offline and come back online with controller default values. Resolution The Max Write Time applies to writable proxy points. Specifies the maximum “wait time” before rewriting the value, in case nothing else has triggered a write. Any write action resets this timer. If property value is 0 (default), this rule is disabled (no timed rewrites). The Max Write Time of the Tuning Policy can be set to periodically write to proxy points at a set time interval. 1. Open the station and expand its BACnetNetwork 2. Expand Tuning Polices 3. Double-click on the policy you want to update 4. Enter a maximum time to be used in the Max Write Time property. (example 10 minutes) 5. Save change Note: In some cases setting this to some value, for example 10 minutes, may be useful. Often, a network may have devices that upon a power cycle (or even a power “bump”), have writable points that reset to some preset “default” value or state.

Issue Can I add BACnet MSTP to an I/A Series R2 or G3 JACE-NXT hardware platform? Environment I/A Series R2, G3, JACE-NXT Cause The JACE-NXT platform is based on a Microsoft Windows software platform (Windows XP) that is unable to support the token passing required for BACnet MSTP. Resolution Options are ... 1. Use another device that can act as a router between BACnet MSTP and BACnet IP or BACnet Ethernet (e.g. MNB-1000, etc.). 2. Use a different R2 or G3 hardware platform that provides direct connection to the BACnet MSTP device (e.g. UNC-520, ENC-520, etc.).

Issue Customer has an older ENC-520-2 and has run out of memory for his station programming.  His ENC has only 128mb of memory, not the 256mb of memory in the current ENC-520-2 controllers. Environment ENC-520-2 or ENC-520-2-N manufactured in Rockford (SN xxxxxB) prior to BootFlash upgrade. Cause Manufacturing change. Resolution The base memory (128mb) version of the ENC-520-2 cannot be field upgraded to extended memory (256mb) due to other component changes on the controller circuit board.

Issue Changing the LON device's subnet and node address. Environment I/A Series G3 LonWorks Integration Cause When a LON device is added to the station database, its subnet and node addresses are automatically assigned. For the correct communication to be established there may be a need to change the subnet / node address of the LON device. Resolution To change the device subnet / node address: Right click on the LonNetwork and go to the Lon Device Manager. Select the LON device for which subnet / node address needs to be changed Edit the device by double clicking on the LON device or using the 'Edit' button at the bottom of the Lon Device Manager view. Enter the correct subnet address and a unique node address for the device. Commission the LON device regardless of whether it has been commissioned before. 

Issue The Veris H8920-3 will not update its Lon SNVTs unless a fetch is performed. The H8920-3 shadow object in the Niagara R2 UNC-410 will not update automatically. Environment Niagara R2, UNC-410, UNC-510, UNC-520 Veris H8920-1, H8920-3, H8920-4, H8920-5   Cause The Veris H8920-3 Auto Propagate Feature is not configured to automatically update all network variables. The Auto Propagate Feature of the H8920-3 must be set accordingly for its network variables to be automatically updated to the UNC. Resolution The following steps configure the H8920-3 Integrator to automatically update it variables to the UNC. Open the UNC-xxx station in WorkPlace Pro. Expand the folder containing the H8920-3 shadow object Right-click and open the H8920-3 properties Click on the OpenLoopSensor tab and then Config tab Set the nciMaxSendTg to and value above its default of “0”. (suggested value is 100) The Veris H8920-3 Integrator will now periodically update its network variables to the UNC. NOTE: The following is an excerpt from the Veris H8920-x Installation Guide: The H8920-x automatically propagates all network variables. If nciMaxSendTg is set above zero (default is zero), all variables are propagated periodically. Units are in tenths of a second. For example, if nciMaxSendTg is set to 100, the H8920-1 will automatically propagate all variables every 10 seconds.

Issue The MNB-Vx (MNB-V1, MNB-V2) controllers are shown as replaced by the MNB-Vx-2 (MNB-V1-2, MNB-V2-2) on iPortal.  What is the difference? Environment MNB-V1 (-2) MNB-V2 (-2) Cause Production change Resolution There are no functional differences between the MNB-V2 and the MNB-V2-2 controllers. The part number was changed to allow tracking of an internal manufacturing change in the actuator part of the assembly.

Issue Changing the default port numbers for the Fox, Platform Daemon and HTTP ports in I/A Series G3 Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Enterprise Network Controller Cause There is a need to change the default port numbers of the Fox, Platform and HTTP ports used in I/A Series G3. Below are the descriptions of the ports usage and their default port numbers: TCP port 1911 (Fox port) Default port for a station's Fox Service used for Workbench to station and station to station communications TCP port 80 (HTTP port) Default port for a station's Web Service used in browser access (Hx, Wb) TCP port 80, 3011 (HTTP and Platform Daemon ports) Default ports for Workbench Platform connection Resolution The default ports for the Fox and HTTP ports can be changed during the process of creating a new station. Follow the following procedures if the ports need to be changed after the station has been created. To change the Fox port: In Workbench, open the station. Expand 'Config' > 'Drivers'. Open the Property Sheet of the NiagaraNetwork. Expand the 'Fox Service' and you can change the port number from the default of 1911. To change the HTTP: In Workbench, open the station. Expand 'Config' > 'Services'. Open the Property Sheet of the WebService and you can change the Http Port number from the default of 80. To change the Platform Daemon port: In Workbench, open the host's Platform. In the Platform view, go to the Platform Administration. In the Platform Administration view, click on the 'Change HTTP Port' button to change the default port.

Issue Roam IA communications error when disconnecting from one standalone controller and plugging into another Environment I/A Series Workplace Tech WorkPlace Commissioning tool Cause The Roam IA is designed to join a trunk and then access various devices.  As such the Roam IA must be connected to a communicating trunk or device before it's turned on so it can be detected when switched on and it can sync to the established baud rate, see the TAC I/A Series RoamIA Quick Start Guide for details.  Resolution When working with standalone controllers turn off the Roam IA after completing work with one controller, connect to the next standalone controller and turn on the RoamIA.  It will establish communications with the new unit and allow communications.

Issue When "Exporting Data" from a multi-history chart there are many nan's in the data. Environment I/A Series G3 (Niagara) Cause The timestamp in the history data has a millisecond component that is not shown on the data displays.  When the Export data is displayed history values are provided with the timestamp.  If the timestamps for all the histories samples are exactly the same (to the millisecond) the data value is displayed, if not "nan" is displayed.  Resolution This condition occurs only when the "rollup" for the chart is left at the default of none.  Changing the "rollup" to a value other than none will bring the data into order.  Setting the rollup to the sample interval of the histories gives the best results in the Export data.

Issue The error message "BACnet is not enabled!" is displayed in the Standard Output Window of the UNC when a whoIs is performed in BACnetService. No devices are displayed. Environment Niagara R2, UNC-410, UNC-520 Cause The BACnet instance number in the UNC was set at its default of -1. It must be configured with an unique number between 0 - 4,194,302 Resolution Assign the unique instance number for the UNC. Open the UNC’s station and expand its Services container Right-click BACnetService and select Properties Open the General and Config tab Enter a unique number in the Instance Number property and then click Apply The BACnet devices will be populated when a whoIs is performed.

Issue Unable to override an ASD point from a Niagara G3 Enterprise Server. . Environment Niagara G3 Cause TAC/ASD module is missing from Enterprise Server Niagara Modules folder. Resolution Download TAC/ASD module from The Exchange Download Center Download the matching revision module and copy the file in the Niagara Modules folder. Restart the Niagara Service and Workbench to register the module.

Issue Frequently see Java.lang.Exception errors in the UNC error log or Standard output window that reads, in part,      "At tridiumx.gcm.GcmUnsolicitedReceive.run (bytecode xxx)" Environment I/A Series R2 UNC I/A Series GCM 84xxx or GCM 86xxx connected to UNC Cause The GCM does send unsolicited messages all the time, more or less depending on how you have the logging configured in the GCM. Depending on the source of the message, some will simply be reported to the Standard Output Window as "Unsolicited GCM message received" or "Processing Unsolicited Message"'. Other messages will be reported as a part of an error message written to the Standard Output Window and / or the Error log. Resolution You can minimize these messages by insuring that none of the print groups in the GCM are configured to use the serial port to which the UNC is connected. You also need to confirm that all of the Exception Print Flags in the GCM are set to NO. The remaining messages that cannot be eliminated are almost always GCM Network communications protocol messages that have no meaning to the UNC.  

Issue An end customer wants to use SSL on his Niagara R2 control system.  Is it supported? Environment Niagara R2 Cause Security policy changes by end customer's IT department Resolution SSL is not supported in the Niagara R2 environment.