Building Automation Knowledge Base

Issue Supplemental Documentation on the Menta OPT block for optimized start and stop. Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The document below is intended to clarify the inputs and configuration parameters of the Menta OPT block and when/how to use them. Resolution Click here to download the example Menta macro A Brief Overview of Optimized Control Optimal Start Optimal Start measures how long it takes a room temperature to reach setpoint each morning when the air-handling unit is enabled. These measurements are then used to predict how long it will take the next time. As time goes on, the predictive algorithm is refined until it becomes quite accurate. An optimally started unit saves energy by only starting as early as is needed, not just an arbitrary hour or two before occupancy. Optimal Stop Optimal Stop is less common. An optimally stopped unit stops running prior to the end of the day. It measures how long it takes before the measured room temperature drifts outside of an acceptable range around the setpoint. This saves energy on cooling a building until 5:00pm (for example) when the occupants are just about to walk out the door. The example in this document will not implement Optimal Stop. Inputs to the OPT Block RoT Room Temperature. If there is just one room temperature sensor being served by the optimally started unit, then this is where it would be used. However, if the unit has several room temperatures or serves many VAV terminal units, consider the following options: Average all temperatures Pick one interior zone Highest room temperature for cooling/lowest room temperature for heating Use return air temperature In all of these scenarios, some consideration should be made for if the input sensors fail: Averaging all temperatures is the most robust method. However, if SNVT inputs are used, it may be necessary to discard invalid values (621.8°F) from the averaging calculation. If one interior zone is used and the temperature sensor fails, the unit will eventually revert to starting as early as is allowed every day. The default value for this is 12 hours early; the example in this document uses 2 hours. If the primary sensor fails, use a secondary, or disable optimal start on a failed condition. Instead of the highest and lowest room temperatures, it may be wise to use the second highest and the second lowest room temperature. This allows for one failed sensor in each direction before the Optimal Start calculation is affected. Using return air theoretically is a lot like using the average of all room temperatures. Adjusting the setpoint to get the desired result might be required. A failed sensor input should disable the Optimal Start calculation. SP Setpoint. Using two OPT blocks – one for Optimal Start cooling, one for Optimal Start heating – allows each to be fine tuned. If there is a morning warm-up sequence, then the heating Optimal Start may be much quicker than the cooling. Using one block requires the internal calculation to adjust as the needs change from cooling to heating, and can be less agile when switching from cooling to heating requirements. OuT Outdoor Temperature. Resets to the curve occur based on the outside air temperature. If it is very cold or very hot outside, the unit will start sooner. This curve is reset automatically as time goes on to better predict the effect outside air temperature has on the controlled space (if AutoAdjust > 0). OpI Operation Indication. In the example of an air-handling unit, OpI would be the fan status. If the configuration parameter OperIndicF is set to 1, then this will be used for internal calculations. Otherwise, it will just use the command as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. TmL Time left. A time schedule (TSCH) input goes here. This tells the calculation how much time is left before the unit is scheduled to turn on (or off). The OPT block then starts the unit early based on this number. It also ensures that the unit always runs during the scheduled occupied time. Mode Mode is for heating/cooling or enabled/disabled. It is advantageous to always program in a method for disabling Optimal Start through a public variable (PVB). Many times the seeming complexity of Optimal Start is found to be undesirable by building operators and they will ask to have it disabled. Mode could be programmatically set for heating/cooling based on outside air temperature (or some other factor), but in the example in this document, two separate OPT blocks are used and are hard-coded for their respective modes. Configuration Parameters of the OPT Block AutoAdjust AutoAdjust refers to whether or not the OPT block gets smarter by adjusting the curves set initially on the first download. If AutoAdjust is set to 0, then the OPT block will still adjust the start time every day based on the room temperature and outside air temperature, but it will not adjust those early start times based on past experience. Set the AutoAdjust to 1, and the curves will adjust a little every day. Set AutoAdjust to 2 and the OPT block will also adjust the holiday compensation (the unit will start a little earlier after a 3-day weekend, but may need to learn exactly how much as time goes by). To maximize the potential of the OPT block, it is suggested to set this value to 2. RoomTempF Room Temperature Flag. Is a room temperature sensor present? Without a room temperature sensor, it is not possible for the OPT block to adjust its curves. It is guessing at that point based on pre-determined curves. It is not recommended to use OPT without a room temperature sensor. OperIndicF Operation Indication Flag. If OperIndicF is set to 1, then the OpI input will be used for internal calculations. Otherwise, the OpI input is ignored and the command is used as status. This prevents a mechanically failed unit from affecting the calculation. A good rule to follow is if fan status is available, use it. StartTimeLo Start Time at Low Outside Air Temperatures. When it is cold outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust as needed each day, but a good default value is important. StartTimeHi Start Time at High Outside Air Temperatures. When it is hot outside, how much earlier should the unit start? This will change between a cooling and a heating optimal start block. If AutoAdjust is set to 1 or 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. HolidayComp Holiday Compensation. This is the default compensation for a holiday (longer than 48 hours of continuous unoccupied time). The value is a percentage. If there is a 3-day weekend, how much earlier should the unit start on the following Tuesday? If AutoAdjust is set to 2 then this is just a default value. It will adjust it as needed each day, but a good default value is important. MaxStartTi Maximum Start Time. This is the maximum amount of hours the unit is permitted to start prior to the occupied time. The default value is 12 hours. The first time the unit is downloaded, it will start this early and measure how long it takes to achieve setpoint. 12 hours is very early. The example in this document uses 2 hours. Even if something goes wrong with the internal calculation (failed sensor input, for example) the earliest it could start would be 2 hours early. ETol Error Tolerance. How close to the desired setpoint does the temperature sensor need to be to be considered at setpoint? An error tolerance of 0.5°F is default and is usually acceptable. StopLoTemp, StopTimeLo, StopHiTemp, StopTimeHi, StopTimeErr All of these parameters refer to the Optimal Stop portion of the OPT block. Setting them to 0 disables the Optimal Stop functionality. Output of a OPT Block There are three possible output values of an OPT block: 0 = The unit is off, unoccupied 1 = The unit is on, occupied 2 = The unit is on, optimally started Putting It Into Practice The example below is a Menta Hierarchy Function Block (HFB) and shows HFB inputs to the blocks. The top OPT block is set to heat mode and looks to a heating setpoint. The bottom OPT block is set to cool mode and looks to a cooling setpoint.   OPT_START_HEAT OPT_START_COOL AutoAdjust 2 2 RoomTempF 1 1 OperIndicF 1 1 StartTimeLo 60 0 StartTimeHi 0 60 HolidayComp 0 0 MaxStartTi 2 2 Etol 0.5 0.5 StopLoTemp 0 0 StopTimeLo 0 0 StopHiTemp 0 0 StopTimeHi 0 0 StopTimeErr 0 0 Using the hints and tips suggested will allow not only for proper programming techniques, but also for creation of macro libraries that can be reused and shared to improve effectiveness across business units.

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 On a new installation of SmartConnector, the service is not able to start. The log shows a SQL server authenticate error. Product Line EcoStruxure Building Operation Environment SmartConnector Cause For some countries, the administrator account has been localized. (List available here: If the operating system is using one of these localized languages, the Windows administrator account may not be recognized by the SmartConnector service, https://social.technet.microsoft.com/wiki/contents/articles/13813.localized-names-for-administrator-account-in-windows.aspx ) Resolution Workaround 1:  Reinstall a non-localized version of Windows.   Workaround 2: Create a new user in the SQL database.   Workaround 3: Open Microsoft SQL Server Management Studio and connect to the SQL instance the SmartConnector will use. Using the Object Explorer menu, navigate to the logins folder: 'Machine-name > Security > Logins' Right-click on the Logins folder, and select 'New login' A window will appear, to configure the new user account. Provide a Login name: this is the log-in the SmartConnector will use. Then select 'SQL Server Authentication', fill in the password field, and type it a second time in the 'Confirm password' field. Select 'Server Roles' from the menu on the left side of the account windows. Check both 'public' and 'sysadmin' if not already checked. Move to the next page: 'User Mapping' Select 'SmartConnector.Service' row, update 'User' and 'Default Schema' with 'dbo' value. Check the 'Map' box, then in the bottom list check the 'db_owner' box. Repeat steps 10 & 11 for 'SmartConnector.User' entry. Click 'OK'  Now that the user is created Uninstall the SmartConnector and restart the machine Reinstall the SmartConnector, and select 'SQL authentication' when requested Provide the newly created login with the associated password. Complete the SmartConnector installation. Validate the service is running without error.  

Issue Viewing Script time from the editor can show incorrect time Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB, AS Classic Building Operation Enterprise Server Building Operation WorkStation Script Program Editor Cause Scripts use Local Server time, but the Clients like Script Editor or WorkStation expecting a server to be UTC. The result is that during Daylight Saving Time, the time seen in the script editor may appear an hour out. Resolution During debugging of Times or Dates or DateTime Values, it is helpful to "Print" the Datetime to a string as this will show actual time being used rather than the Clients interpretation of the time (See script below).The client will take the Server time as UTC and apply offsets to achieve its "Local" time, which can give an incorrect time. The UTCOffset property can be used to correct for time zones but there is no DST(Daylight Saving Time) offset available until v4.0.

Issue What is the b2 and i2 Controller Object Format property used for? Product Line EcoStruxure Building Operation Environment Continuum Conversion i2 Controller objects b3 controller objects Cause i2 and b3 Controller objects include a a Format field for objects created using the Continuum Conversion tool. What is this used for and how does the value effect the operation?     Resolution These Format values are propagated through the Continuum Conversion Tool for reference only and have no impact on operation in EBO. The values cannot be modified. In EBO there are two ways to configure numeric display formats. -In WorkStation property pane and watch window, the number of decimals displayed to the right of the decimal point is inherited from the WorkStation PC's regional settings. This setting applies to all values displayed in WorkStation except for values in graphics. -In graphics, the number decimals displayed to the right of the decimal point is configured value-by-value in the Graphics Editor.   The format value is not stored in an EBO export and if objects are manually created, then standard formats are used for the type of object created .

Issue Deleting logs from External Log Storage takes a very long time. Workstation becomes unresponsive when deleting trends from External Log Storage. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause The deletion process can take a long time on large PostgrSQL databases, sometimes as much as an hour.   Workstation must complete the deletion process before it becomes available for other tasks.   When logged into Enterprise Server to delete a trend that was hosted by a child server (Automation Server), Workstation tags the log for deletion.  The AS that held the original log, will survey the trend_meta table every hour to check for pending flags, and will then delete logs that are flagged.  This can cause the deletion to be delayed by as much as an hour.   Resolution The following method should be used when deleting trends from External Log Storage: The trend must no longer exist in EBO. Log on locally to the server that hosted the associated trend.  Then deleted the trend from the System\External Log Storage folder. Indexing the trend_data table can improve the speed of deletion dramatically in large PostgreSQL databases (1 TB or larger).

Issue The SmartX Controller Advanced Display requires internet access in order to activate the Kiosk Mode on initial startup. Product Line EcoStruxure Building Operation Environment SmartX Controller Advanced Display v2 and v3 SmartXKiosk Cause The SmartX Controller Advanced Display requires internet access in order to be activated on initial startup, site IT departments may need to allow access for activation to proceed. Resolution Internet access is required only once during initial installation to activate the Samsung license If you are in the Americas, enable access to these servers:  Server Port gslb.secb2b.com 443 us-prod-klm.secb2b.com 443 us-elm.secb2b.com 443 If you are in China, enable access to these servers:  Server Port china-gslb.secb2b.com.cn 443 china-klm.secb2b.com.cn 443 china-elm.secb2b.com.cn 443 If you are in Asia, Africa, Europe, or other regions, enable access to these servers:  Server Port gslb.secb2b.com 443 eu-prod-klm.secb2b.com 443 eu-elm.secb2b.com 443   For additional communication paths, refer to the online help topic Information Technology System Planning Guide

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

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 ES takes up to 30 minutes to perform a shutdown. Trace log contains multiple entries indicating "Subscription service forcefully shutting down; [sub-server name]"  "Subscription service forcefully shut down; [sub-server name]"   A secondary issue - When performing Windows Updates automatically, Windows attempts to shut down all running services within one minute which can end the Enterprise Server service prematurely Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server 3.1.x and below Large Multi-server installation  Cause During a shutdown procedure of the Enterprise Server a call to every sub server is made to remove subscriptions. However, the thread pool that executes these commands may already be stopped and the server then waits the 15 seconds timeout period prior to moving to the next item.  On a large 100+ multi-server installation, this 15 second delay can accumulate to a lengthy shutdown period.     The trace log will contain the messages shown  in the issue and the 15-second delay between each server  Enterprise Server Trace log messages seen during shutdown showing the 15-second timeout delay. Resolution Upgrading to 3.2.2 (and above) will rectify the timeout issue provided that the subscription thread pool has already stopped.  These versions now ignore the 15-second timeout for each sub-server if the thread pool has already stopped.   It is possible to extend the Windows service shutdown time by adding or adjusting a registry entry called WaitToKillServiceTimeout .   To change the timeout: Start the registry editor (“Regedit”) In the tree on the left, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control In the right panel, find the WaitToKillServiceTimeout value. If you don’t see it, create it by: Selecting Control on the left Choosing Edit > New > String Value (not DWORD) from the menu Naming the new value WaitToKillServiceTimeout. Double-click the WaitToKillServiceTimeout entry to bring up the Edit String window. Enter a numeric value (e.g. 60000) in the Value data field in milliseconds and click OK to save your change. Reboot your computer. The new timeout setting will not take effect until Windows restarts. Note that this modification will not make Windows wait indefinitely for your service to finish. If your service takes longer than the entered time (in this example 60 seconds), it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown time intolerable.

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue TLS Error seen when attempting to export WebReports data from the displayed report as follows: Unable to download ReportsView.aspx (IP address) Unable to open Internet site, the requested site is not accessible or can not be found  Product Line EcoStruxure Building Operation Environment Building Operation WebReports 3.0.x and above  Internet Explorer (used within WorkStation) and Google Chrome Web Browsers Cause To download files, Internet Explorer must create a cache or temporary file. In Internet Explorer 9 or a later version, if the file is delivered over HTTPS, and any response headers are set to prevent caching, and if the Do not save encrypted pages to disk option is set, a cache file is not created. Therefore, the download fails Resolution See Microsoft documentation on how to correct this.  Typically Method 1 will correct the issue. Cannot download files from secure websites - Browsers | Microsoft Docs

Issue PCT workstation displays message “Server version not compatible with client", when restoring a server configuration with new IDs. Product Line EcoStruxure Building Operation Environment Buildings Operation Project Configuration Tool Cause When backing up and restoring an AS-P/AS-B with a new ID in PCT at EBO 3.2.2.61, when logging back on with PCT using the installed EBO workstation,  the message “Server version not compatible with client" is displayed Resolution PCT is the offline programming tool but, it launches the workstation installed on the computer. If the workstation version on the computer is EBO 3.2.2.61, Hotfix 3.2.2.4002 (CP3) is required to be installed on the computer running PCT, taking the computer’s installed workstation version to 3.2.2.4002.

Issue Clarity is needed on the new ES License Inheritance feature available in EBO 3.x Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Enterprise Central Building Operation SmartX Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in SmartX Servers, such as SNMP Licenses, since EBO 2.x.  The concept of Inheriting Licenses from an ES into a SmartX Server is a new option which can be used from EBO 3.1 onward, although the original Embedded License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   In EBO 3.2 SNMP and TimescaleDB. Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   'Inheritance' means that an ES License will be shared down to its child SmartX Servers while also being retained for use by the ES.   Note: SmartX Servers must be running the minimum supported 3.x version for Inheritance to function There is no such thing as a 'Site License' that can accommodate multiple ES There is no Licenses Inheritance from an EC

Issue The Optimum Stop feature of the OPT function block in Menta / Building Operation Function Block Editor does not auto-adjust, even when the auto-adjust parameter is enabled. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 281 Xenta 301 Xenta 401 Menta FBD Cause This behavior is by design, although it is not made clear in the Menta documentation.  The auto-adjust feature only works with Optimum Start, not Optimum Stop.  The optimum stop time is calculated from a fixed Outside Air Temperature vs time curve.  As some compensation, both end points of the curve are manually adjustable for both time and temperature.  For the optimum start, only the time parameters of the curve end points are manually adjustable. Resolution The optimum stop curve must be manually adjusted over succeeding days until an acceptable stop time is achieved.

Issue Samsung’s Knox security protection on your phone or tablet data is out of date. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Advanced Display v2 Cause   One of the security features contained within the Android operating system is Samsung Knox which the Advanced Display uses. Samsung Knox needs to get security updates periodically and needs to be online to the Internet to receive these updates. As a security feature if Samsung Knox is out of date it can stop the operation of some of the apps. For further information, see the Samsung’s Knox website. If Samsung Knox security needs an update when the AD-Link is launched then one or both the following messages may appear on your display.   Resolution Firstly, if the Advanced Display v2 is not running SmartXKiosk v8.2 and SmartX AD-Link v8.0.apk, then the latest versions are not installed and a request can be made by raising a case with your local product support team for the latest releases. To resolve the Samsung Knox issue, carry out the following procedure: Connect the Advanced Display to a WiFi network that has Internet access. Re-start the device. Confirm the phone or tablet still has an internet connection. Launch AD-Link. (several license windows will appear on your display). The SmartX AD-Link app should now run.

Issue EBO 3.2.x SNMP Engine ID seen in EBO 3.2.x is not the one used by the EBO 3.2.x system. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v3.2) Building Operation Automation Server (AS-P and AS-B) (from v3.2) SNMP Cause EBO 3.2.1 introduced a new SE3Linux operating system for the AS-P and AS-B servers. The engine ID: seen in Device Administrator or Workstation is the engine ID: contained in Linux, this is not the one used by EBO 3.2.x Resolution The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Device administrator: The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Workstation The engine ID used by EBO for this example would be: 0x80002a1d03005006042bd7 The difference is always 2a1d compared to 1f88 and the rest of the bytes are the same. For further information see the attached document SNMP SBO 3.2.x Engine ID Explained.

Issue The 0–10 measured output voltage from the RP-C’s Ub terminals may not provide the expected voltage. Product Line EcoStruxure Building Operation Environment SmartX Controller RP-C Cause On the RP-C controller's the Ub return terminals although internally connected to each other are isolated from ground (-). Resolution Add a ground reference connection between ground and one of the return terminals of the controller. Example if the controller is stand-a-lone using terminal 3, which is an isolated terminal and can be used for the connection.