Building Automation Knowledge Base

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue BBMD and BBDT Enterprise Server or Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server and Automation Server BBMD (BACnet Broadcast Management Device) IP subnet, IP router  Cause Clarification for both BACnet Broadcast Management Device (BBMD) and BACnet Broadcast Device Table (BBDT) when used within Building Operation servers. Resolution A BBMD is needed when communicating to BACnet devices on another IP segment/subnet (across IP routers). One BBMD is required per subnet; this is because IP routers block broadcast packets and BACnet uses broadcast packets to initiate and maintain communications.  Continuum CyberStation (below) or bCX4 can act as a BBMD.     A BBMD can be created in a Building Operation Enterprise Server or Automation Server.    The BBMD on the other subnet should be as below   Now all the BACnet devices should be visible on both subnets Notes No more than a single BBMD should be created on each subnet for each IP port used. Additional information about BBMDs is available on WebHelp The Teach and Learn commands are useful for larger networks with multiple BBMDs  

Issue SpaceLogic SLA CO2 units prior to date code 2138 cannot be field calibrated and ABC (Auto Baseline Calibration) is not set to ON by default. Product Line Field Devices Environment Veris Models – Cost Down version: CWE2, CWE2C, CWE2D, CWE2H, CWE2K, CWE2M, CWE2N, CWV2 Firmware prior to REV1.05.23 Prior to 2138 DC   Schneider Electric + Veris Models: CW2LA2A, CW2LA2AV, CW2LAXA, CW2LAXAV SLABLC2, SLABLCV2, SLABLCVX, SLABLCX, SLASLC2, SLASLCV2, SLASLCVX, SLASLCX, SLAWLC2, SLAWLCV2, SLAWLCVX, SLAWLCX Firmware prior to REV2.08.41 Prior to 2138 DC Cause The CO2 sensors are calibrated during manufacture, but can develop an offset during shipment or storage. Units cannot be field calibrated other than by the Auto Baseline Calibration (ABC) algorithm.  The offsets can be greater than 200PPM.  The ABC only calibrates at 30PPM a week.  That would require wait times of greater than 6 weeks. Resolution Replace with a unit with a date code of 2138 or higher or make sure ABC is enabled and wait the necessary time for ABC to correct.

Issue What TAC Xenta I/O modules could act as a Stand-Alone LonWorks device? Product Line EcoStruxure Buildings Operation, TAC Vista Environment EcoStruxure Building Operation  LonWorks TP/FT-10 Network TAC Xenta 420A TAC Xenta 421A TAC Xenta 422A TAC Xenta 450A TAC Xenta 451A TAC Xenta 452A Cause It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. Resolution It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. TAC Xenta 400 I/O modules without -A, will not work as Stand Alone LonWorks devices. Once communication has been established with the Xenta I/O module the green status led will flash on for 1 second every 10 seconds indicating it is in Stand-Alone mode.   In Building Operation, the Lonworks devices list will show devices without an "A" after it. This may lead to the wrong conclusion that these devices can be added as stand-alone devices, but that is not the case. These devices are listed so that they can be added manually to a programmable Xenta device as an IO module.

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 Is it possible to rename an ES after an AS has been created? Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation 1.9 and lower Enterprise Server Automation Server Cause Not possible to rename the Enterprise Server or Automation Servers once attached as a multi-server system Resolution It is not possible in the earlier revisions 1.9 and lower to rename an ES or an AS once created under an ES. From EcoStruxure 2.0 and above this is possible;  Refer to WebHelp for additional details: Server Rename

  Issue TAC Xenta I/O modules working as LonWorks device, indicates offline, flashes fast after power restore. Product Line TAC Vista, EcoStruxure Building Operation Environment XENTA421A XENTA451A Cause When the TAC Xenta I/O modules are used as Lonworks devices, this is indicated by the LED that flash once every tenth second. After a power failure, the device will indicate offline by 5 flashes per second.   The device will indicate offline until it gets an update to any nvi or nci variable. Resolution As soon as the device gets an update on any nvi or nci, it will again start to flash once every tenth second. This means, that if you only read variables from the device, that is, only uses its inputs, it may indicate offline until the next time the configuration is changed.   A workaround for this issue could be to just use a dummy output, that is updated regularly.  

Issue SE7000/SE8000 controllers are randomly going offline or are undiscoverable on BACnet network. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 SSL SE8000 Cause Improper terminations of the BACnet MS/TP communication cable.   Resolution The REF (reference) Terminal is a BACnet Reference which is a voltage reference required by BACnet testing lab (BTL) and it is rarely used in the industry. If not used as a reference, The Ref terminal should be left empty. It is not a terminal to land a shield nor a ground.    At each thermostat (Cable Junction) : Connect the (+) and the (-) wires Twist the shields together Tape around the cable to prevent short-circuit. Ground the shield at one end only (usually on the BAS side) and leave the REF terminal empty Ensure that the shield wire is not connected to the REF (Reference) terminal.

Issue SE7000s (all) and old hardware SE8000 (firmware <= 1.7.4) won't support EBO Zigbee. Product Line EcoStruxure Building Operation Environment SSL SE7000 SSL SE8000 Cause EBO Zigbee has Standard and High-Security levels. The SE7000s and old hardware SE8000 (firmware <= 1.7.4) only supports Zigbee Low Security. Resolution Replace the SE7000s and SE8000s old hardware using SE8000 with the current hardware that supports firmware 2.0.0 and newer.

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

Issue When EcoStruxure Building Operation (EBO) is installed after TAC Vista on the same PC, changes to the national character set in the OP Configuration Tool in Menta cause an error preventing the generation of the MTA file. The error appears when the Generate command is selected in Menta. Depending on the combination of versions of EBO and TAC Vista, the error message is: "National character set not selected" "Cannot open file: struxureware path\ national.dec" (where struxureware path is the location of the Schneider Electric StruxureWare\ Building Operation 1.x installation folder) "ERROR! Failed to create OLE dispatcher: GraphOP.Application.320, GraphOP.Application.NSP" Product Line TAC Vista, EcoStruxure Building Operation   Environment Building Operation Workstation Vista Workstation Cause The installation of EBO overwrites settings in Menta regarding character sets. When Menta is opened with normal user rights, changes to character sets in the OP Configuration Tool are not saved due to the OS user security settings. Resolution Right-click on Menta in the program list and select "run as administrator". Then select your required character set in the OP Configuration Tool ("Formats | Character set file"). The changes can now be saved and Menta will generate successfully. This procedure is only required the first time you run Menta after installing EcoStruxure Building Operation. Normal user rights can be used for subsequent editing sessions.

Issue The System Alarms: "Timeout Cloud SMS channel offline" and "Cloud telemetry channel offline" are never reset and therefore always present in the Alarm view. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Building Operation Enterprise Server Cause When cloud connectivity is enabled, the EcoStruxure BMS sends data from the system to the central storage for diagnostics and analysis along with data from other buildings and sites. Under the Cloud Connectivity Tab, The default communication setting is "Auto". If the customer has the "server.cloud.customer" license feature, the BMS Server tries to activate the cloud communication. The alarms are generated if the ES/AS-P, at some point, was able to connect to the cloud, but then taken off the internet while the setting was "Auto/Enabled". Resolution Upgrade the system to EBO version 3.2.1 or to the latest available version. According to Release Notes for EBO version 3.2.1 this issue should have been fixed in that version, see defect 42293 in Release Notes If the issue is still present see the solution below. The only way to reset the alarm is to have a successful connection to the cloud(Internet) again. Make sure the ES/AS-P has internet access Now the Cloud alarms should go away. Verify that they disappear. Go to the Control Panel in Workstation and click Cloud Connectivity Set the Communication setting to Disable and save the changes. Take the BMS Server off the internet again

Issue In the Workstation, old alarms are showing in the alarm pane. Recheck does not remove, and the only option left is to "Hide". The same goes for disabled alarms. Is there a way to erase or scrub these 8-month-old alarms? When checking disabled alarms, there are a lot of alarms that have been disabled, but no one has disabled any alarms. When right-clicking on the alarms to get the context menu, most of the alternatives are greyed out. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.2 or higher Cause First, check the disabled cause to see what disabled the alarms. If it is "user," a person has disabled them. If it is "system," the system has automatically disabled them because the alarm object has lost its monitored value. Resolution Alarms in the alarm view "Recheck" command does not help then try the "Alarms Integrity Check" commend, please see LL Removing invalid alarms  Check the source path on the alarms, do they point to actual alarm objects? If the alarm objects that triggered the alarm in the first place still exist, you should be able to disable them then just enable them again. If you cannot, use the disable button in the alarm viewer then you can use the Disable alarm property in the editor (assuming version 1.2 or higher). If you can’t disable them then try to trigger them back and forth once. If the alarm objects don’t exist anymore, create alarms that would fit the source path, then just trigger those. After that, it should be safe to delete the alarm objects again. Basically, the alarms you create will take ownership of the old alarms in the viewer. Also, add the column Type in the alarm viewer and see what type they are. It would be helpful to know what the Source path and System alarm id (if there is one) are. Remove old Alarms in Alarm Pane Disabled alarms If the monitored values are not used anymore delete the alarm object that monitors the value If this is not enough make sure the path exists in the system, it can be needed to recreate the alarm in the correct path meaning the folder structure needs to be recreated. There is also the choice of right-clicking on the Alarm which gives the following menu: From this menu, one can Disable the alarm or alternatively, Hide the alarm. To view Hidden or Disabled alarms once they are not shown in the Alarms window, select one of the two Icons from the Alarms window icons as shown below:

Issue How to add and bind SNVTs to a local node High bandwidth usage on FT10 LonWorks network causing slow system response Product Line EcoStruxure Building Operation Environment LonWorks FT10 network Cause FT10 bandwidth is too high due to a large TGML graphic or lots of Change of value trends set up in the server polling points on the FT10 network.  Resolution The local node resides within the Automation Server so the trend or graphic that is polling every 0.5 to 1-second will only poll the local node and not out on the FT10 LonWorks network. The SNVTs in the field then updates the Local node at a frequency rate setup in the SNVT.   Here is a link to a Quick help Video showing how to set up and bind to a Local node

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 for assistance. Issue Need to replace and upgrade AS (Classic) to AS-P-NL. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Building Operation Automation Server Premium non-LON (AS-P-NL) Cause From EBO v3.2 the AS-P-NL is available, there is a need to upgrade an AS (Classic) but the AS is only supported up to v3.1. Resolution A lower version of EBO can be installed into the AS-P-NL e.g. from v2.01, but this must only be for the purpose of upgrading the database.   Therefore the upgrade path can be as this example shows, there is a requirement to upgrade an AS from v1.6: Upgrade AS v1.6 to v3.1.x) . Backup the AS. Install v3.1.x) on AS-P-NL ( x needs to be same as in step 1). Note: Installing 3.1.x on an AS-P_NL is only for the purposes of upgrading the database, the following steps 4. and 5. must be completed . Restore backup on AS-P-NL. Upgrade to v3.2 or later.   For details regarding upgrade paths see article - Upgrade path from version 1.0 to current version 

Issue How to Identify a specific PCT (Project Configuration Tool) project. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause How to identify a specific PCT (Project Configuration Tool) project. Resolution In PCT check the project name for the project to be the backup. For this example, the project named “Test 5 Project” is used.   Go to the project storage folder. (The following is the default locations for PCT v1.2.7.223): C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects   Using a text editor (for example Notepad or Notepad++) open each folder then open the file “project.thrift.pctj”, Open each folder in turn until the correct project has been identified to backup. The stored project folder name can be seen:   Further on in the text editor, the PCT project name can be seen, in this example 'Test 5 Project'.   Alternatively click the “edit” menu item and select find (ctrl + F) from the options and search the text for the PCT project name. Making sure PCT is not running when copies of any of the projects are taken

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 Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. NOTE: It is best to only use the Domain (Netbios) name (as shown above) when adding the Windows Domain name to this property.  Using the full DNS Domain name, for example, eur.gad.schneider-electric.com will cause issues when utilizing other features that require active directory authentication.  One example where this has been identified is with Change Control.   Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials. When logged on to the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. Must use HTTPS. Must enter your Windows username and password. Must enter the domain as the Windows domain as defined within Building Operation.  See below: An example log-on format is shown below when using the above configuration when using WebStation:    Alternatively, if the following is configured in Building Operation: WebStation log-on will look as follows:  Download a TVDA for Single Sign-On Instructions

Issue EcoStruxure Building Advisor does not connect by default to the Automation Server and the request to EWS returns a HTTP 401 error Product Line EcoStruxure Building Operation Environment Building Operation SmartX Server EcoStruxure Building Advisor Cause Required configuration in EBO to enable EcoStruxure Building Advisor Resolution An EBO connection to EcoStruxure Building Advisor requires MD5 authentication to be enabled, disabling it in EBO will result in EcoStruxure Building Advisor being unable to connect. The “Allow authentication with MD5 hash” can be enabled under the EBO Security manager. During the TLS handshake process, both the EcoStruXure Building Analytics Data Transfer Service (DTS) and EBO negotiate to use Sha384 encryption regardless of whether MD5 is enabled/disabled in EBO. With MD5 enabled, the use of Sha384 encryption works as expected. With MD5 disabled, the use of Sha384 encryption does not work and the request to EWS returns a HTTP 401 error. MD5 is disabled by default in EBO v2.0 and later.