Building Automation Knowledge Base

Issue Encountered the following error while accessing an UNC station recently added with the SnmpService Cannot initialize view. java.lang.IllegalStateException: tridiumx.snmp.services.SnmpService: releases incompatible [2.302.532.v1 != 2.301.431.v1] Environment I/A Series R2 Cause This is caused by the version of WorkPlace Pro software used. WorkPlace Pro software version r2.301.431 was being used to access an UNC station with SnmpService version r2.301.532. Resolution Use WorkPlace Pro version 2.301.5xx and above to access the UNC station.

Issue Customer site security requirements do not permit web browser access via the http protocol to any device on their Ethernet network so they need to be able to disable it. Environment UNC-410 or UNC-520 Cause Government / corporate IT security regulations do not permit web browser access via the http protocol to any device on the Ethernet network. Resolution If creating a new station, do not select the "Web User Interface Service" in the Add Services dialog. If the station has already been created and is running, open the station in WorkPlace Pro and cut the "WebUiService" out of the Services container.  After cutting out the service, you need to restart the UNC.  If the WebUiService does not exist in the station, an http 400 error, "No Browser Support" error will be returned when an attempt is made to access the UNC station graphics via the browser.

Issue In Niagara R2 Workplace Pro, what's the default size of a Container's Workspace?  What are the maximum settings? Environment Niagara R2 Cause A large shadow object cannot be fully viewed in the Workspace due to the current width and height settings. Resolution The default settings are:  800 (width) by 550 (height). The maximum settings are:  1500 (width) by 1500 (height). To modify these values, right-click the Container properties, Visual tab.

Issue Is there a way to set both local and imported histories to update live when accessed in Niagara G3? Environment Niagara G3, versions 3.4 and higher. Cause User wants to display live data. Niagara G3 allows for the displaying of current history values (live data updates) buy using its On Demand history feature. Resolution The On Demand feature provides live updates for the History Chart or History Table views only. On Demand can be used for both local and imported histories. The On Demand feature provides a 'Live Updates' toggle button (check box in Hx view) on both the history chart and history table views. Click this button to start the live update process. Note: The following must be set in order for Live Updates to work with imported histories. These setting are normally enabled by default, but may have been changed. The imported history’s “On Demand Poll Enabled” property must be set to true. 1. Expand the NiagaraNetwork of the station and select the source station for the imported history 2. Expand the source station and then expand Histories 3. Right-click on the Remote history you want to view live updates and select Property Sheet 4. Make sure that “On Demand Poll Enabled” is set to true and save The On Demand feature provides a 'Live Updates' toggle button (check box in Hx view) on both the history chart and history table views. When you click the 'Live Updates' button, it initiates a history subscription that finds the source of the history and subscribes to that source component. If the source is a history import descriptor, then that descriptor starts polling at a frequency defined by its On Demand Poll Frequency property (described below). If the source is a local History Ext,

Issue Will changing the IP address of a BACnet/IP controller affect communication between BACnet objects on an established network? Environment Niagara R2 and G3, UNC-520, ENC-520, WorkPlace Tech Commissioning Tool, MNB-1000 Cause Niagara R2 and G3, UNC-520, ENC-520, WorkPlace Tech Commissioning Tool, MNB-1000 Resolution BACnet communicates using the BACnet device’s instance number, so changing the IP address of the controllers will not affects the communications between BACnet points. The BACnet/IP controller's MAC Address is comprised of its IP address and port number. This BACnet/IP Controller’s MAC address will automatically updated whenever one of the following tree procedures are performed, a “whoIs” is in R2, a “Discover” in G3 or a "Browse" of the BACnet/IP network in WorkPlace Tech Commissioning Tool.

Issue Is the MNL-110 or MNL-130 controller available in any profile other than Fan Coil profile (F3)? Environment MNL controllers (MNL-110, MNL-130) Cause The MNL-110 and MNL-130 controllers are only available with the Fan Coil profile (F3).  The profiles cannot be modified in the field. Resolution Review alternative hardware platforms (MNL-50, -100, -150, or -200) in the following profiles ... Rooftop profile (R3) Fan Coil profile (F3) Heat Pump profile (H3) Satellite profile (S3) Satellite profile (S4)

Issue I/A Series R2 Optimum Start Stop program object may improperly calculate start time when outdoor air temperature compensation is used. Environment I/A Series R2 (all versions) Cause Optimum start / stop compensation is performed through the use of a program object. The object could calculate a negative start lead time when outdoor air temperature compensation was used. Resolution A check was added to the program object to prevent a calculated negative start leadTime due to outdoor air temperature compensation.  The revised object is available for download from The Exchange Download Center. Download the file >> OSS for Niagara 08_03_11.zip In addition, the object includes the following change history. 10-Nov-00  Moved the parameter reset control to an external stimulus 16-Aug-01  Changed reset input from BooleanPriority to DateTime 20-Dec-02  Added check for command time > next event time to account for a large leadtime calculation that results in a start time prior to midnight 14-Sep-05  Added safety check to prevent dynamically adjusted runtime factors from becoming too large 25-Apr-06  Corrected the following stop-time issues:            1) stop-time calculation when earliestStopTime is after schedule stop time            2) stop-time calculation when start/stop times span midnight            3) determining when to perform stop-time analysis    05-Nov-08  Added changes from 2002 and 2003            Added prestart (maxStartLimits) and comfortLimit inputs 18 Nov 02            Added the ability to use OA temperature for OSS calculation 24 Feb 03 12-Dec-08  Added OA temperature to message strings.  Added output for calculated command time. 19-Feb-09  Corrected issues with stop-time analysis:            1) lastStartTime was being used for stop-time calculation            2) analysis for heating was adjusting drift time for cooling            3) analysis for cooling was adjusting drift time for heating            Corrected issues with stop time calculation:            1) heating mode failed to drift when > upper comfort limit            2) cooling mode failed to drift when < lower comfort limit            3) stop mode calculation always reflected the next event time 15-Oct-09  Added properties and check to prevent dynamically adjusted drift time factors from exceeding a specified maximum value. 03-Aug-11  Added check to prevent calculated negative start leadTime due to outdoor air temperature compensation.

Issue What licensing is required for the I/A Series LON Flow Balance tool? Environment I/A Series LON Flow Balance Tool Cause The LON Flow Balance Tool has been downloaded and provided to the air balancer. Resolution The LON Flow Balance Tool software does not require a license.

Issue When is an "additional 500 points" license required for an Enterprise Network Server? Environment I/A Series G3 ENS-1 Enterprise Network Server Cause The basic Enterprise Network Server license does not include any external point driver licenses.  Driver licenses are required for each 500 or fraction thereof points of any of the four supported driver types. Resolution An Enterprise Network Server can be licensed to directly communicate with BACnet, OPC, MODbus or SNMP points by the addition of the specific driver license option.  Each of these driver licenses support communication with up to 500 points of that specific type of points. The four driver licenses are as follows: ENS-BAC (BACnet IP or BACnet Ethernet) ENS-OPC (OPC Client), ENS-MOD (Modbus TCP) ENS-SNMP (Simple Network Management Protocol).  Each of these driver licenses will support the communications with up to 500 points of the specific type.  For each additional block of 500 points of a specific type, you need to purchase an additional points license, ENS-BAC-500, ENS-OPC-500, ENS-MOD-500 or ENS-SNMP-500.  Here is an example of how these licenses are used.  The Enterprise Network Server needs to communicate directly with 1250 BACnet IP points and 60 SNMP points.  The following licenses will be required: ENS-1 -- Enterprise Network server license ENS-SNMP -- allows ENS to communicate with the 60 SNMP points, technically allowing communications with 500 SNMP points. ENS-BAC -- allows the ENS to communicate with 500 BACnetIP points ENS-BAC-500 -- allows the ENS to communicate with an additional 500 BACnet points bringing the total to 1000 BACnet points ENS-BAC-500 -- this second ENS-BAC-500 license will allow the ENS to communicate with the additional 250 BACnet points, actually bringing the total allowable BACnet point count to 1500 points

Issue After upgrading the WorkPlace Tech Tool software to release 5.8 and requesting / installing a new TIP demo license, the license is still shown as expired. License request was generated using the "Purchase WIBS Software" icon on the computer desktop. Environment I/A Series WorkPlace Tech Tool software, release 5.7.2 or newer including release 5.8.x. Cause The WIBS Purchase program is used for licensing all WIBs product family software and the WorkPlace Tech Tool software, prior to release 5.7.2.  This licensing software is not compatible with Windows 7. The licensing subsystem software used with the WorkPlace Tech Tool software, release 5.7.2 and newer uses a new licensing subsystem that is compatible with Windows XP, Windows Vista and Windows 7. Resolution After installing the WorkPlace Tech Tool software, version 5.7.2 or newer, the "WIBS Purchase" icon can no longer be used to request a new or updated license for the WorkPlace Tech Tool software.  The "WIBS Purchase" licensing program does not work with the newer version of the WorkPlace Tech Tool software. During the installation of the WorkPlace Tech Tool software, a new license request program is installed on the public desktop, if not already installed.. This license request program is named "Purchase WorkPlace Tech Software".  This icon must be used to create the license request and install the new license for the current version of the WorkPlace Tech Tool Software.  Depending on the computer configuration and user permissions, the "Purchase WorkPlace Tech Software" icon may have not been created on the computer's desktop.  If the program is not on the desktop, the corresponding program, WPTLPurchase.exe can be found on the computer in the folder C:\Program Files\WorkPlace Tech\Licensing\Core".  A shortcut to this program should be created on the computer desktop.

Issue Can both RS-232 ports be used for Modbus simultaneously on an I/A Series UNC-520? Environment I/A Series UNC-520 Cause The I/A Series UNC-520 is licensed with the Modbus master driver IA-DRV-MOD.  The requirement is for the UNC to communicate Modbus to third party controllers using RS-232. Resolution Yes ...both I/A Series UNC-520 RS-232 ports can be used simultaneously with the Modbus driver IA-DRV-MOD (ModbusAsync) set for COM1 and COM2.

Issue Attempting to link from one I/A Series G3 station to another using a pop-up link and getting an error when using the browser.  The error indicates - javax.baja.license.FeatureNotLicensedException: tridium:brand. Environment I/A Series G3 (all versions) Cause Created a PxFile with a bound label pop-up binding to open another link outside the station environment (e.g. history).  The link works properly when using and viewing in Workbench but does not work with IE browser. Resolution The pop-up link through the browser currently does not support links to another station (supports only links within the same station).  Recommend the graphic be located with the associated history in the same station if pop-up link required.

Issue ASD devices appear intermittent (device up / device down) when running the I/A Series R2 ASD driver build 514 and older. Environment I/A Series R2, ASD, ibsAsd-2.301.514.v1 (build 514 or older) Cause The ASD driver (514 or older) utilized the user defined retry count as part of the device recovery setting the value to zero during the ping.  This value could be subsequently captured in flash if the station backup occurred while the value was zero. Resolution This has been resolved in newer versions of the driver ibsAsd-2.302.516b and higher.  Upgrade ibsAsd and serialDriver as required.

Issue Customer has received some MNB-300 bases that have green connectors instead of the usual blue ones.  Are they interchangeable? Environment I/A Series MNB-1000, MNB-1000-15, MNB-70, MNB-300 and associated base part numbers MNB-BASE-15, MNB-BASE-1000 or MNB-BASE-300 Cause Manufacturing parts procurement variations. Resolution Bases are  fully interchangeable with other bases of the same part number, regardless of the color of the I/O colors. This color variation does not apply to the power or communications connectors.   Power is always a three-pin Green connector.   BACnet-MS/TP is always a three-pin orange connector.  MNB-1000-15 communications trunk and corresponding connector on the MNB-1000 is  three-pin Black connector.

Issue In Niagara G3, how can an ENC be diagnosed as overloaded? Environment Niagara G3 ENC-410 Niagara G3 ENC-520 Jace-6 Cause Programming guidelines needed to prevent overloading the ENC. Resolution The CPU usage should be less than 80% on a continuous basis. The heap.used should be less than 75% of the heap.max value.  Java heap is comprised of station objects operating under runtime conditions.  Objects are created as needed and destroyed via garbage collection (GC) when no longer needed.  Garbage collection is a mechanism provided by the Java Virtual Machine (JVM) to reclaim heap space from objects eligible for collection.  An object becomes eligible for garbage collection if its not reachable from any live threads or any static references (e.g. all references are null). A heap ratio (heap used to heap max) that exceeds 75% causes the JVM to allocate additional time to perform garbage collection and cleanup.  This in turn begins to increase CPU usage which slows down overall station processing and performance.  Eventually, a station watchdog can occur if the processing becomes too slow rebooting the unit due to a watchdog timeout. Note: Make sure to execute or manually trigger a garbage collection prior to evaluating the heap.max value. Using Workbench, right-click on the connected station and select Spy from the drop down menu.  Select util and gc to execute the garbage collection. Methods to decrease heap used: Removing objects from the station logic that may not be required. Reviewing custom objects or programs that may be memory hogs. Use of a controller with additional maximum heap.  The max heap of a ENC-410 or ENC-520 (non-extended memory 128 MB RAM version) is 48 MB.  The extended memory ENC-410 and ENC-520 versions increase the RAM to 256 MB and the maximum heap to 96 MB. The JACE-6E can be purchased with the extended memory option to increase the heap to 96 MB. Add another ENC or JACE controller. Histories can also affect the heap.used value. When the station needs to write a record to a history, it opens the specific history into the running station from the file system if PC based or the ram disk if QNX-based.  The open history does contribute to the heap.used of the station.  Remove unnecessary or unused histories by disabling the history within the extension, removing the associated history file, and removing the history extension.

Issue What do the LEDs indicate on a MSC-NC or MSC-NCM? Environment DMS Cause Communications is down on a jobsite.  Trying to troubleshoot the MSC-NCM. Resolution Here is the function of each LED: WDT:  indicates processor and MSC-NCM communication status.  One blink/second indicates that the MSC-NCM is communicating with at least one Microsmart controller.  Two blinks/second indicate that the MSC-NCM processor is functioning but the MSC-NCM is not communicating with any controllers.  If it is blinking very fast, the MSC-NCM processor is functioning but the MSC-NCM program has not been downloaded into the controller (hence, the system is down). ALARM:  indicates a service or point alarm condition exists somewhere on the controller trunk TxD:  indicates data transmitted RxD:  indicates data received DCD:  illuminates when the Data Carrier Detect signal is active (used with modems) RING:  illuminates when the modem detects an incoming call

Issue What type of surge protection comes with a MNB controller? (e.g. from a lightning strike) Environment MNB controllers Cause Job specification requirement Resolution All of the MNB controllers are tested to the IEC EN 61000 standard which is a rigid test for surge protection where all I/O, Power, and Communications are subjected to a 20KV surge. During design, this normally results in having to add in extra protection so as to pass the test. Communications within the controllers have optical isolation which protects the communications transceivers to transients.  

Issue The Application Director output window displays an Engine Watchdog Timeout by issuing a thread dump and displaying App Failed.  This condition can occur when installing an upgraded station, after a reboot of the existing station, or during normal station operation. Environment I/A Series G3, Niagara Cause The software watchdog mechanism is designed to periodically report the station's engine cycle count to the platform daemon.  The main purpose is to detect and restart a "stalled" station when the control engine is believed to be in a deadlocked condition.  If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy. Depending upon station operation, the watchdog timeout may need to be increased to compensate for transient conditions where the NRE engine thread is temporarily busy during a single execution cycle.  These conditions include simultaneous execution of multiple objects or point extensions that occur on the same time interval, archiving of log history, custom objects, etc. during normal operation.  The default timeout is 1 minute. Resolution Tuning may be required (increase of the default watchdog timeout value). Open the running station, expand Config, expand Services, right click PlatformServices - View - Platform Service Container Plugin, locate the Engine Watchdog Timeout property.  Increase the value by 30 second or 1 minute increments and monitor controller operation (adjust as required).  If the condition continues, contact Schneider Electric Product Support for further assistance. Watchdog policy selections include: Log Only — Generates stack dump and logs an error message in the system log.   Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.   Reboot — Automatically reboots the host JACE platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.   Engine Watchdog Timeout — Default is 1 minute, and range is from 0 ms to infinity.

Issue Is the an M-bus (meter bus) driver for UNC's? Environment UNC, I/A Series, niagara Cause Not applicable Resolution An M-bus driver does not exist for the R2 system.  There is a driver available in the G3 system.

Issue The I/A Series R2 VAS Client connection is lost whenever a new alarm is received. Environment I/A Series R2 (all versions), VAS Client 2.42 Cause This is caused by a version mismatch between the VAS Client and the associated VAS jar file.  The VAS Client (Versions 2.42 and 2.50) can lose connection whenever a new alarm is received when vas jars vas-2.301.522 or vas-2.301.529 are in use by the Enterprise Server. Resolution Update the VAS Client and associated vas jar file.  If you are using R2 and the database is Cloudscape, make sure to use the vas-2.301.532.v2 jar included with the VAS 2.5 Client download from The Exchange Download Center. Review the included release notes for further details.