Building Automation Knowledge Base

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers (AS)-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS    The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP34010 ES Upgrade from 3.X to EBO 2022 with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 These licenses need to be activated using Device Administrator.   For each AS-P one of the following bundles would be required for each AS-P.   SXWSWASPUP34SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 AS-P Bundle – Standalone SXWSWASPUP34SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 AS-P Bundle – Standard SXWSWASPUP34EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 AS-P Bundle - Enhanced SXWSWASPUP34FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics. Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP34SD Upgrades an AS-P from EBO 3.x to EBO 2022 AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   For the AS-Bs one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP34SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard SXWSWASBUP34FU Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP34SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full Would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP34SD ASB Upgrade – Standard license is all that is required. For the additional AS-P classic and the AS-P secure boot one of the following licenses would be required for each.   SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required for each.   SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x, one of the following licenses would be required to upgrade to EBO 3.x first.   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x   SXWSWECUP34005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP34010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2022”   For information on software and features that require licenses  

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited), 4.0 Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016  1.9.1.95 Apr 2017   1.9.2.45 Maintenance Release Oct 2017  - See release note 1.9.3.24 Maintenance Release April 2018  - See release note 1.9.4.29 Maintenance Release April 2019  - See release note 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) - See release note 2.0.2.67 Maintenance Release Sep 2018  - See release note 2.0.3.45 Maintenance Release Dec 2018  - See release note 2.0.4.83 Maintenance Release June 2019  - See release note 3.0.1.104 May 2019  - See release note 3.0.2.33 Maintenance Release July 2019  - See release note 3.0.3.11 Maintenance Release Aug 2019  - See release note 3.0.4.43 Maintenance Release Dec 2019  - See release note 3.1.1.312 Dec 2019  - See release note 3.1.2.29 Maintenance Release Mar 2020  - See release note 3.2.1.630 Aug 2020  - See release note 3.2.2.61 Maintenance Release Nov 2020  - See release note 3.2.3.59 Maintenance Release Mar 2021  - See release note 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note EBO 2022 (4.0.1.86) Dec 2021 - This version follows v3.x, and reflects a new naming convention focused on release year for clarity - See release note EBO 2022 (4.0.2.559 & 562) Maintenance Release Apr 2022 - WorkStation Hotfix and License Admin 4.0.2.562, others 4.0.2.559, see revised release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead EBO 2022 (4.0.1.86 and later) The following protocols, objects, and devices are not supported in EcoStruxure Building Operation 4.0 or higher: I/NET, Sigma, MicroNet, NETWORK 8000 ASD and LCM. A multi-version system supports I/NET, MicroNet, NETWORK 8000 ASD and LCM on automation servers and Sigma on an enterprise server, running an earlier version than 4.0. Report Server/WebReports is not supported in EcoStruxure Building Operation 4.0 or higher. See release notes for details. Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them

Issue The file linked below details a model of the MicroNet sensors with carbon dioxide sensing.  Are these available for purchase? MN-Sxxx CO2 sensors Product Line TAC IA Series Environment I/A Series MN-Sx sensors Cause Sales literature with reference to Schneider-Electric Resolution The MicroNet sensor models with carbon dioxide are a product of another company - Barcol-Air. The standard MicroNet sensors from Schneider-Electric were modified by Barcol-Air to include carbon dioxide sensing. Visit http://www.barcol-air.nl for more information. In the United States, contact Alpha Controls and Services to order these sensor models. Alpha Controls & Services 4104 Charles Street Rockford, IL 61108 Office:  815-227-4000 www.alphaacs.com  

Issue How to use the Encoder and Encoder Client to encode new cards or configuration cards for modifying Smart Card Readers configuration parameters. Product Line Security Expert Environment Security Expert (PRX-ENC-SW) Smart Card Readers Encoder (PRX-ENC-DT) Encoder Client (AKA Credential Manager) Cause Unable to find documentation or the Encoder Client software to allow the use of the Encoder to encode cards. Resolution As it stands right now, the encoder software required for the encoding process is not currently released and therefore the encoding process can not be supported. Currently, we are unable to support customers wanting to perform their own encoding of: Security Expert cards third party cards Mifare Configuration Cards for programming Security Expert Smart Card Readers. Contact your local solution category management for an updated road map on when this Encoder Client and encoding functionality will be released

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF

Issue Using BQL query to extract data from a G3 station How to display data from the BMS system on their custom / third party application. Environment I/A Series G3 Cause A requirement to display data from the BMS system on their custom application. Resolution You can query for data using a BQL (Baja Query Language) query. The Baja Query Language ( BQL ) is an SQL-like query language that provides a mechanism for identifying various sets of data. It provides an ad hoc way to search for data based on some criteria. 3rd party applications which is capable of running a web query can be used to query data from a G3 station. One such application is Microsoft Excel. The  Niagara BQL Query Examples PDF  provides several examples of BQL queries as well as an example of using Excel web query. Most data in a station can be queried including point values etc. For detailed description of BQL usage, refer to the Niagara Help in Workbench ( as shown below).

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 A Jace8000 requires a factory reset via installation clean distribution file but a current backup of the station is not available and the Jace is not communicating via platform or station connection. Product Line TAC IA Series Environment Jace 8000 Cause No current .dist or .bog of the Jace is available. If the Jace has to be reset to factory condition, all data is lost. Resolution If the Jace8000 is running N4, then utilize the USB port to make a backup to a USB stick per the Jace8000 Backup and Restore Guide. If the Jace8000 is configured for AX, the USB backup is not available, an attempt to transfer the station using a File Transfer Protocol utility can be attempted.   Connect to the Jace via serial shell using Putty or a similar program, refer to the System Shell section of the Jace8000 Install and Startup Guide for details.  Once the System Shell menu is displayed, enter 4 to select Enable/Disable SSH/SFTP.  When prompted enter a port number, 22 is typically used for this purpose Using the FTP utility, connect to the Jace.  The following screenshot shows the settings when using FileZilla to do this. Enter the IP address of the Jace, the platform user name and password and the port number you enabled in the Jace and click on Quickconnect. On the Local site (your PC), navigate to C:\Users\your username\Niagar4\stations On the Jace side navigate to /home/niagara/stations Transfer the station folder from the Jace to the Local site.

Issue When the Vista export file is converted using the Vista conversion to an EBO Server the Xenta devices are created with an empty application. Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Conversion tool Cause The user name that was used to log into Vista Database to run the Database export does not have full access to the Xenta devices Function Block Program. Resolution Log in with the System user that has full access to the Vista Database and export the database for the conversion tool to use.

Issue When trying to embed a website in an N4 Px view, the site renders in Workbench but not in most browsers displaying this error in the browser's developer console; Product Line TAC IA Series Environment I/A Series N4 Workbench Web Browsers, Chrome, Firefox, Edge, Internet Explorer Cause Most major browsers no longer support  NPAPI/ Java plugins.  Oracle has stated they would remove it in JDK 9  and from Java entirely.  The N4 WebBrowser object under the workbench pallet requires Java to work correctly.  That is why it only works in the Workbench environment, Internet Explorer, and older Oracle Java platforms. Resolution When using the WebBrowser object in Niagara N4. Viewing in the Browser Preview Mode or in an actual browser that doesn't support the Java plugin, the embedded site will not render. The only solution is to use Internet Explorer or the Web Launcher application detailed in the attached document to view the Px. For more information, refer to the Niagara Web Launcher - Niagara Java-based Web Clients Guide PDF

Issue The Alarm Priority does not display the correct value (110) in the Alarm View or Event View when the Alarm is in the "Alarm" state and displays 100 Value instead. It displays correctly in the Alarm view when the alarm state is "Acknowledged" or "Reset", and it displays correctly in the Event view when the alarm state is "Reset Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Incorrect configuration Resolution There is an"Alarm decorator override" that seems to override the priority for the alarm If in alarm state and priority is 110, then the priority is overridden to 100 as configured in the alarm decorator object Removing the override in the decoration will resolve this issue

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 backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In   Project Configuration Tool , in the   Project   view, select the project you want to export. On the   Header   toolbar, click the   Export project   button  or right-click on the project and select "Export". On the   Export selected project(s)   dialog box, in the   Folder   box, browse to the folder on your hard drive where you want to save the exported project. Click   OK . TIP:  You can select multiple projects and export all of them at once.  

Issue For various reasons it may sometimes be desirable to have the system display the raw bitstream of a card. Here is the configuration needed to accomplish it. Product Line Security Expert Environment Security Expert Controller Security Expert Server Cause Guidance is needed on how to make a Security Expert system display the actual raw bitstream of a Wiegand card. Resolution Configure the reader's format for Custom Credential Make sure the card presented at the reader will not  result in valid access granted transaction, e.g. by temporarily removing that user's access to the door.  As seen in the image below, the system will display the format of the card (i.e. 37-Bit), followed by the actual Raw bitstream, for all invalid access transactions.   If the system is able to decode the card, it also appends the decoded info in parentheses right after the raw bitstream, which can also be very useful.

Issue The system will not execute an unlock latched command on a door if the door is in the middle of processing a Request to Exit (REX) transaction.  (Client/Server 4.3.308.52    Controller 2.08.1247) The entry on the Status page below, indicates the system processed the 'unlock latched' command, but left the door in its current state. This can be problematic when attempting to 'unlock latched' a busy high REX traffic door. Product Line Security Expert Environment Security Expert Controller Cause Firmware issue to be addressed in a future release. Resolution The workaround for this issue is to create a Programmable Function to perform the 'unlock latched' when the REX is not active.   1) Make a Virtual Output. 2) Set the Virtual Output's Activation Time to 1 second 3) Create a Programmable Function with the following settings:               Type:                              Door control             Door function mode:    2 - Follow pulse on output             Door control mode:      1 - Latch door unlock             Output to check:           The virtual output created in step 1)             Door to control:            The high REX traffic door you wish to 'unlock latched'   Note: Workaround works for native Security Expert door, do not work for INET transitioned door, a possible solution for INET transitioned door is to convert it to native Security Expert door.

Issue Are there any Example Reports for the new native Notification Reports which came out in EBO 3.2 to replace the now deprecated WebReports and Report Server? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause As of EBO 2022 (4.0) WebReports and the Report Server have now been deprecated and replaced by External Log Storage using Postgres SQL and Timescale DB, plus the new native Notification Reports  which are now built into EBO 3.2 and above, but there are no examples to help new starters to get going. Resolution A Schneider-Electric Community page has been set up specifically for  Notification Report users  so that they can share their Reports and collaborate on Reporting ideas: https://community.exchange.se.com/t5/EcoStruxure-Building-Operation/Reports-showcase-share-your-reports/m-p/388619#M75732

Issue Device Administrator is not able to load new database version 3.2.3.59  into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Upgrade to 3.2, 3.1, and 3.0 failed, EBO 2.0 was successful Resolution This is an issue with the new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70% This can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.7 and later versions Jace 8000 Tridium Niagara N4.7 and later versions Enterprise Server  Cause The SpaceLogic (f ormerly known as SmartX)  IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.     * New v4.0 features are not supported when used with EBO v3.x.x.. Note: RP-C is only supported on EBO 3.0 and later   SpaceLogic BACnet/IP devices can be upgraded using WorkStation , as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded u sing the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers Note: SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 currently for Jace 8000 and Niagara Enterprise Server using N4.7 and newer platforms.    

Issue IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue Unable to determine why Users are being denied access at doors. Reviewing events shows that the Users are being denied access due to an Access Level that is not even configured to allow access to that door. User [UN1] Door not allowed [DR2] Using Access Level [AL1] Product Line EcoStruxure Security Expert Environment Security Expert Cause The user has no valid access levels for this door. Resolution The event showing like this is a side product of how access is validated. When a user badges at a reader, the card is first matched to a User record.  Each of that user's access levels is then checked, from top to bottom, until either one is found to have access to the door, or all are checked and none have access to the door. If a valid access level is found then that is the access level shown in the Granted entry/exit event. If the user has only one access level and it is not valid for this door, the event will appear to be correct as that will be the access level name shown in the Door not allowed event. If the user has multiple access levels and none of them allow access to the door then the Door not allowed event shows the name of the last access level checked, which in all cases is the one from the bottom of the user's list of access levels.

Issue Embedded WebStation client licenses were needed when logging directly into a SmartX server as of 3.0.1 but are no longer needed Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation SmartX Server Cause The license requirement is being removed due to market feedback. The quantity of direct web connections to the SmartX server is restricted by the Architectural Guidelines only. Resolution Important for version 4.0 (EBO 2022) and above:  Note that in Building Operation 2022 (v4.0.x) and above, WebStation licenses have now been enforced at the server level and are required.   If there is no embedded server license for example "XWSWXBU0000SD ASP Bundle - Standard" in the SpaceLogic server it will not be possible to login to the server using Webstation. The Webstation license is included in the embedded server license.   For version 3.0.x The change is available via a HotFix to version v3.0.3 and will be incorporated into Maintenance Release v3.0.4. In both the HotFix and the Maintenance Release, license status presentations in the Device Administrator and Control Panel will indicate the availability of 99 client licenses. However, the supported quantity of direct web connections to a single SmartX server is established by the Architectural Guidelines; currently, the maximum is five concurrent connections. In v3.1, the Device Administrator and Control Panel will not list client license availability at the SmartX server level since it is not constrained by licenses.  

Issue When connecting to several OPC servers, is it necessary to have several OPC Client licenses? Product Line TAC Vista Environment Vista OPC Server Cause In some cases, several counts of the same license module is required if several simultaneous sessions are in use. (Example: Workstation) Resolution You can connect to several OPC servers simultaneously while you just have (1) one OPC Client license.