Building Automation Knowledge Base

Issue The outputs of three kitControl objects - Maximum, Minimum, and Average - will all go to Nan if any of its inputs are Nan. Product Line TAC IA Series Environment I/A Series G3 (Niagara) station Cause The internal logic of these blocks is set to pass Nan through if all inputs are not valid for comparison. Resolution There are two potential work-arounds: Pass the inputs through some intermediate logic to ensure that a Nan value is never passed to the Minimum, Maximum, or Average blocks. Null values are valid and will allow the internal logic of the block to proceed. Use the MinMaxAvg block instead. It is located in the kitControl > Util folder. The internal logic of this block will ignore Nan inputs.

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.

Issue Is it okay to leave BACnet/IP or BACnet/Ethernet port enabled on an I/A MNB-1000 even if it's not physically connected to a network? Product Line TAC IA Series Environment WorkPlace Tech MNB-1000, all versions Cause Leaving BACnet/IP or BACnet/Ethernet enabled means that the MNB-1000 is acting as a router. The MNB-1000 thinks there are networks present and tries to route to them. This produces routing loops. Resolution When an MNB-1000 is configured as an MS/TP-only device, and does not use BACnet/IP or BACnet/Ethernet, be sure that BACnet/IP and BACnet/Ethernet are both disabled. Caution: The MNB-1000 is not recommended to be use as an MSTP device.  It is meant to be used as a BACnet/IP or BACnet/ Ethernet device. Note: If either BACnet/IP or BACnet/Ethernet is needed for maintenance reasons, you can access the MNB-1000 via the MS/TP trunk and enable the necessary port. Once you maintenance is completed, disable the unused port again.

Issue I/A Series MNL-VAV controller continues to display a small air flow value (CFM or L/S) even when airflow is not present (zero flow conditions). This condition is typically seen as small CFM readings on graphics screens when air is not present (AHU off condition). Product Line TAC IA Series Environment MNL-V1RV3-2, MNL-V2RV3-2, or MNL-V3RV3 Cause The I/A Series MNL-V1, V2, V3 and controller platforms were recently redesigned to incorporate the latest Echelon FT 5000 Neuron Smart transceiver. With no air flow, when the fan system is not running, minor fluctuations in duct pressure could result in false air flow readings from the MNL-V1RV3-2, MNL-V2RV3-2, and MNL-V3RV3. Resolution Use the MNL Firmware Updater Utility to update the MNL-V1RV3-2, MNL-V2RV3-2, or MNL-V3RV3 controller firmware to version 4.3B5. A velocity pressure reading below 0.005 in. WC (1.25 Pa) will be processed within the controller as no or zero flow. Controllers within these date code ranges should be updated with the utility detailed below. MNL-V1 and MNL-V3 starting with date codes of 1208 MNL-V2 starting with date codes of 1212 Note: The MNL VAV control range of 0.05 to 2.00 in. WC (12.5 to 498.2 Pa) is not affected. When air flow control below 0.05 in. WC is required, the I/A Series MNB VAV controllers, with a control range of 0.004 to 1.5 in. WC (1.0 to 373.6 Pa), should be used. MNL Firmware Updater Utility The MNL Firmware Updater 4_3B5.zip can be downloaded from The Exchange Download Center. The zip file contains these instructions and the “MNL Updater Setup.exe”. Executing “MNL Updater Setup.exe” will place the latest firmware into C:\Program Files\Schneider Electric\MNL Firmware Updater\bin and add the installer to the Start Menu item under Schneider Electric. MNL-V1RV3-2, MNL-V2RV3-2, and MNL-V3RV3 controller firmware version 4.3B5 MNL-5 controller firmware version 4.3A5 If the MNL Firmware Updater had previously been installed, the MNL-V1RV3.NDL, MNL-V2RV3.NDL, and MNL-V3RV3.NDL files located in "C:\Program Files\Schneider Electric\MNL Firmware Updater\bin" will be replaced.

Issue In a Niagara G3 station, whenever someone logs into the graphics (with any web browser), the following error appears in the application director output: javax.baja.xml.XException: Root element must be "nav" [line 3]  at javax.baja.nav.NavFileDecoder.err(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.decodeDocument(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.nav.NavFileDecoder.load(NavFileDecoder.java)  at javax.baja.user.BUser.getHomePage(BUser.java)  at com.tridium.fox.sys.user.BUserChannel.fetchPrefs(BUserChannel.java)  at com.tridium.fox.sys.user.BUserChannel.process(BUserChannel.java)  at com.tridium.fox.sys.BFoxConnection.process(BFoxConnection.java)  at com.tridium.fox.session.SessionDispatcher.dispatch(SessionDispatcher.java)  at com.tridium.fox.session.SessionDispatcher.run(SessionDispatcher.java)  at java.lang.Thread.run(Unknown Source) Product Line TAC IA Series Environment Niagara G3 Cause The G3 user account has the nav file property pointed to a file that is not a nav file. Resolution Correct the nav file property setting.

Issue A Niagara R2 Enterprise Server station is extremely slow in starting, and there are hundreds of alarms. Is there a way to delete all the alarms? Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause Storing unwanted various alarms can cause the station to boot slow. Resolution The alarms can be deleted in two ways. The first method is to delete the app folder under the station directory. The entire historical content of the station will be deleted. This includes archived trends, alarms, and events. Follow the steps below to delete the app folder. Deleting the app folder to clear the contents of the database only applies to a Cloudscape installation. Open windows explorer and navigate to Niagara\station\[station name]\app Delete or move the app folder Restart the station The second method, is to use the appdb/queryForm servlet to selectively remove data from each table including alarms. This is done by using a web browser. Depending on the size of the database this method may take a substantial amount of time. Follow the steps below to delete data from the database by using SQL queries. Open a web browser and navigate to http://[ipaddress]/appdb/queryForm In the form, enter the following query - delete from event.eventhistory This will delete all history data in this table. For further information refer to the SQL_Tutorial\QueryExamples_10_6_04.pdf

Issue In Niagara G3, how do I display an object's BACnet instance number within the object in the Wire Sheet? Product Line TAC IA Series Environment Niagara G3 all versions Cause The BACnet object ID is not displayed by default. Resolution Steps for displaying the BACnet object’s ID in the object Right-click in the BACnet object you want to display its objectID and select Slot Sheet Right-click on the view pane and select "Add Slot". Enter "objectID" for Name For Type, select "bacnet" and "BacnetObjectIdentifier" from the drop-down menu and then select "OK" to save Expand the BACnet object in the tree and right-click its "Proxy Ent" and select "Link Mark" from the drop-down menu Right-click on the BACnet object in the tree and select "Link from "Proxy Ent"" Under Proxy Ext (Source) select "Object ID", and under the BACnet object (Target) select "ObjectID" and then click on the OK button The BACnet ObjectID will now be displayed in the object.

Issue Can a UNC be setup as a BACnet server to expose its native Niagara objects as BACnet objects? Product Line TAC IA Series Environment Niagara R2 UNC-520 Cause By default, the UNC can only act as a BACnet client, not as a BACnet Server. A UNC-520 can be configured as a BACnet Server. Resolution Steps for configuring exposing native Niagara objects and BACnet objects: Open the properties of the native Niagara object you want to expose as a BACnet object. Click on its Config tab The foreignAddress must be changed from its default of “-1” to an integer from 0 - 4194302. (BACnet instance number rules applies) Apply the change The object is now exposed as a BACnet object. The following standard Niagara objects can be exposed and BACnet objects: AnalogInput (AI) AnalogOutput (AO) BinaryInput (BI) BinaryOutput (BO) MultistateInput (MSI) MultistateOutput (MSO) Calendar Schedule Reference Chapter 4 of the "BACnet Integration Reference" guide for more detailed information.

Issue Can the actuator collar and set-screws for the VAV controllers (MNL, MNB, MicroNet 2000 product lines) be purchased separately? Product Line TAC IA Series Environment VAV controllers (MNL, MNB, MicroNet 2000 product lines) Cause Replace parts in the VAV (Variable Air Volume) controllers. Resolution Actuator collars and set screws for VAVs can only be purchased in a retrofit/enhancement capacity as detailed in Product Announcement 06-030. The part number for ordering is DCQC-234-10.

Issue When balancing a MNB VAV box with WorkPlace Tech Flow Balance tool it fails when starting the "Maximum flow" function with an error that states "Unable to read previous balance values." Product Line TAC IA Series Environment MNB VAV WorkPlace Tech Cause This error indicates there is invalid data in the memory location where the balance data is stored. Resolution To clear the error: Open the WorkPlace Commissioning tool Select the VAV box in question and launch the flow balance software from the WorkPlace Commissioning tool. Balance page opens. Click on "Balance Data" in the left column. On the "Flow Balance Details" window, click on the "clear" button Click OK. Start the Flow Balance process again.

Issue Where can I find the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets? Product Line TAC IA Series Environment WorkPlace Tech Tool software I/A Series MNB BACnet family of controllers I/A Series MNL LON family of controllers Cause There is no single online source for the all the current documentation for the WorkPlace Tech Tool software, MNL LON controllers, MNB BACnet controllers and their associated specification data sheets. Resolution All documentation related to the WorkPlace Tech Tool (WPT, WPCT & WPFB) and related controller documents are installed to your computer when you install the WorkPlace Tech Tool software. At the time of release, the current version of each software manual, hardware installation manual (LON & BACnet), specification data sheet (LON, BACnet & Software) and the software release notes document is built into the software installation program. These documents are all accessible under the \WorkPlace Tech\Help folder on any computer where the WorkPlace Tech Tool software is installed. All documentation can be displayed from the list displayed by the WorkPlace Tech Help menu. This was done to insure that all WorkPlace Tech Tool users would have access to the version of all documents related to that specific release of the software. Since these documents are included in the installation package for any version of the WorkPlace Tech Tool software, you can download the latest WorkPlace Tech Tool installation file from The Exchange Download Center to get the complete set of documents. These documents are also available individually from the 'Publication Zone', accessible from the 'Links' menu on iPortal (https://iportal2.schneider-electric.com).

Issue What is the factory default IP address for a new I/A Series G3 JACE-6 or JACE-7? Product Line TAC IA Series Environment I/A Series G3 JACE-6 JACE-7 Cause Initial power up and connection to Workbench Resolution Two female 10/100-Mbit Ethernet connections are provided on the JACE-6 and JACE-7 hardware platforms. These are RJ-45 connectors labeled LAN2 and LAN1. Use a standard Ethernet patch cable for connecting to a hub or Ethernet switch. An activity LED for each Ethernet port is visible, and are labeled "LAN2" and "LAN1" on the cover. The factory-default IP address for LAN1 on the JACE-6 and JACE-7 is 192.168.1.12n, where the last numeral n in the address matches the last digit of the JACE's serial number, and subnet mask is 255.255.255.0. By default, LAN2 on the JACE-6 and JACE-7 is disabled. The factory default platform username and password is tridium / niagara.

Issue When should end-of-line (EoL) terminating resistors be installed on a BACnet/MSTP network? Product Line TAC IA Series Environment BACnet/MSTP network Cause Knowing where to implement the termination helps reduce signal reflections, which might cause issues in the system. Resolution Resistors of 120 ohm value must be installed at each end of a MSTP (or RS-485) trunk segment. They help reduce signal reflections and RF interference. Failure to install end-of-line resistors may result in intermittent communications.

Issue The output of the actuator block in a MNB-Vx sometimes shows 'NaN' (Not a Number) instead of a valid position. The only way to clear it is to drive it fully open or fully closed. The issue is intermittent and it is not specific to the same installed controllers. It appears on different controllers at different times. Product Line TAC IA Series Environment MNB-Vx Cause The actuator can be initialized to avoid displaying 'NaN'. The setting in the VAV actuator block is called InitMode. Here's a description of this setting from the WorkPlace Tech Engineering Guide Supplement (F-27356): Abbreviation Configuration Property Description Range InitMode Initialization Mode Class: Enumeration - The initialization mode configuration property controls synchronization of the VAV object position output after a rest. 0 - No automatic synchronization of the position output. Synchronization occurs when normal control causes the actuator to drive full open or full closed. 1 - Actuator drives full closed after a controller reset to synchronize position output 2 - Actuator drives full open after a controller reset to synchronize position output 0-2 If InitMode = 0, and the actuator doesn't drive full open or full closed for a long period of time, the NaN value will continue to be displayed. Resolution Ensure InitMode is set to either 1 or 2 so that it synchronizes after a power cycle or database download.

Issue When accessing the Platform Diagnostics information from the Station Spy in an I/A Series G3 station, the log, log1, and log2 system log files can be displayed but not directly downloaded.  How can these log files be downloaded? Product Line TAC IA Series Environment I/A Series G3 ENC Cause Needs to be able to download the log files so that they may be emailed for analysis. Resolution These log files and the other diagnostic files displayed through the Station Spy platform diagnostics can be displayed or downloaded by accessing them through the web browser, as follows. Connect to the station at the address "http://:3011/qnx. When prompted, log in using the hardware user name and password. To display the specific diagnostic information in the web browser, double click the entry. To download specific diagnostic information, such as log1, right-click the entry and select "Save Target as" (in Internet Explorer) or "Save Link as" (in Firefox), then select the location and specify the name where the file is to be saved.

Issue WorkPlace Commissioning Tool is displaying third party devices in red.  Product Line TAC IA Series Environment I/A Series WorkPlace Commissioning Tool Cause When the WorkPlace Commissioning Tool discovers a device (if Extended Data in selected) it will display the devices name as learned from the device.  If a device name is not unique it will be displayed in red. Resolution Displaying the devices in red does not suggest trouble, but rather indicates duplicate device names were discovered (see F-27358 WorkPlace Commissioning Tool and Flow Balance Tool Users Guide Chapter, "Device Icons").  The device name assigned by a third party manufacturer is not something the WorkPlace Commissioning Tool is designed to alter.

Issue In Niagara R2, is there a way to stop alarm notification from being generated and forwarded when a boiler is down for maintenance or other reason? Product Line TAC IA Series Environment Niagara R2 Cause Logic programming for preventing nuisance alarms Resolution This can be accomplished by adding a Binary Output (BO) object. Link the StatusOutput of the BO to the StatusInhibit of the Analog Input object (the AI alarm being inhibited).  Note that the inhibitTime property of the AI object has to be some value other than its default value.  It doesn't matter what value, but it must be something other than zero in order for it to function correctly.  In a real world application the BO object would be the output from an object which indicates that the boiler is down or offline; or it could also be from a manually activated GxPage object which would indicate that the boiler is down. With either setup, when the boiler is down and the appropriate input signal is feed into the StatusInhibit of the AI object, the AI object will not produce an alarm even when an alarm condition is present. Proper functioning should be verified before being placed into a working application.

Issue After reviewing a DMS installation, the red end-of-line (EOL) termination modules are not installed on the Microsmart trunk. The original part number was N406-032. Are they available for purchase? Product Line TAC IA Series Environment DMS Cause Part number cross reference Resolution The part number is changed to RBSC-16. Use this number when contacting customer support services.

Issue Reverting to an older than installed version of the firmware is required. Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB 1000 Cause Prior to the 1.515 version of the firmware, it is not possible to revert to an older release of the firmware. Resolution Firmware after 1.515 has the ability to be reverted. 1.515 is the oldest version the controller can be installed with.  If this procedure is required, please contact your countries Product Support for more information.

Issue MNB Controller firmware upgrade failed, which resulted in the device showing a blinking-red status LED. Product Line TAC IA Series Environment I/A Series MNB Controllers (ASC) (All firmware revisions) Note: This does not apply to the MNB-1000 Cause A blinking-red status LED means the MNB controller is in Boot Loader mode and it cannot reboot. It is now a "slave" unit, listening to traffic, not initiating communication. Resolution Using the WorkPlace Commissioning Tool, click on the File pull-down menu and select "Add MS/TP Slave". If asked to select from IP, Ethernet or MS/TP, select MS/TP. (Note: It's a good idea to have the controller isolated from the trunk, so the firmware upgrade process runs less risk of being interrupted.) At the prompt for the address, enter the address set on the controller DIP switch. The controller should get added to the list. If it is already in the list, a message will indicate that there's a duplicate address. Answer prompts in such a manner to get the controller added to the list. The 'slave' controller may show up with a blank name. Do the firmware upgrade again. This procedure works 80% of the time. If the upgrade fails, put the controller into Dedicated Boot Loader Mode. Take the controller off the MSTP trunk, set the DIP switch address to 254, cycle power, and try another firmware upgrade (keep it addressed as 254). Following a successful firmware upgrade, set the DIP switch back to the correct controller address and cycle power to the controller.