Building Automation Knowledge Base

Issue Automation Server - Warm and Cold Start differences Product Line EcoStruxure Building Operation Environment Building Operation Automation server Cause The explanation on the differences between a warm start and a cold start in the documentation and web help may not be clear to some.  Resolution Warm Start: Restarts the controller's application Cold Start: Restarts the controller's operating system An Automation Server can be warm/cold started from Workstation or by using the reset button on the Automation Server. Refer to Reset Functions on Web Help for an explanation of the differences between warm and cold starting the AS.  Basically, you can set the Retain Levels for variables in Building Operation to 'No', 'warm start' or 'cold start'. To change the retain level of a variable and go to its properties.  - Click on the gear icon. - Set the retain level of the variable. 1. Retain level set to 'No' - The variable is reset to the value set when the object was created. When you create an Analog Value object, the value of the newly created object is '0'. A user can set this to another value. When retain level is set for this Analog Value object, after a warm or cold start, the value of this object will default back to '0'. 2. Retain level set to 'Warm start' - The value is set back to the last value set by the user. If a user change the value of an Analog Value object to another value and save, after a warm start, the object will return to the last value set by the user.  3. Retain level set to 'Cold start' - The value is set back to the last value set by either the user or the system (for instance by a program). The operation is similar to the warm start but in this case, the last value set by the system will also be retained. 

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Product Line EcoStruxure Building Expert,EcoStruxure Building Operation,Field Devices Environment SE7200 / SE7300 / SE76000 Room Controllers Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

Issue Site looking to add some WorkStations with the ability to show Graphics but without the Graphic editor. Not sure which part number to order. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Documentation Resolution V2 or higher, Enterprise Server or Enterprise Central license includes three concurrent client licenses (WebSation or WorkStation). For additional clients, order one or more of the licenses below. These licenses do not include any editors, the WorkStation will show the graphics but will not allow editing, order below part numbers:   If graphic or programming editing is required, you can order professional WorkStation license, which will add extra WorkStation with editors, or order Programming & Graphics Editor licensing, which will add editors to existing WorkStation Standard license.  

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue Unable to monitor a SmartStruxure Lite MPM controller over a Building Management System using BACnet to an AX BMS Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause Misconfiguration of BACnet settings on a MPM controller. Resolution Open Building Expert on the controller with a supported browser. In this example both the MPM controller and the BMS system are in the same IP subnet range. Highlight the Device's name e.g. SmartStruxure Controller and go to the Configuration tab. On Ethernet Settings (ETH1) The IP address of the MPM controller must be in the same subnet IP range of the BMS IP address, but not the same IP address. Netmask must be the same subnet on both controllers (MPM and BMS) e.g. 255.255.255.0, if not then a BBMD/Foreign Device needs to be used. Gateway IP if used. On BACnet Settings (BAC1) Network ID (171) used on the MPM controller must be different than the BMS network numbers used for BACnet MS/TP and BACnet IP Set Protocol to BACnet IP Click on the upper-left icon (Save database to flash) Important! Right-click on "SmartStruxure Controller" then on "Restart Controller," be patient. On the BMS Jace AX, under BACnet network, click on Discover, uncheck all MPM Networks assigned within the MPM (if this facility is available in the BMS), in this example we have only one, it’s #171, refer to point 4. If you don't uncheck MPM network number, the devices will still discover but with duplicates. In this example, network #1 is the BMS IP network and needs to be checked. Network #300 is the BMS MS/TP network number, and has no impact on discovering the MPM as a BACnet device. Click OK. Here’s the result of the discovery, all the objects we had at point 4. are shown. Now add the Devices to the Database, then select one device (in this example the SE8600 is selected), click the Discover button, all objects we had in point 4. are now in AX. Add them to AX database.

Issue Points from a SmartStruxure Lite MPM display the question mark character (?) instead of the correct engineering unit when brought into Building Operation via BACnet. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Building Operation WorkSation SmartStruxure Lite MPM with firmware version 2.5.8 or earlier Cause The question mark (?) placeholder for units is used when Building Operation reads a BACnet unit id that we do not have a translation for to Building Operation units. In MPM firmware version 2.5.8 and earlier, units are translated as vendor proprietary, in firmware version 2.7 and later the units are translated to standard BACnet units. Resolution Upgrade the MPM firmware to Version 2.7x or later. MPM firmware can be downloaded from the https://ecoxpert.se.com/building-expert/discover#tab/documents . Please note that firmware is on a secure area of the site that is only accessible to certified SmartStruxure Lite engineers.   I M P O R T A N T   Also, any thermostat where the communication module is replaced must be re-addressed and re-discovered, additionally all related Widgets will have to be re-linked to the new object(s). If you are not sure which module you have on your SE7000P units do the following... a) Remove the cover. b) look at the part number, the new extended profile modules are 051-0132

Issue Investigating event with EBO Webstation and need to collect logs for Product Support to assist. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Product Support requests logs to investigate an event in EBO Webstation Resolution Opening Developer Tools in Google Chrome or Microsoft Edge Open browser Hit F12 or Ctrl+Shift+I to toggle open and close the Developer Tools section Note: In Microsoft Edge, one can use F12 if you check to Remember my decision and click the Open DevTools button                                                                                                      Collect Information from Developer Tools - Console Open the browser's Developer Tools Select the Console tab. NOTE: Exceptions from the server or client-side issues will be shown in the console. Select inside the console tab, hit Ctrl-A to Select All, hit CTRL-C to Copy, and in any text editor, hit CTRL-V to Paste. Save the file. NOTE: In this example, there are no exceptions to be saved.  Collecting Network Logs The communication between the server and client can be logged. This can provide essential information about the information sent from the client to the server and how the information is parsed by the client. It can be useful to: take a network log while reproducing the issue clear the application cache then take a new network log.   Preparing and saving the network log Click the Network tab. Make sure network traffic is being recorded (toggled with ctrl+E) Clear the network log by clicking the Clear symbol in the upper left Open the page or object representing the issue Carry out steps to reproduce the issue Stop the recording (toggled with ctrl+E) Click Export HAR... to save the HAR file  Clearing the application cache and type information Click the Application tab Click the Application - Storage section Ensure ALL boxes are checked Click Clear site data.  NOTE: This will log you out and you need to log back in 

Issue How do I read unsigned 8-bit (byte) values from a Modbus holding register and represent the analog value in Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In this case, the Modbus holding register is a 16-bit unsigned value that is used by the Modbus device to represent two individual 8-bit values.  The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into two analog values. Resolution Use a Building Operation Modbus Analog Input Point for each value required.  Each object will be configured to read the same Modbus register address with the bitmask value applied before evaluating the value to determine the output. For example: Read Modbus holding register 40001 which is a 16-bit unsigned value and decode as two analog values. Under the Modbus device object - create a Modbus Register Group Under the Modbus Register Group - create two Modbus Analog Input Points Configure each point as follows: Modbus Analog Input Point 40001 (AI-HighByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 8 through 15 Modbus Digital Input Point 40001 (AI-LowByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 0 through 7 Additional information can be found in the Building Operation Technical Reference Guide - Modbus Point Configuration (Bitmask) or WebHelp at Point and Value Configuration

Issue The Enterprise Server service keeps stopping, and Windows restarts it right away. This is preventing WorkStation or WebStation from logging on. When viewing the Building Operation Software Administrator, the "Start Service" option is greyed out, and the server status is Stopped. Product Line EcoStruxre Building Operation Environment Building Operation Software Administrator Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause The Enterprise Server or Central service uses TCP port 80 by default.  If another service on the PC is using port 80 (e.g., Internet Information Services), this will cause the service to stop and re-start constantly. Resolution Two options: Stop the conflicting service from running (e.g., IIS, Dropbox, Skype) Change the HTTP or HTTPS port in Enterprise Server or Enterprise Central to a unique port (e.g., 8080) To change the ports, open Software Administrator and stop the server if it is not already. Then the port fields will no longer be grayed out, and they can be changed. Finally, restart the server. Refer to: Configuring Server Port Settings Note: Once the port has been changed to a unique one, this must be specified when logging into WorkStation, as seen below.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue How to reset an existing EBO Licensing installation Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Most of the time, issues with damaged or corrupted EBO Licenses can be resolved by simply returning and re-registering the affected License, either manually or with the help of Product Support. However, on some occasions, this is not enough, as the actual Licensing installation is affected.  Even re-installing the License Server does not fix the issue because of unwanted data left over in the registry. Resolution A License Server Reset Tool capable of partial or complete reset of an EBO License Server installation has been developed and available for download from the Community: SBO License Server Reset.

Issue An AS-P (SpaceLogic Server) is crashing; just before the crash, the memory usage in the AS-P increases until it reaches a level where the AS-P crash.  Product Line EcoStruxure Building Operation  Environment Building Operation Automation Server Premium (AS-P) Cause The issue was caused by a Notification report which was located in the ES to which the AS-P was connected, Every time this report was run, the AS-P crashed after a while.  This report included a search of all Modbus points in the system and all properties of the Modbus points. When running the report, the ES was setting up a lot of subscriptions to the AS-P in a very short time period. The AS-P could not handle this huge amount of subscriptions and crashed after a while when trying to process all subscriptions from the ES. Resolution In this particular case, the AS-P had around 2000 Modbus points. When the Notification report was running, the search for these 2000 Modbus points and all properties, which were around 20 per Modbus point, caused the ES to set up around 40 000 (2000*20) subscriptions to the AS-P in a very short time period, and it crashed. To solve this issue, the number of Modbus points in the AS-P was reduced to below 1000, and then the AS-P could handle the number of subscriptions (1000*20=20000) with no crash.   When running a Notification report, including a search, be careful not to search for too many objects and properties in the same report, like in the example above when a search was done for all Modbus objects and properties in an Automation Server.   This is only a problem when a search is done via a Notification report if doing a search from Workstation that is made differently and will not set up a subscription in the same way.

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue Blank screens seen when starting WorkStation, Device Administrator, License Administrator and Software Administrator Product Line EcoStruxure Building Operation Environment Windows 10 Cause Graphics Card Driver Issue In this case there was a "Intel(R) HD Graphics 4600" graphics card (this is the Intel Core i7-4790 CPU built-in graphics card) and there was a dedicated "NVIDIA GeForce GT 630" graphics card which was in the end also the culprit because it was the one with the outdated graphics driver, the Intel one didn't required an update. Resolution Update Display Drivers Fix for Windows 10 Professional Version 1803 below Start Computer Management Go to Display adaptors and update driver  Search online for drivers  Verify with second run after driver update if newest driver is installed 

Issue User can’t disable the fan in heating mode Product Line EcoStruxure Building Expert Environment   SER7000 | SER8000 Cause  Misconfiguration of the thermostat Resolution SER7300 In some application, the device may control baseboard heat or different controls and the user may want to stop the fan in heating mode. The user shall set the Pulsed HT parameter to ON and Fan Cont to Off Auto and this will solve the issue. SER8300 The user shall set Fan Cont to Off Auto and this will solve the issue.

Issue The standard opened Unifact Pro stencil provides items for BB83 range of Unifact Pro controllers and does not provide items for older Unifact Pro range. Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma Environment VisiSat NCP Palm Unifact Pro Cause As standard the automatically open stencils do not provide items for the older BB*2 Unifact Pro range. Resolution The current range of Unifact Pros are presented in the standard Unifact Pro stencil. The obsolete Unifact Pro range (BB*2) are not presented in this stencil, a different stencil needs to be added, to provide the older BB*2 Unifact Pros, before there available to use on the drawing. Visio 2003/2007 Go to the Visio menu Click File Click Stencil Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil You will then have the opportunity to choose one of the older range of Unifact Pro controllers. Visio 2010 Under shapes click More Shapes Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil These stencils are installed during the VisiSat installation process. If for whatever reason your computer no longer has this file, to save you reinstalling VisiSat, you can download a copy of the VisiSat 2.1 Build 196 (200, 201) obsolete stencil from here. You can store the stencil anywhere on your system and use it, VisiSat's default storage locations is under “C:\Satchwell\Binary\VisiSat\EN\Visio”

Issue Configuring the Xenta 102-AX to accept a 4-20 mA CO2 sensor input on Universal Input 3.  A negative value is required on the CO2 offset value, but it is not possible to edit the scaling of the input in StruxureWare. Product Line EcoStruxure Building Operation Environment Xenta 102-AX 4-20 mA output CO2 sensor SmartStruxure Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input.  The best option is to always buy a CO2 sensor that is compatible.  However, if 4-20 mA CO2 sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20 mA CO2 sensor with a 0-2000 ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to None Wire the CO2 sensor and a 250Ω resistor across U3 and M.  This converts the 4-20 mA signal to 1-5V. In SBO WorkStation, create a Function Block program to convert the 0 to 100 % signal to ppm.  (You can import the Function Block program here). Edit Bindings on the CO2 Curve program and bind the nvoUnvInput3/Value.lev_percent from the UnivIn3Sense folder of the 102-AX to the CO2_RAW of the CO2 Curve program. Bind the CO2 from the CO2 Curve program to nviCO2/Value.ppm that is in the UnivIn3Sense folder of the 102-AX. At this point, if you have values entered in for the Airflow Reset or CO2 Low Limit and CO2 High Limit then the Airflow reset will be active and operational. Also, if you have multiple CO2 sensors on multiple 102-AXs then you don't have to have a CO2 Curve Function Block program for each one.  You can just edit the existing CO2 Curve program and copy/paste the exiting Function Block program multiple times in the same Function Block program.  You would just need to rename each public point with a unique name.  Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid).

Issue When trying to connect to a Sigma system from SmartStruxure an "Unable to load SigXmlExport.dll" error message is displayed. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment SmartStruxure Enterprise Server version 1.5 Sigma 4.08 Cause The Sigma to StruxureWare Support files have not been installed to the Sigma installation. Resolution Download the Sigma To StruxureWare Building Operation Support Program from the Exchange Download Center. This additional software allows a Sigma Release 4.08 installation to respond to data import requests from SBO 1.5 and takes Release 4.08 to Build 3.46.66 On the existing Sigma 4.08 Sigma server PC, run SigmaSBOSupportSetup.exe and install the software to completion. There is no need to stop Sigma clients or the server.

Issue With the "Apply initial value" property activated in a script program, there may be confusion on how this impacts the operation of the program after a cold start of the controller, which includes system upgrades. Product Line EcoStruxure Building Operation Environment Script Programs Cause In SmartStruxure versions up to and including 1.9.X, when the “Apply initial value” property of a script program is set to Yes, then the following scenario will occur upon a cold start of the server; The inputs, outputs, and public numerics will revert to the initial values set in the script program. Note: It is important to keep this in mind before upgrading a site that has script programs in the database. If the “Apply initial value” setting is Yes, then the Input, Output, and Public Numerics will be re-initialized with their Initial Value attribute. Depending on whether these attributes were configured and/or the application, upgrade or cold start may result in data loss or unexpected behavior. Resolution Versions up to and including 1.9.X If the values of public numerics need to be retained after a cold start in a script program: The "Apply initial value" property must be set to No. Outcome after a Cold Start: Inputs and Outputs will go to null Public Numerics will retain their last known value   If the values of the public numerics need to go to their configured initial value: The "Apply initial value" property must be set to Yes. Outcome after a Cold Start: Inputs and Outputs will go to their configured initial value Public Numerics will go to their configured initial value   Warning: If "Apply initial value" is set to No, it has been observed in upgrades to version 1.9 that some public numerics do not retain their last known value. The fix for this issue has been assigned to EBO 2.0.