Building Automation Knowledge Base

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

Issue Boiler plant is not operating. Environment DC1100 DC1400 Compensator Plant Off Day Economy Cause Controller is in a Day Economy mode. Resolution The DC1100 / DC1400 has a mode known as "Day Economy, this will prevent the plant from working. The controller display will show "Day Economy", its operation is as follows. Day Economy Day economy will allow the system to turn the heating off during an occupation period if the space temperature is at or above the Space Setpoint and the outside temperature is within 4 degrees of the Space Setpoint. When the heating is switched off by day economy, pump run-on will commence. If during a day economy period the space temperature drops more than 1 degree below setpoint or the outside temperature is no longer within 4 degrees of the Space Setpoint then the heating will switch back on. The Day Economy function can be disabled though the controller menu system. For further details please select the data sheet HERE.

Issue Documentation on how to add and remove controllers in Version 3. Product Line Access Expert Environment Access Expert Version 3 Win10 and above Server 2012 R2 Premise Install Cause There is no documentation on how to add or remove controllers in Access Expert. Resolution This video shows how to add and remove controllers from one instance to another in Access Expert.

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

Issue A floating-point value is displayed incorrectly in a TGML graphic. The presentation field appears to show random numbers. The example shows how the value 11.60 is represented in a TGML graphic. 11.60 is actually stored as 11.600000381469727. In format presentation mode: In none presentation mode: The last 6 digits of the stored floating-point value are seen! Product Line TAC Vista Environment TAC Vista 5.1.X TGML editor 5.1.X A presentation text bound to a floating-point value. Cause Vista uses the PC's default settings for number of decimals, when presenting values in TGML graphics. Resolution To resolve the issue, either set the format property to "Presentation" for the binding object or change the PC's settings to view fewer decimal places eg. 2.

Issue Actuator M44 is no longer available (withdrawn in 2000) and needs a replacement. Environment M44 M9B EM9 Forta Cause Depending on application, since the M44 was used for both rotating and sliding valves, a few different replacement actuators could be used. Resolution For valves with rotating stem, (TRV, VTRA, VTRE and STMG), actuators M9/EM9 can be used. For valves with linear moving stems the TAC Forta series actuator is used.

Issue LonPort is discovered and shows as online but no Service Pin is received Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation ES 1.1 LConfig Cause Since StruxureWare Building Operation ES is running as a service, the legacy driver also has to be. Resolution Open LConfig Click advanced Change Legacy Driver to run as service

Issue StruxureWare Building Operation AS status data Environment StruxureWare Building Operation AS Automation Server Cause AS Information program such as CpuUsage, MemUsage, ProductID, Partnumber, Serial, SWversion, and much more. Resolution The attached file can be imported into a AS (with any or the releases 1.1.x  through the current release 1.5.x). It will create two graphics that supply a wealth of operational information. Screenshots are shown below:   After import into your AS, look for System View folder. Open to view the two ProgramInfo and SystemInfo tabs. Please note that you can also see the CPU% and memory usage of the AS by using Building Operation Workstation, highlight the AS, go to the Properties tab and in Basic, the stats are listed.

Issue Xenta 102-AX version 2.19 included 6 major updates and changes. They are outlined below. Product Line TAC Vista Environment Vista Xenta 102-AX Cause M/STAT Air Flow Calibration Errors Error Description: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is not generated in circumstances where one would be generated in the 102-AX Plug-in. This adversely affects the accuracy of the calibration, in particular at the low flow setting. Note: All steps for calibration using the M/STAT are found in Calibrating Airflow on a Xenta 102-AX (or MR-VAV-AX) using the M/STAT. Workaround: Perform the calibration using the LNS 102-AX plug-in tool or the TMGL plug-in tool Xenta 102-AX does not perform wink function properly Error Description: Attempts to perform the wink function fail. When a wink function is performed, the red light on the controller is expected to come on and flash to identify the controller and the STR-250 should display "00" with the man logo displayed as well. This should last approximately 45 seconds. STR-250 connected to the Xenta 102-AX is not controlling the fan properly Error Description: The STR-250, stat when connected to the Xenta 102-AX, reacts incorrectly to buttons being pressed when in the fan menu. The increase button causes a decrease and the decrease button causes an increase among other odd behaviors. Also, if the fan is set to shut off (this action should not be allowed) the Xenta 102-AX performs a resynchronization. Pressure dependent mode erroneously requires airflow and fan enabled Error Description: The 102AX requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Error Description:  When the Xenta 102AX does a hot water floating control valve resynch based on being in the 10-90% "happy" zone for 60 seconds and then goes to 100% it does not resynch at the 100% open position for the full stroke time. It gets to 100% commands the resynch, then closes the valve, re-opens the valve to 100% then allows the valve to control back to a normal position. Xenta 102-AX Floating Hot Water valve control failures Error Description:  Heating outputs stop working on Xenta 102-AX sporadically causing hot water valve to open even though application is calling for it to be closed. This occurs when the 102-AX is set up for a floating valve actuator (PWM 2) and occurs sometimes within a day but could take a few of days to show up. The resynchronization of the valve seems to have no effect and the only way to fix the controller is to cycle power or by switching nviEmergCmd to something other than its default and then back again a moment later. Resolution If any of these errors are occurring, upgrade the Xenta 102-AX to version 2.1.9 or higher. Click here to download the APB file. Complete upgrade instructions can be found at Upgrading a Xenta 102-AX to version 2.16 or later Version 2.19 addresses the problems listed above as follows: M/STAT Air Flow Calibration Errors Fix: When calibrating a Xenta 102-AX using the M/STAT a Velocity Pressure Offset is now properly generated. Xenta 102-AX does not perform wink function properly Fix: After clicking Wink the a red LED on the controller flashes to identify the controller and the STR-250 displays "00" and the man icon. After approximately 45 seconds both the controller and the STR-250 return to normal. STR-250 connected to the Xenta 102-AX is not controlling the fan properly| Fix: The ability of the STR-250 to override the fan command on the 102-AX is disabled by default. If this functionality is required it can be turned on by setting DamperActuator.SCPTdirection.bit15 to 1. Pressure dependent mode erroneously requires airflow and fan enabled Fix: The 102AX no longer requires 80% Airflow Setpoint to run Heat1 in Pressure Dependent mode. Xenta 102-AX Hot Water floating control resynch fails Fix:  Logic has been corrected to only resynch open or resynch closed as needed. Additionally, the heating output resynchronization algorithm has changed to operate as follows: Two internal timers have been added to track the accumulated amount of time that heat load is 0% and at 100%. Once either of these timers reaches 30 minutes, a resynch is initiated in the respective direction of the timer. The resynch consists of activating either the open or close triac output for an amount of time equal to the user defined stroke time. Xenta 102-AX Floating Hot Water valve control failures Fix:  Heating output logic corrected to prevent failure.

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

Issue Various errors during installation of I/NET 2.42 and Vista 5.1.7 on a 64-bit Operating system Product Line TAC INET, TAC Vista Environment Windows 7 64-Bit Cause Windows 7 64-Bit Resolution Overview: Install SQL according the instructions found in the SQLExpress folder on the I/NET CD Run the SQL Server 2005 backwards compatibility tool located on the I/NET installation CD Install Vista 5.1.7 Install I/NET 2.42. Step-by-Step Process: Installing SQL Download SQL2008 Express 64 (SQLEXPR_x64_ENU.exe) bit from this location http://www.microsoft.com/en-us/download/details.aspx?id=1695 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install Vista 5.1.7 Download and Run the TAC Vista Server 5.1.7 installation package. Accept all default settings Do not start the Vista Server at this time Install I/NET Seven 2.42 Install I/NET Seven 2.42 using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET Activate any Vista Licensing Start Vista Server Start Vista Workstation

Issue Can SLPSXC2 CO2 sensor calibration be used with both methods (ABC standard and Fresh Air process) at the same time? Product Line Field Devices. Environment Building Operation SmartX Living Space Sensor. Cause SLPSXC2 CO2 can be calibrated using two different methods. Automatic Baseline Calibration(ABC) The ABC algorithm constantly keeps track of the sensor’s lowest reading over a pre-configured time interval and slowly corrects for any long-term drift detected when compared to the expected fresh air value of 400 ppm. ABC calibration is enabled/disabled through coil 4 (invoke = enable ABC). Manual Calibration Coil 11 triggers the manual calibration (FRC 400ppm) => this will tell the sensor that the current level of CO2 should be interpreted as 400ppm. When setting this register to 1, it automatically goes back to 0 a couple of seconds later. Setting Coil 11 to value 1 is the same as pressing the calibration button. Resolution The both methods of calibration can be used simultaneously since one method is for correcting drift over time (1 week intervals), the other is a manually executed reset.   The only error would come if the unit was exposed to high CO2 concentrations at night, inducing abnormal averages. If ABC is disabled, manual calibration would need to be performed more frequently.

Issue As per RFC 4510 The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Do EBO servers support LDAP protocol? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Need to know if EBO supports LDAP protocol. Resolution EBO doesn't support LDAP protocol. EcoStruxure Windows based BMS servers (Enterprise Server/ Enterprise Central) support integerationto Windows Active directory. The Active Directory integration is not using LDAP directly, but the NetLogon service on the Windows OS that ES/EC is running on.  This connection enables inherited user account groups from the Windows Active Directory to EcoStruxure Building Operation software, and allows users to log on to WorkStation with their Windows user accounts. Refer to: Windows Active Directory User Groups and Integrating Windows Active Directory user accounts with EcoStruxure - Communities For EBO 2022 or higher, Authentication using SAML 2.0 is also supported (Edge Server, AS-P, AS-B, ES and EC) . This enables configuring WebStation to use single sign on (SSO) using Federated Authentication, refer to: Federated Authentication. SAML Authentication feature requires license.

Issue After installing or upgrading from EBO 2.0.x to EBO 3.x.x or EBO 4.0.x, the Enterprise Server or Enterprise Central will not start. When the "Start Service" button is pressed in the Building Operation Software Administrator the server status is stopped and does not change and no activity is seen in the system log area. Product Line EcoStruxure Building Operation Environment Enterprise Server Enterprise Central Cause The vcruntime140.dll file is missing from the Window’s system32 folder. Resolution The vcruntime140.dll file is installed as part of the Visual C++ Redistributable for Visual Studio 2015 installation. Visual C++ Redistributable for Visual Studio 2015 can be downloaded from the link below. https://www.microsoft.com/en-in/download/details.aspx?id=48145   If you have later versions Visual C++ Redistributable for example Visual C++ Redistributable for Visual Studio 2017, Visual Studio 2015, 2017, 2019, and 2022 can be used to save uninstalling version 2017. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170  

Issue nvoSpaceTemp from TAC Xenta 100 series used with the room unit STR150 does not read temperatures greater than 33.4 °C (92.3 °F). Product Line TAC Vista Environment ZBuilder Xenta 121 Xenta 122 STR Sensor Cause The STR150 and the Xenta 100 line of controllers are capable of displaying temperatures greater than 33.4 °C (92.3 °F) or less than 8 °C (46.4 °F). However, the communication protocol between the STR150 and the Xenta 100 series is limited and thus restricts the temperature that the TAC Xenta 100 can read from the STR150 device. Resolution The STR150 data sheet states that temperature range transferred to a TAC Xenta 100 device is limited to 8 °C through 33.4 °C (46.4 °F to 92.3 °F). If temperatures outside of that range are needed an STR100 (simple 1.8k thermistor) or an STR-350 (communicating Lon stat with display) could be substituted. The ranges of those devices connected to a TAC Xenta 100 device are as follows: STR100: –10 °C to +50 °C (14 °F to 122 °F) STR350: 5 °C to 45 °C (41 °F to 113 °F)

Issue Replacing battery Product Line Satchwell Micronet Environment Panel Wall mounted Controller mounted Cause Obsolescence Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Battery part number Type LS14500 The battery is available from RS Components

Issue What alternatives are available for accessing Continuum WebClient from browsers other than Internet Explorer? Product Line Andover Continuum Environment Continuum WebClient Server Cause While Internet Explorer is the only officially supported browser for Continuum WebClient, Microsoft has announced that support for Internet Explorer will end in June 2022.   When accessing WebClient sites using Microsoft Edge in Internet Explorer mode. WebClient server returns an error, indicating that Internet Explorer is needed to access WebClient. Resolution It is possible to access WebClient using Microsoft Edge in Internet Explorer Mode. 1. In Edge click on the ellipses (...) top right then select Settings and set like the snapshot below. a. Allow sites to be reloaded in Internet Explorer Mode(Allow) b. Add the webclient machine's login page (http://webclientservername/webclient/logon.aspx) 2. Setting Internet Explorer compatibility mode and Internet Explorer mode for future use. Navigate to the webclient URL with Edge and select Reload in Internet Explorer mode By default, these settings will be Disabled, Set both of the buttons to Enable as shown below. Note: you may have to go through the process twice to enable both buttons   A snapshot of a successful login to webclient with Edge and also the selection in yellow to Exit Internet Explorer Mode if necessary to run other web applications.   The method of specifying Internet Explorer Mode for a site’s webClient URL will depend on how the customer treats the configuration of Edge – either settings at the individual Edge level or via group policy settings.

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

Issue Replacement an AF24-S Actuator? Environment AF24-S Damper Cause Customer requires a replacement actuator for a AF24-S. Resolution The AF24-S is a 24v power open, spring return damper actuator, it has a torque of 15 Newtons. To view the data sheet, please click HERE. The replacement actuator range is the MD10SR/MD20SR ranges. The MD10SR damper actuators have a torque of 10 Newtons (dampers up to 2m2) and are available in the models shown below. To view the full data sheet, please click HERE.   The MD20SR damper actuators have a torque of 20 Newtons (dampers up to 4m2) and are available in the models shown below. To view the full data sheet, please click HERE. In the specific case of the AF24-S the replacement would be the MD20SR-T or -TS if auxiliary switches are required.

Issue MESSAGE [08:29:10 31-May-13 CDT][sys] *** Station Started (203ms) [1919ms total] *** niagara>MESSAGE [08:29:12 31-May-13 CDT][history.db] Starting async warmup of history config index... MESSAGE [08:29:12 31-May-13 CDT][history.db] Async history config index warmup completed in 15 ms. ERROR [08:29:16 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind ERROR [08:29:21 31-May-13 CDT][web.server] HTTP Server failed to bind to port. Address already in use: JVM_Bind Product Line TAC IA Series Environment I/A Series G3 Enterprise Server, all versions Cause Another service on the pc is using port 80, conflicting with the Enterprise Server. For example, Skype will use port 80 as an alternative unless you uncheck the box in Skype options. As a second example, another Niagara station may be running on the same computer. See Changing the HTTP, HTTPS, or TCP ports of the Enterprise Server for a similar port conflict issue with SmartStruxure. Resolution In the Skype menu > Tools > Options > Advanced > Connection, uncheck the box for "Use port 80 and 443 as alternatives for incoming connections"