Building Automation Knowledge Base

Issue How do I request a new TIP license for the I/A Series R2 software? Environment I/A Series R2 software installation Cause I/A Series R2 License request process for field offices on the TIP program has changed. Resolution See Product Announcement PA-00186 for details. Please note that the demo license described in this document is only available to our partner offices that participate in the TIP program.  If your office does not participate in the program, please contact your regional sales manager for more information.

Issue Customer has previously purchased the WorkPlace Tech software release 4 and wants to know if there are any controllers available that can be programmed with the release 4. Environment WorkPlace Tech release 4.0 Existing MNL controllers of various releases. Cause WorkPlace Tech release 4.0 generates an error message when an existing application created for an old version of an MNL controller is downloaded into a new controller. Resolution See the section "Controller Firmware Revisions" in Chapter 1 of the WorkPlace Tech Tool 4.0 Engineering Guide for a explanation of the LON controller firmware versions.  If the controller application was programmed for use with an earlier version of the controller,  the application must be updated to the current version before the application can be downloaded into the controller.  Current production controllers contain revision 4.1 firmware.  The revision 4.1 controller model numbers are as follows:  MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F3, R3, H3 , S3 or S4), MNL-11RF3, MNL-13RF3 or MNL-VxRV3 (where x is 1, 2 or 3).    Older production controllers can be identified by the following model number series: MNL-10Rx1, MNL-20Rx1, MNL-VxRV1, MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F2, R2, H2 , S1 or S2), MNL-11RF2, MNL-13RF2 or MNL-VxRV2 To convert the application controller version, use the WorkPlace Tech "Hardware Wizard" after opening the application file. Open the Hardware Wizard. Click the [< Back] button at the bottom of the Hardware Wizard window to display the Controller Selection screen. Note that the current controller version for the application will be displayed in the box at the bottom of the window. If the old controller type is a MN V1, MN V2 or MN V3, select the [MN VAV] tab otherwise select the tab corresponding to the displayed controller type. On the controller selection page, select the model number of the new controller to be used for the application.  If the controllers are using the "Satellite" profile and the old controller was a "Satellite 1" profile, select the "Satellite 3" profile for the new controller.  Select "Satellite 4" if the old controller was a "Satellite 2" profile.  For all other controllers, select the new controller with the same profile type (Fan Coil, Heat Pump, Roof Top) as the original.  After selecting the controller profile for the replacement controller (in step 5), verify that the controller model number shown (MNL-xxxxx) matches the original controller, except for the last digit.  This is the model number of the controller that should be used for the replacement. Click the [Next] button to accept the new controller type selection then click the [Next] button to accept the controller configuration. Click the [Finish] button to exit the Hardware Wizard and apply the changes to the application. The application can then be compiled and downloaded to the new controller.

Issue Is there a way, within the MNB-1000 application program, to determine if communications has been lost between an MNB-1000 and an attached MNB-1000-15 RIO module? Environment MNB-1000 with attached MNB-1000 RIO module(s) Cause The WorkPlace Commissioning tool can display the status of the RIO modules attached to the MNB-1000 but this information is not available within the MNB-1000 application program. Resolution A proposed solution is to use a UO output and a UI input on the same RIO module to allow the MNB-1000 program to monitor the RIO module.  The concept is to drive the UO, 0-20ma with a binary signal from the program. The value would be programmed to change On/Off periodically -- once a minute for example.  The value of the UI would be compared and an internal application alarm generated if the value read from the UI does not agree with the value being written to the UO.

Issue Is there a document that gives the suggested controller to I/O device (field hardware) wiring information?  Wire Gauge, Type of Wire, etc. Environment I/A Series controllers and field hardware Cause Customer wants a document that provides Schneider-Electric's recommendation on controller field wiring. Resolution For the MNB family of controllers, refer to the MicroNet BACnet Wiring, Networking and Best Practices Guide, F-27360. For the MNL family of controllers, refer to the I/A Series MicroNet System Engineering Guide, F-26507. For the Network-8000 family of controllers, refer to the Network 8000 Hardware Installation Practices guide, F-23061. The Network 8000 Hardware Installation Practices guide is also a good guide for field device wiring for use with any family of controllers.

Issue Public time sync Servers for the United States Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment IP Level Devices USA Cause Time synchronization is required for accurate alarming and reporting Resolution Here is a web site referencing several US based Time Sync NTP Servers. http://tf.nist.gov/tf-cgi/servers.cgi

Issue Xenta Server installation on a LON network Environment LNS Network Cause Installing a Xenta Server on a LON network Resolution The Xenta Server can be installed anywhere along the LON channel as long as the terminators are located at each physical end of the wire. The server will function the same as any other LON node.

Issue A schedule was created in the ENC and imported into the ENS, but it can not be edited in the ENS Environment Niagara G3 all versions, ENS, ENC-520, ENC-410 Cause The imported schedule becomes the slave of the original (master) schedule. Only the master schedule can be edited. The slave schedule can not be edited. Resolution If the schedule is to be edited in the ENS, then the schedule must first be created in the ENS and then imported into the ENC.

Issue After installing WorkPlace Tech 5.8 the Hardware wizard cannot be accessed. Environment I/A Series WorkPlace Tech Cause Earlier versions of WPT 5.7.4, 5.7.5, 5.7.6 and 5.7.7 when uninstalled leave behind files that can cause such an issue. Resolution The simplest solution is to uninstall WPT58 and re-install it.  The uninstall of WPT58 will remove the extraneous files so the next install will function properly.

Issue Points can be overriden in the field using PSI; have verified the standard 'USER' and 'PASS' login for all Microzones and the LCM; the GCM is able to be downloaded successfully. Still having trouble with overriding points in a Microzone II via TreeTech. It returns error 'no user found'. Environment TreeTech Network 8000 Microzone II under GCM Cause The date in the GCM & any Microzone/PEM controllers must match that in the PC with TreeTech since the password to access the controller is calculated based on dates. Resolution The date in the GCM & any Microzone/PEM controllers must match that in the PC with TreeTech since the password to access the controller is calculated based on dates. If TreeTech can't Login, you can't override the MZ2. Check the dates in the PC and all devices match and correct if necessary.  

Issue What is the best way to remove a version of R2 software from a PC? Environment I/A Series Niagara r2 Cause A formal uninstaller does not exist. Resolution Stop the Niagara service Delete the r2.301.XXX folder containing the version you wish to remove.

Issue Attempting to view I/A Series G3 graphics via browser. Error indicates HTTP 501 "Not Implemented" error with the message "Module content filter excludes user interface packages." Environment I/A Series G3, ENC-410, ENC-520 Cause When an ENC is accessed from a browser, it is necessary that the user interface packages be available to correctly render the web-based display.  When these packages have been filtered out, the browser will report an HTTP 501 "Not Implemented" error with the message "Module content filter excludes user interface packages." Resolution To correct the module content filter must be changed to include the UI package and the associated modules must be re-installed. Open the platform for the ENC and run the Commissioning Wizard. Clear all selections and enable "Select module content filter level." Step through the commissioning process and change the Module Content Filter Level to UI+RUNTIME. Continue through the commissioning process and Finish to install the UI modules.

Issue What to do and who to contact when a controller needs to be repaired or upgraded. Environment All Product Repairs Cause Require information on what to do and who to contact to arrange repairs of defective product, order Controller option upgrades, order Cyberstation option or software version upgrades. Resolution   PROCESS FOR CONTINUUM REPAIRS   NOTE: Repaired items are set-up in Pronto with the part number prefixed by “4-“. This is done to allow visibility for follow-up if required and costing.   Engineer completes “Andover Continuum Hardware Return Authorisation Form”; one for each controller requiring repair. Email completed form/s to TAC AP – Logistics Replenishment ( NOT the US Repair Centre). Do nothing with the controller/s at this stage. Logistics email the completed forms to US Repair Centre requesting cost to repair and turn-around time. Repair Centre replies with cost, turn-around time and RA number/s Logistics pass this information to the requesting engineer who will decide Y or N. If yes, the engineer enters a Sales Order in Pronto, informs Logistics and forwards the goods to Melbourne DC. Logistics raise a Purchase Order on Repair Centre and instruct Melbourne DC to despatch goods. After the goods are repaired they are returned to Melbourne DC where they are receipted and despatched to requestor.   Repair Forms Fill out one of the forms below (whichever applies) and send to local Logistics. Andover Continuum Return Authorization Forms - Americas & APAC OR Andover Continuum Controller Upgrade Forms - Americas & APAC

Issue "Cannot paste. /tridium/props/error.properties#error.E_RC_TO_NODE" when trying to paste a Lon shadow object into the workspace of an UNC. Environment Niagara R2 UNC-410 UNC-520 Cause There could be two possible causes for the error message. One possible cause is that the Lon jar file which contains the shadow object was updated on the WorkPlace Pro PC, but the updated module was never installed to the UNC. The other possible cause is that the updated Lon nt jar file was not installed in the \nre\modules folder of the WorkPlace Pro PC. Resolution There are two things to look into. Perform both procedures 1 and 2 only if the lon nt jar was not installed/upgraded to the nre\module folder.  If all of the Lon jars are installed/upgraded correctly (Lon nt jar file installed to nre\modules folder) on the WorkPlace Pro PC, then only procedure 2 needs to be performed. Procedure 1 If the lon nt file was not installed/updated to the \nre\modules folder, use the following steps to do so. These steps assume that the updated Lon nt jar is already installed on the WorkPlace Pro PC, but not it was not installed to the nre\modules folder. Stop WorkPlace Pro. Open the Niagara\build\nt and copy the Lon jar Open the niagara\build\nre\module folder and rename the Lon jar in question “.old”. Paste the copied Lon jar to the module folder and restart WorkPlace Pro. The module will now need to be upgraded to the UNC. See above steps for procedure. Procedure 2 If the UNC Lon module has not been installed/updated to the UNC, use the following steps to do so. Open the Admin Tool. Open a connection to the UNC Select the "Installation" tab then click the [Installation Wizard] button. Select the "emb" folder in the "Select Distribution Directory" window then click [Install] In the "Niagara Remote Installation" window, select the "Configure Modules Only" radio button then click the [Next >] button. Verify that there is a checkmark in the "Upgrade/Add" column for the updated lon jar file. Click the [Next >] button to continue. Make sure that on the "Database Backup" screen that you do backup the existing database. Continue through the remaining steps and allow the upgrade to install and the station to restart. You should now be able to paste the shadow object to the WorkspaceEditor view.

Issue A Niagara R2 station is being upgraded from version 431 to 529.  A copy of the station from 431 is successfully converted to xml.  However, the config.xml does not convert to a config.db or a config.sns in version 529. The following error appears in the conversion window: ------- Errors ------- ERROR: c:\niagara\r2.301.529\stations\Blake\config.xml(630110,66):    Could not parse value.    Invalid dateTime "60356-06-20T10:54:24.17-7". Parse of XML failed. ----- End of input ----- Environment Niagara R2 all versions Cause Somehow, an incorrect date reference was registered in the station.  It may have occurred during the creation of the config.xml. Resolution Using a XML editor utility (ie: Notepad++), modify the date so that it reads "2011" instead of "60356". from:  <lastDailyArchive>60356-06-20T10:54:24.17-7</lastDailyArchive> to:      <lastDailyArchive>2011-06-20T10:54:24.17-7</lastDailyArchive> Run a conversion again.

Issue Unable to commission an I/A Series JACE-6 or JACE-7. The commissioning wizard cannot locate the sun-jre-qnx-ppc distribution file required for the installation process. Environment I/A Series G3, JACE-6, JACE-7 Cause The sun-jre-qnx-ppc distribution file was not included in the initial TAC release of build 3.6.31.6.  in addition, the Sun Hotspot Virtual Machine (JVM) for the QNX operating system included with the 3.6.31.6 build was found to have timing issues. Review TPA-IA-11-0005.00 for more details. Resolution The initial TAC release of build 3.6.31.6 was removed for download within a few days of original release.  The software was replaced by TAC build 3.6.31.7 (dated 09/29/2011). For those using I/A Series G3 Release 3.6 you must take the following actions: Discontinue using G3 release build 3.6.31.6.   Download and install the latest build, G3 release 3.6.31.7 from The Exchange Download Center.   For those instances where deployment has already occurred in the following JACE platforms JACE-6 or JACE-7, an upgrade to G3 3.6.31.7 is required. Note: The version of the Sun Hotspot JVM can be verified using the Workbench Platform tool – Platform Administration. The Java Virtual Machine (sun-jre-qnx-ppc) should indicate Sun Microsystems Inc 1.5.0.16.21 or higher.   The Enterprise Network Server, ENC-410, ENC-520, and JACE-2 platforms do not utilize the Sun Hotspot Java Virtual Machine (JVM) for QNX.  These platforms are not affected by the issue. However, it is strongly recommended to upgrade to G3 3.6.31.7 to maintain compatibility with the same version of Workbench and associated files.

Issue Too much LON communications traffic can cause LON communications errors. Environment MNL-50, MNL-100, MNL-150, MNL-200, MNL-110, MNL-130, MNL-VxRVx controllers Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution In a particular application the engineer needs to consider the amount of data being transmitted on the LON network due to LON network bandwidth limitations.  On an FTT-10 LON network, the bandwidth is limited to approximately 72 packets (messages) per second.  Because the LON network is operating using CDMA (Collision Detect, Multiple Access) communications techniques, data collisions will reduce the practical data limit to approximately 1/2 of the maximum.  Typically the LON network designer will limit the packet transmission rate of 30 to 35 packets per second.  There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. The nciSndHrtBt determines the maximum amount of time that is allowed before all bound NVOs are updated, that is, the data is marked to be "re-sent" to all bound nodes.  This value is typically set to 120 seconds, causing all bound NVO SNVT values to be transmitted at least once every two minutes. The nciRcvHrtBt sets the fallback timer value for each NVI object.  If a value is not received via a binding in this time period, the NVI object will revert to its application defined default value.  It should be noted that this value does not directly affect the LON bandwidth but it does affect how the controller handles the loss of the bound data communications.  This value is typically set to about 2.5 times the nciSntHrtBt to allow for occasional lost communications packets and delays due to data collisions occurring on the network. The nciMinOutTm controls how often a bound NVO value will be transmitted when the value is changing within the controller.  Each specific SNVT type has a specific data resolution and any time the data value changes by one count, the value will be sent.  For example a temperature value bound through a NVO as a SNVT_temp_p type has a resolution of 0.01 degrees Celsius.  If bound this temperature NVO will be transmitted each time the value changes by 0.01 degrees C.  The setting of the nciMinOutTm throttles this bound NVO value transmission by forcing the controller to ignore any changes to that NVO value for a specific time interval each time it is transmitted.   The nciMinOutTm value defaults to NA causing the bound NVO value to be transmitted each time it changes.  Typically the nciMinOutTm is set to a value in the 1 to 5 second range causing the controller to throttle the transmission of the changing NVO values.

Issue AVG Internet Security Suite Business Edition 2012 has been installed on Enterprise Network Server computer at customer site.  After the installation, no connection can be made between either the ENS or Workbench from that computer even though all Windows firewall functions have been disabled. Environment I/A Series G3 ENS installation on Windows computer. Computer protected with AVG Internet Security Suite Business Edition 2012 Cause The Link Scanner function of the AVG Internet Security Suite Business Edition 2012 acts as a smart firewall Resolution The Link Scanner function of the AVG Internet Security Suite Business Edition 2012 must be configured to allow point to point Ethernet connections between the ENS/Workbench computer and each ENC used on the jobsite.  Refer to AVG Internet Security Suite Business Edition 2012 documentation for more information and instructions.

Issue Unable to send email from I/A Series R2 Enterprise Server.  Error indicates "datax:nohandler for: notification." Environment I/A Series R2 Enterprise Server Cause The I/A Series R2 Enterprise Server station has it's NotificationService 'archiveMode' property set to 'archive_disabled'.  This is the default selection and it prevents notification from processing. Resolution Change the default in the I/A Series R2 Enterprise Server: Configure the Enterprise Server station's NotificationService 'archiveMode' to 'archive_local'.

Issue Attempting to connect the I/A Series G3 Enterprise Network Server to an ENC and getting a Niagara Station Fault Cause License Exception. Authentication Failed: Exceeded Device limit of 0. Environment I/A Series G3, Enterprise Server, ENC-410, ENC-520 Cause Communications between the I/A Series G3 Enterprise Network Server and ENC-410/520 requires that both are licensed to for peer-to-peer (Niagara Driver) support.  The error indicates the ENC is not licensed for peer-to-peer. Resolution Use Workbench License Manager to "view" the license in the ENC. Locate the feature for niagaraDriver and verify the device.limit is none.  A device.limit of 0 indicates the ENC requires the addition of the P2P option. To add the peer-to-peer option ... ENC-410-1 ... purchase ENC-410-P2P. ENC-520-2 ... purchase ENC-520-P2P.

Issue Does Niagara G3 provide a method to throttle rapidly changing BACnet proxy point values so they don't overwhelm the network with traffic? Environment Niagara G3, ENC-410, ENC-520 Cause Rapidly changing BACnet proxy point overwhelming the network with traffic. Resolution The Min Write Time property applies to writable proxy points, especially ones that have one or more linked inputs. It specifies the minimum amount of time allowed between writes. It provides a method to throttle rapidly changing values so that only the last value is written. If this property value is 0 (default), this rule is disabled (all value changes attempt to write). The Min Write Time of the Tuning Policy can be set to limit the frequency of rapidly changing proxy points being sent. 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 minimum time to be used in the Min Write Time property. 5. Save change