Building Automation Knowledge Base

Issue The file structure is incorrect for MNL-FLOW-BAL 3.0 software for use with Windows 7 64 bit OS.  The FlowBalance.exe needs to be run in Windows XP (Service Pack 3) compatibility mode. Product Line TAC IA Series Environment Windows 7 64 bit MNL-FLOW-BAL Balance Software Cause The paths for certain files being used by the software cannot be modified. When loaded on a 64 bit PC, the default paths are incorrect for the rest of the processes to find. Resolution Manually create and insert the folder structure required. Set the FlowBalance.exe compatibility Copy the TAC folder in the Program Files (x86) folder from Windows Explorer. Paste into the Program Files folder Open the pasted TAC folder and delete all the files except for the XIF folder and the FlowBalance.cfg file in the LON FlowBalance folder. Right-click the FlowBalance.exe icon created on the desktop Open properties/compatibility tab. Set as Windows XP (Service Pack 3)

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Receive an error, "Invalid Device " when trying to download an application to an I/A Series LonMark controller with Workplace Tech. Product Line TAC IA Series Environment I/A Series LonMark (MNL-5Rxx, MNL-10Rxx, MNL-20Rxx, MNL-11RFx, MNL-13RFx, MNL-V1RVx, MNL-V2RVx, MNL-V3Rvx) Workplace Tech Cause Typically, this situation occurs when a user runs the Hardware Wizard in Workplace Tech and then downloads a controller without recompiling the application. Resolution See Technical Bulletin TB06-01 for detailed information and a solution.

Warning Issue UNC-520 heartbeat LED had no activity but the UNC appears to be running without issues.  Environment I/A Series Universal Network Controller - UNC-520 Cause The UNC CPU idle is at 0% which resulted in the UNC heartbeat LED not having any activity (always off).  In this case,  this is caused by changing the ControlEngineService executionFrequencies to faster values and objects' executionParameters frequency set to faster or fastest. The station is using large amount of CPU resources.  Resolution To correct this make the following adjustments:  In the ControlEngineService properties, Config tab, change the executionFrequencies back to the default values of fastest at 500ms, faster at 1s, normal at 2s and slower at 5s.    Change the objects' executionParameters frequencies back to the default setting of normal. You can used the AdminTool object to perform a search and replace and changed all the executionParameters frequencies to normal.  There may be a need to change these values from the default values to optimize the UNC performance. Refer to the Niagara Capacities Engineering Notes for details. You should contact Product Support if you are unsure of these settings. 

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue How do I locate the latest patch files (modules) for the I/A Series G3 maintenance builds (3.6.407, 3.7.108, 3.8.41) Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.407, 3.7.108, and 3.8.41 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution The latest consolidated patch files for I/A Series G3 maintenance builds 3.6.407, 3.7.108, 3.8.41 are listed below.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric EcoBuildings Exchange Extranet and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes bacnet3.6.407.2 baja 3.6.407.3 eibnetip 3.6.407.1 hx 3.6.407.1 mbus 3.6.407.3 ndriver 3.6.407.1             Consolidated_Patches_3.7.108.2.7_SE_02092016.zip   ...  Click here for Release Notes     Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes   Consolidated_Patches_3.7.108.2.7.1_SE_06282016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1 weather 3.7.108.1   Consolidated_Patches_3.8.41.2.9.1_SE_06282016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 weather 3.8.41.1 web 3.8.41.1           ********* Previous Release History ********* Consolidated_Patches_3.7.108.2.7_SE_02092016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1       Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes bacnet 3.8.41.12 baja 3.8.41.2 bajaui 3.8.41.1 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.1 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1 Consolidated_Patches_3.8.41.2.9_SE_04052016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1   Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes

Issue Where can I get information and documents on the Building Analytics service? Environment Building Analytics Cause Information and documentation is required on this product. Resolution Available documentation is available on the Download Center A diagram of network architectures can be seen Here.

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue After upgrading to Niagara G3 3.8 (from 3.7), nested PxIncludes now only partially load and very slowly.  They are not all entirely missing.  After a screen refresh, most will load except for a random few.  Also, they may load all at one moment but not the next.  The same Px file in version 3.7 loads faster with nothing missing. Environment Niagara G3 / AX version 3.8 Cause PxInclude caching is disabled by default in 3.8. Resolution This issue was addressed with the release of an updated bajaui module - version 3.8.38.3.  This version re-enables PxInclude caching.  Download it here.

Issue Robertshaw T99-112 RTD Immersion Temperature Sensor - Specification Sheet & Temperature / Resistance Table Environment DMS MicroSmart Cause Create a custom temperature / resistance object in Niagara, SBO, etc... Resolution Spec & T/R table available here.

Issue Existing sensor has failed (TS-5751-850).  The application involves below freezing temperatures (not outside air but a storage freezer).  Since the sensor is obsolete, what's a suggested replacement? Environment Network 8000 MicroZone II Cause Sensor failure Resolution Try the TO series sensor from Veris Industries.

Issue Installation flowchart for a network SIGNAL software installation Environment SIGNAL network version Cause Installation documentation Resolution Installation flowchart available in the Network Supplement of SIGNAL (F-25952), page 9 (pdf) or page 7 (paper)

Issue Trying to use OPRIF to make a few programming changes to a MicroSmart controller. OPRIF is installed on a SIGNAL computer (Windows 98). With SIGNAL disabled, OPRIF is able to start and handshake with the COM port. However the Auto Answer feature is enabled by default and begins an endless loop of trying to synchronize with the modem. The looping effect prevents a proper connection to the DMS to do programming changes. How can the Auto Answer be disabled on startup of OPRIF? Product Line TAC IA Series Environment OPRIF or Operator Interface version 11.4 and higher Cause Initialization file was modified by default Resolution The readme.txt file in the DMS folder explains how to prevent Auto Answer from being enabled on startup of OPRIF. Click here to view the entire readme file. Below is the excerpt on how to disable Auto Answer: Changes to the command strings used for modem-initialization and control The default modem init-string "AT C1 E1 V1 S0=1 S7=51" has been changed. It is now "AT&C1&D2E1V1". If you or your modem don't like this string, you can now override the default. Using NOTEPAD or EDIT, create a file called MODEM.INI in the DMS directory. This file should contain a single line of ASCII, which will be your customized initialization string. The line must begin with the letters "AT", and must not contain the letters "DT". Other than this one restriction, your modem-init string can contain whatever commands your modem requires. Two separate default strings have been defined for turning auto-answer ON and OFF. These may be overridden by creating files with the appropriate names in the DMS directory. To specify a customized string to force your modem to STOP auto-answering, use NOTEPAD or EDIT to create file a called ANSWEROF.INI in the DMS directory. By default, this file would contain the single ASCII line "ATS0=0". If your modem requires a disconnect command, you could instead write a line that reads "ATH ATS0=0". The default autoanswer ON string "ATS0=1", instructs the modem to answer on the first ring. To answer on the third ring, use NOTEPAD or EDIT to create a file called ANSWERON.INI in the DMS directory. It should contain the single ASCII line "ATS0=3". SUMMARY: Description Default String Filename Comment Modem Initialize AT&C1&D2E1V1 \DMS\MODEM.INI Modified in 11.4 Auto-answer On ATS0=1 \DMS\ANSWERON.INI New in 11.4 Auto-answer Off ATS0=0 \DMS\ANSWEROF.INI New in 11.4

Issue The AX Serial Tunnel service does not initialize on a station startup: ---------- Station Starting: FRI JUL 11 14:02:45 2014 ---------- Tridium Niagara Station, r2.301.529.v1 [WFU_UNC06] MESSAGE: ErrorLogService installed [/WFU_UNC06/services/ErrorLogService] ************************************************************ ERROR: Could not init node [/WFU_UNC06/services/IbsAsdService/AxSerialTunnel] java.lang.NullPointerException at tridiumx.tunnelAx.Tunnel.doInit (bytecode 48) at tridiumx.ibsAsd.AxSerialTunnel.doInit (bytecode 84) at tridium.foundation.node.Node.init (bytecode 1) at tridium.foundation.prism.LoaderModule.initNodes (bytecode 26) at tridium.foundation.prism.Prism.initNodes (bytecode 4) at tridium.foundation.Station.startStation (bytecode 60) at tridium.foundation.Sys.boot (bytecode 27) at tridium.foundation.Sys.bootLocalSns (bytecode 17) at tridium.tools.StationMain.bootSns (bytecode 0) at tridium.tools.StationMain.doIt (bytecode 352) at tridium.tools.StationMain.main (bytecode 10) at java.lang.reflect.Method.invoke (Native Method) at tridium.nre.Nre.mainTmpl (bytecode 271) at tridium.nreNre.main (bytecode 1) Product Line TAC IA Series Environment Niagara R2 (revision 522 or above) Cause The tunnelAx jar is not installed in the host UNC. The release notes for AX Tunneling in R2 do not clearly state to install the jar file in section 2.4 and 2.5 which provide install instructions; however, section 1.2 indicates the requirement of this jar file. Resolution Install the tunnelAx jar file prior to starting the install instructions in 2.4 and 2.5.

Issue Vulnerability affecting certain versions of OpenSSL. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment OpenSSL Cause Software vulnerability Resolution Information and Customer Statement located at the following link on the community: Schneider Electric Security Statement Regarding the Heartbleed Vulnerability. A corporate statement on this can also be found here: Schneider_Electric_Heartbleed_Customer_Statement_APR_15_2014.pdf.

Issue MicroSmart MSC-P1500 Series controller quick reference for interfacing voltage and current sensors. Environment MicroSmart MSC-P1500 Cause The configuration for this controller is non-standard meaning the wiring and software configuration are not 'typical' with the rest of the MicroSmart controller line. Resolution The images available here are excerpts from the MSC-P1500 Installation Instructions (F-25504)

Issue Using the SIM-MTECH manual (F-26133-2) for reference, the Read/Write range of "Space Static Pressure Setpoint' on page A-45 displays as 0 to 5.0 "WC.  But the displayed setpoint does not match the value in the McQuay controller.  And, in general terms, any space static is never as high as 5.0 "WC. Environment SIM-MTECH Cause The manual contains a typo. Resolution The above-mentioned space static pressure setpoint range is actually -0.25 to +0.25 "WC. Keep this in mind as calculations are done to convert the unitless range of 0-250 to a value in "WC.

Issue A new computer has been configured as an InVue Client computer.  In Viewer, when displaying a typical graphic screen, the dynamic values for each OCX is replaced with the words "Access is Denied". What causes this message and how can it be corrected? Environment InVue Wonderware for Intelligent Buildings (WIB) Cause Primarily a Windows permissions issue or incomplete communications setup. Resolution Try each of the following to correct the problem: Make sure DCOM is enabled (Start -> Run -> dcomcnfg) and running on both the client and server computers. Use "telnet" command to see if port 135 is open and available for DCOM. Use dcomcnfg.exe to modify its settings: On Default Properties tab, verify that "Enable Distributed COM" is checked, default authentication level is "Connect" and Default impersonation level is "Identify" On Default Security tab, Default Launch Permissions - click Edit ... button, verify that the Administrators group is shown and has "Allow Launch" permission" On Default Security tab, Default Configuration Permissions - click Edit ... button, verify that the Administrators group is shown and has "Full Control" permission" Windows login account for the client pc must exist on the server as well -- same username and password -- administrative privileges mandatory Ensure wwuser.exe (factorysuite/common folder) reflects the local computer name and administrative user account Re-do the DDE Shares as outlined in Tech Bulletin 02-26 on the client computer. Turn off any firewall and disable/remove anti-virus / anti-spam program or service.