Building Automation Knowledge Base

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue If a Xenta 913 with SNVT(s) is added as a Lon device to an Automation Server Lonworks network the commission process fails in the last step with error 0 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server TAC Xenta 913 TAC Xenta 700 Cause This is a bug in the Xenta Server firmware. Resolution This issue will be fixed in Xenta 913 firmware version 5.1.9, however  hotfixes have been made for 5.1.8 and can be requested from PSS (TACXenta913-5.1.8.15 and TACXenta700-5.1.8.47). Note: All data will be lost in the Xenta Server when applying the hotfix.

Issue "Enable incoming http communication" option is grayed out and cannot be unselected. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When Building Operation Workstation is connected to the SmartX Server using a HTTP connection, the option to disable incoming HTTP connection is unavailable.     Resolution Use HTTPS in Building Operation Workstation to connect to the SmartX Server to allow this option to be unselected. Refer to the Online Help Topic: Disabling Incoming HTTP Communication

Issue Changing the Automation Server HTTP / HTTPS ports, 1.3 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause There is a need to change the Automation Server's HTTP and/or HTTPS ports from the default ports of 80 (HTTP) and 443 (HTTPS). Resolution The HTTP / HTTPS ports of the Automation Server can be changed from Struxureware/EcoStruxure Building Operation WebStation, requires SBO/EBO V1.3 or higher.  From a web browser*, connect and log on to the Automation Server. After you have logged on, click on the 'Account menu' near the top right corner: EBO 4.0.3 or higher,  From the "Options" select 'Setting'. From the network tab, you can change the HTTP / HTTPS ports.    EBO V4.0.2 or lower, From the "Options" select 'Device Configuration'.   The TCP/IP configuration page should appear. From here, you can change the HTTP / HTTPS ports.       3. Perform a Warm Start on the Automation Server to apply the HTTP / HTTPS port changes to the server.     * Check supported web browsers for Struxureware/EcoStruxure Building Operation at the WebStation specification sheet, make sure to select the correct SBO/EBO version: WebStation (se.com)     Firefox 4 or later (32-bit)

Issue An alarm goes on and off several times in a short amount of time. Each time the alarm condition clears and reasserts itself, by default, another email will be sent. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SMTP alarms Cause Every time an alarm goes off, the email notification checks its parameter and, if true, sends an email. Resolution Filter the email notification by "count." Set it to "from 0 to 1" and you will only get a email on the first alarm (count).

Issue Various items are not being displayed in the system tree or the binding tree of EcoStruxure Building Operation Workstation. When navigating through the tree, items such as folders or parameters may be missing. Product Line EcoStruxure Building Operation Environment Workstation System tree Cause If items are missing in the system tree or the binding browse tree then the filter settings are not set up correctly. Resolution If the expand icon next to a folder is missing or items are missing from the system tree, follow the steps below.     If the expand icon next to a folder is missing or items are missing from the system tree, make sure that the funnel icon is not clicked or activated (Show/Hide non-presentation objects)     If points are missing in the bindings browse window, make sure the funnel in the top left corner of that window is not clicked or activated (Hide parameters)

Issue Unable to back up the Automation Server Unable to retrieve a working backup from an Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Enterprise Central Cause Corrupt configuration.db Network environment issues Power failure Resolution Database Corruption When the server backup process is initiated, the server tests the integrity of the configuration.db.  If the database does not pass the integrity test, the backup process is terminated, and no resulting backup is produced. In this case, an older backup will need to be used.  The backup should be bench tested for integrity before restoring to the production server.   Network Environment In some cases, the AS may produce a valid backup file, but when the backup is saved off of the server the file size is unusually small.  This can happen when network issues interfere with the backup save to disk process.   In such cases, Automation Server backups taken from the Enterprise server will usually be damaged as well.    You can work around this problem by connecting a Workstation laptop PC directly to the AS with an ethernet cable, thus eliminating the network from the process. Backups can also be retrieved in this way using most versions of Device Administrator.    Power Failure The power fails while the EcoStruxure BMS server is backing up and the system displays a “Failed backup” message in the Event view. The solution is to initiate a new backup when the power resumes and the EcoStruxure BMS server goes back online. Power Failure Occurs During Backup     

Issue A license violation alarm is shown in the alarm viewer even though the system has all licenses necessary. The alarm returns to normal without any action from the operator. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Enterprise Server / Central contacts the License Server installed on the computer to determine what licenses are available. The License Server will then contact the "Trusted Storage" on the computer which is created when activating the licenses and ask how many licenses are available. The issue comes when the "Trusted Storage" creates some metadata once a day.  The metadata is a file created showing which licenses are used at that moment.  This is not currently used but could be by a third-party client who is interested in the license information for the system.  When the "Trusted Storage" creates the metadata it will be busy and not answer the License Server.  This is when the license violation alarm will be activated.  The alarm will return to normal after the "Trusted Storage" has finished creating the metadata. Resolution An investigation is ongoing. This issue has been fixed in EBO 2022. Please refer to License Violation Alarm 

Issue PE Script program created in b3 or i2 has no error but its not executing. Product Line EcoStruxure Building Operation Environment Infinet i1, I2 BACnet b3 Automation Server, AS, ASP, ASB Cause Program compilation was not valid. Resolution Examine the code and determine what is causing the compilation issue. Known causes... 1. Variable declared in the code but not used (unbound)

Issue Unable to compile a b3 Script program if there is a bind to the priority array of a commandable property. How to command an object at a particular priority in b3 Script program. Product Line EcoStruxure Building Operation Environment b3 WorkStation Automation Server Cause Because of historical reasons (that are outside the scope of this article) in the evolution of the b3 firmware, binding to the priority array of an object within a Script program in the b3 is NOT supported. Resolution To command an object from a Script program in the b3 at a specific priority the WriteProperty command MUST be used. NOTE If the b3 firmware is 4.500064 then priority 10 will always be set rather than the one specified in the WriteProperty command. This was fixed in v4.500076, it is best to use the the latest firmware

Issue Unable to access ES or AS after setting a new Domain as the default domain Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause If you set a domain as a default domain before logging in through that domain, it is possible that you do not have users set up and therefore will be locked out of the system. Resolution Open Building Operation Workstation Enter a Username and password for the Local domain or another previously functional domain Set the Domain as "Local", please note that this is case sensitive. Select the correct Server Log in Change the default domain back to Local until you have successfully logged in using the new domain.

Issue Certain Xenta controllers and I/O modules can accept 10k thermistor temperature inputs. Product Line EcoStruxure Building Operation,TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always used 10k thermistors. Now some of the I/O modules and programmable controllers also have an option for 10k thermistor inputs. A common question is -- what type of 10k thermistors? Type 2? Type 3? Resolution The reason there is no reference to 10k Type 2 or 10k Type 3 is because these are Continuum-specific terms. The 10k thermistor that is compatible with Xenta 42XA and 45XA I/O modules are the same that I/NET uses. They are Vishay Dale Curve #1. View this PDF for the Resistance vs. Temperature Conversion Tables for this thermistor.

Issue Backup set file cannot be imported.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Automation Server Enterprise Server Backup set file Cause Backup set file is very large so import of backup set file fails.   Resolution A current workaround is to manually copy the backup file set to the default backup location. Browse to C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\db_backup or C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server\db_backup By default the ProgramData folder is hidden. To view the ProgramData folder follow the below steps: Select Organize>>Folder and Search options. In Folder options under view tab select "Show hidden files,folders and drives". Manually copy the Enterprise Server Backup set file and paste to the below location: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\db_backup\LocalBackup   Manually copy the Automation Server Backup set file and paste to the below location: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\db_backup\ASArchives

Issue When launching a program or when working with a program, you get an error from "Microsoft .NET Framework".   Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC INET, TAC Vista Environment Windows .NET Framework Cause Microsoft .NET Framework is used in almost all larger applications, and there can be various reasons why you see an error. One reason can be application specific, meaning that there is an actual issue with the software and the way the software is using .NET Framework, but another reason can be that the .NET Framework installation itself is corrupted. If it's an application specific issue, you need to contact product support, but in many cases simply repairing the .NET Framework installation has proven to solve the issue. Resolution 1: Close all applications 2: Make sure you have the correct version of .NET Framework installed for the software you use referencing the product's data sheet. You can use this tool to check what versions you have. Here is a direct download link. 3: Install versions that might be missing. You can download the various versions from the tool linked above. 4: Download Microsoft's .NET Framework repair tool and run it applying all fixes the tool suggests. Here is a direct download link.

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.