Building Automation Knowledge Base

Issue I/A Series R2 and G3 MIB files Environment I/A Series R2 SNMP integration I/A Series G3 SNMP integration Cause A Management Information Base (MIB) describes a database of objects that can be monitored by a network management system. SNMP uses standardized MIB formats that allow any SNMP tool to monitor any device defined by a MIB. The Tridium MIB defines the information that can be exposed for a I/A Series Niagara station running the SnmpService. The third party system is having trouble reading the SNMP traps from I/A Series using the MIB file that was sent to them. Resolution Ensure that the correct MIB file is used. Starting in I/A Series R2 version 2.301.528 and above, a new TridiumR2-MIB was created that is supported by R2 Snmp stations. This was created because of the need to differentiate Tridium MIB object identifiers between R2 and G3. I/A Series G3 versions 3.4 and earlier uses TridiumR3-MIB.my MIB file. To view this file in WorkBench, go to 'File' > 'Open' > 'Open Ord' (or shortcut Ctrl + L) and key in 'local:|module://snmp/tridiumMib/TridiumR3-MIB.my'. Starting from I/A Series G3 versions 3.5 and above, there is a Workbench function (right-click menu on the local SNMP device) to create a MIB. See 'About locally generated MIBs' on page 3-17 to 3-21 of the Niagara Ax 3.5 SNMP Driver Guide.

Issue Is the I/A Series product line compliant with federal regulations on being "American-made"?  Is there documentation to support it?  This must include the MNB and MNL controllers, the Niagara UNC and ENC models, and field devices like valves, actuators, and sensors.  Environment I/A Series Cause Government buildings specification Resolution The "schedule" links below provide a list of all products in the I/A Series line that are American-made.  The third link provides a signed statement of declaration. Schedule A Schedule B Declaration

Issue What are the details in getting MNL and MNB controllers pre-loaded with applications from the factory? Environment MNL controllers MNB controllers Workplace Tech Cause Large order of controllers for a job that will require the same application program in each. Resolution The files available on the links below will provide ordering information including part numbers and process. Announcement with part numbers Ordering details

Issue In an existing Niagara G3 ENC-520, version 3.3.22, a station will not load after a reboot.  Prior to the reboot, it was functional.  The error in the Application Director Output is:   "javax.baja.xml.XException: InValid LonFloat: '2.788969984E9'. The only way to get the station started is to modify it offline and remove the logic for a LON integration to an ONICON flow meter.  Then, the modified station gets installed and, once the station is started, the same logic that was removed is added back. Environment Niagara G3 version 3.3.22.5 Cause A bug in the lonworks.jar file for version 3.3.22.5 Resolution Installed the lonworks.jar file from version 3.3.34 which is available below (password=niagara). lonworks.jar

Issue Is there a way to dynamically adjust the “Earliest Start Time” and "Earliest Stop Time" parameter of the I/A Series G3 Optimized Start Stop object? Environment I/A Series G3 Cause The I/A Series G3 Optimized Start Stop object “Earliest Start Time” and "Earliest Stop Time" parameters are accessible via the property sheet view.  A program object is required to allow dynamic interface by the user. Resolution Download the ProgramChangeTime program object and save to a known location on the computer. Copy the ProgramChangeTime object into the station database. Expose the "Earliest Start Time" and "Earliest Stop Time" by pinning the slots to the Optimum Start Stop object.  Right click on the Optimum Start Stop object and select Pin Slots.   Select "Pin" the Earliest Start Time and Earliest Stop Time and Select OK to expose the slots of the object. Link the time output of the ProgramChangeTime object to the Earliest Start Time or Earliest Stop Time input as required.  The Actions (changeTime) of the ProgramChangeTime object allows the user to present a dialog box to dynamically enter a new time.

Issue How to clear all block programming and set the device EEPROM back to factory-default condition. Environment Network 8000 GCM, LCM, LNC or SIM controller including all 84xxx series, 85xxx series or 86xxx series devices. Cause It is sometimes necessary to manually clear the controller EEPROM. Resolution Clear the controller's EEPROM. This is accomplished by pushing the reset button and the EE CLR button and holding both for at least 20 seconds before releasing. The reset process is complete when the top two red LEDs on the right edge of the controller begin blinking in their normal sequence (second LED blinks twice as fast as top LED). This process will clear the user programmable memory (including all block programming), returning the controller to its original factory condition. The procedure above is excerpted from Technical Bulletin 99-27 , steps 1 and 2.

Issue Unable to key in a 'plus' sign (+) in the SMS recipient's Phone Numbers field Environment I/A Series G3 Cause The SMS recipient's phone numbers is required to be entered in international format. The international phone numbers format for sending an SMS is different for different countries. Example (using United Kingdom country code '44'): 00441403740290 or +441403740290 The following I/A Series G3 versions do not allow the 'plus' sign (+) to be entered in the SMS recipient's Phone Numbers field. I/A Series G3 version 3.4 and below I/A Series G3 3.5 versions lower than 3.5.36 I/A Series G3 3.6 versions lower than 3.6.36 Resolution Starting in build 3.5.36, 3.6.36, and 3.7 or later, a phone number may contain a ‘plus’ sign, for example: +441403740290. If you are running I/A Series G3 version 3.4 or below, you can download the updated SMS module here. If you are running a version of I/A Series G3 version 3.5 that is below version 3.5.36, upgrade to the latest version of 3.5 which is 3.5.39. If you are running a version of I/A Series G3 version 3.6 that is below version 3.6.36, upgrade to the latest version of 3.6 which is 3.6.31. These can be downloaded from https://ecobuilding.schneider-electric.com.

Issue In the LON Flow Balance program the k-factor calculated by the balance process can be displayed at the end of the procedure.  I cannot determine how to read it in the BACnet Flow Balance program.  The value is needed so that the application file can be updated so that if the controller needs to be re-downloaded, it will not need to be balanced again. Environment BACnet  MNB-V1 or MNB-V2 controller WorkPlace Tech Tool software release 5.7.2 or newer  (Optional, for backup) Cause The BACnet Flow Balance process uses a procedure that results in a more accurate flow calibration process. As a result of this process the rate box flow value does not get re-calculated during the balance process. Resolution The BACnet MNB-V1 & MNB-V2 controllers do not rely on a calibration constant (k-factor) stored in the application.  The Flow Balance calibration data is stored separately from the application data so that a revised application file can be downloaded to a controller without losing any of the recorded air balance calibration data.  The Flow Balance data is also saved as part of the file produced by the controller backup function of the Workplace Commissioning Tool.  Refer to the WorkPlace Tech Tool 5.7.2 release notes for more information. The Flow Balance calibration data can be displayed after balancing the BACnet MNB-V1 or MNB-V2 controller by clicking on "Balance Data" in the menu on the left side of the Flow Balance screen.  The Flow Balance Data screen shows the data entered and produced as a result of the flow balance process.  Refer to the figure "Flow Balance Reporting -- Flow Balance Details" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  In addition to being able to manually display the balance data for a single controller, both the BACnet Flow Balance program and the WorkPlace Commissioning tool can generate a flow balance for any or all of the BACnet VAV controllers on the jobsite. Refer to the section "Flow Balance Reporting" in the Air Balancing chapter (Chapter 5) of the "MicroNet BACnet Commissioning Tool / Flow Balance Users Guide", F-27358 for more details.  The resulting report is automatically saved when it is generated and the HTML version can be displayed / printed without the need to reopen it in the BACnet Flow Balance program. In addition to being able to manually re-enter the balance data into a replaced controller, Release 5.7.2 of the WorkPlace Tech Tool software introduced a software function that allows the complete application including COV subscription data and flow balance calibration data to be backed up.  Should it be necessary to replace a controller, the WorkPlace Commissioning Tool can be used to restore the backup into the new controller.  Refer to the "WorkPlace Tech Commissioning Tool Backup and Restore feature" section on page 10 of the release notes (F-27526-3) for more information.  The release notes are available here.

Issue Compatible GSM Modem for use with the I/A Series G3 SMS Driver Environment I/A Series G3 Cause An externally purchased GSM modem is required to be used for sending out alarms in an I/A Series G3 system via the G3 SMS driver. Resolution The SMS driver has been tested with Siemens MC35 GSM modem. Technically the driver should work with any GSM modem providing the GSM standard has been implemented properly by the manufacturer. Product Support have tested the Siemens MC35 equivalent modems from Cinterion with the G3 SMS driver (https://www.gemalto.com/m2m). The Cinterion devices, MC35i and MC55i have been used on several sites with no issues reported.

Issue I/A Series R2 Soft JACE part numbers Environment I/A Series R2 Cause Enables a computer to function as a JACE for BACnet IP, oBIX, Modbus TCP, OPC Client and SNMP integrations. Resolution Here are the part numbers to purchase the Soft JACE. TRD-SJ-1M Soft JACE software package with installation instructions and license key (USB), 1,000,000 Java resource count limit. TRD-SJ-3M Soft JACE software package with installation instructions and license key (USB), 3,000,000 Java resource count limit. TRD-SJ-2M-U Upgrade for TRD-SJ-1M to increase Java resource count to 3,000,000 resources total. TRD-SJ-UI Web browser support for Soft JACE TRD-SJ-DB-MSDE Database Services via Microsoft SQL Desktop Engine database (MSDE).  MSDE Server is not included.   Additional drivers' part numbers can be found in the Soft JACE License Request Form. BACnet IP and oBIX are included as standard features in the license. Modbus TCP, OPC (client) and SNMP features require separate purchase(s). Contact your local Schneider Electric sales office for pricing and availability.

Issue How can you determine what standard drivers are included with the basic I/A Series G3 hardware product license? Environment I/A Series G3 (Niagara) hardware License (ENS, ENC, NXT, etc.) Cause Product data sheet is not clear in regards to what license options are included with the standard basic license for an I/A Series G3 hardware products. Resolution Refer to the TAC I/A Series G3 Hardware License Request form. In the "I/A Series G3 Drivers" section of the form there is a box that contains text beginning with "Standard drivers for the xxx include".  This box lists the complete set of standard drivers included with the license for associated hardware product. For example, at the time this is written, the ENC-520 Series TAC I/A Series G3 Hardware License Request form shows the following: This box indicates that the following drivers are included with the standard license for an ENC-520. LON BACnet-IP / BACnet-Ethernet (Client only) BACnet MS/TP oBix Client / Server The ENS-1, ENC-410 and JACE-NXT have similar lists of included drivers.  Refer to the license request form for the hardware product for the list of included drivers.

Issue What I/A Series G3 driver can be used to directly interface a McQuay MicroTech OPM with Microtech legacy controllers to the ENC-520? Environment I/A Series G3, ENC-520 Cause The existing system includes McQuay legacy products (e.g MicroTech 1 controllers) communicating to a MicroTech OPM (Open Protocol Master) panel.  The system does not support open protocols such as BACnet or LonWorks. Resolution The McQuay driver communicates to the MicroTech legacy devices through the McQuay OPM.  The driver is compatible with I/A Series G3 versions 3.4 and higher.  The part number through Schneider Electric is ENC-DRV-MCQ. Click here to download the Niagara McQuay Driver Guide.

Issue I/A Series R2 UNC-600 and UNC-610 BIOS Settings and CMOS Battery Replacement Environment I/A Series R2 UNC-600 and UNC-610 Cause NA Resolution The following publication describes the BIOS settings required when replacing the CMOS battery in the UNC-600 or UNC-610.  Be extremely cautious when replacing the battery as the battery holder can become very brittle with age. TB06-05_UNC6x0_Bios_settings_and_CMOS_Battery_Replacement.pdf

Issue What is the accuracy of the wall sensors used with the Micronet 2000 controllers?  The sensor model numbers are:  MN-S and MN-SDK. Environment Micronet 2000 Cause Required for a job submittal Resolution Click here to view Technical Bulletin 97_35 which provides sensor accuracy details.

Issue Offline generation of MNL-800 database in G3 Niagara Environment G3 Niagara Cause Offline generation of MNL-800 database in G3 Niagara Resolution G3 Niagara provides the XML tool to import XIF files to the G3 environment.  For complete steps click on the link below: How to create MNL-800 devices offline

Issue What 10K Thermistor sensors are compatible with the I/A Series R2 UNC-410 and G3 ENC-410? Environment I/A Series R2, UNC-410, I/A Series G3, ENC-410 Cause Specification information Resolution Compatible sensors include the TS-5700, TS-5711, TS-57011, TS-57031, TS-6700, TSMN-90110 Series, or any sensor that matches the resistance to temperature curve for a 10K Thermistor Type G.  The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Note: Network 8000 sensors (10K with the 11K shunt) are not compatible. US Sensor 10K Thermistor R-T Curve Type G

Issue Can alarms in an Enterprise Network Controller (ENC) station 'pop up' on a computer without an Enterprise Network Server? Environment I/A Series G3 Cause Alarms configured in an ENC station are normally sent to the Enterprise Network Server's Alarm Portal for alarm notification. Alarms in the ENC are required for to 'pop up' on a computer not installed with the Enterprise Network Server. Resolution The Alarm Portal can be separately installed and licensed on a computer without the Enterprise Network Server. The installation package for the standalone Alarm Portal can be downloaded from The Exchange Download Center. Access the Alarm Portal installation package within The Exchange Download Center. Locate the version and download the Alarm Portal installation zip file. The part number for this standalone alarm client is ENS-ALM-CON-G3. Install the Alarm Portal to generate the hostId and request for a license using the Alarm Console License Request Form.  The Alarm Portal can also function as the Alarm client for an Enterprise Network Server station.

Issue When ordering an I/A Series R2 (Niagara) UNC-520-2, is web browser support included? Environment UNC-520-2 UNC-520-WEB Cause UNC-520-WEB is a separately purchased upgrade. Resolution No, it is not included. Order the UNC-520-WEB upgrade in order to add web browser support to the UNC-520-2. See the Specifications Data sheet, "Models", page 3.

Issue Working with a 3rd-party lon controller with no existing shadow object available.  Niagara G3 provides the ability to create a shadow object on the jobsite using the Lon Xml Tool. Environment Niagara G3 Cause A shadow object is not available for a specific 3rd-party controller and a dynamic device fails to interface properly.  Resolution The Lon Xml Tool provides the ability to create a Lon Xml file (.lnml) file for a device, using the source .xif file and (if necessary) other resource files, as made available from the device's manufacturer.  Review Appendix A of the Lonworks Integration Guide for Niagara G3.  The Lon Xml Tool is described starting on page A-1.  This section describes the need for custom Lon Xml files as well as an overview of the process and the steps to create one. docLonworks.pdf

Issue A McQuay MicroTech 2000 water source heat pump controller may be addressed as a Level 3 device under an MCG (MicroTech Communications Gateway). This can be confusing when addressing WSHP1 blocks in a SIM-MTECH. Environment Network 8000 SIM-MTECH McQuay  MCG (MicroTech Communications Gateway) McQuay MicroTech 2000 water source heat pump controllers Cause The MCG needs to use an Echelon communications protocol with the water source heat pump  (WSHP)controllers, which uses level 2 internally, and puts the WSHP controllers at LEVEL 3 Resolution The way to address the WSHP blocks under the MCG is HBYTE = 1, LBYTE = x, where x is the address of the controller.  Unlike earlier McQuay controllers where the unit address is set by rotary hexadecimal switches, the addresses of the MicroTech 2000 heat pump controllers are set in software by the McQuay  technician who commissions their network. Click here to see an excerpt from F-26133, Systems Integration Module- MicroTech, SIM-MTECH. See Fig 2.1, and Table 2.1, pp 2-2 through 2-4