Issue Setting up Visual Verification to track who has gained access to a door using Access Expert Product Line Access Expert Environment Access Expert v3 Cause Verification of access is a common feature request in access control integrations. The following steps show how to enable and access this feature within the Access Expert v3 product. Resolution Open and connect to the instance with the required credentials Select the Access Control Tab and click on the Visual Verification button Click on the Assign Reader button to Add the respective readers and click OK The Visual Verification Window opens up with the readers that were selected from the previous step on the right side of the screen. Select the necessary readers that will be used for the verification.                    Once someone scans a card on any of the selected readers, their saved image will then be displayed    *Note* If this Window is closed the configuration for Visual Verification will be lost and will need to be recreated

Issue With revision 1.0.37 and later, folders under the instance within the navigation tree are no longer there.   Product Line Access Expert Environment V3 Hosted Cause The 1.0.37 release of the Keep software removed the folders under the instance within Folder Explorer. Resolution Use the corresponding tabs at the top of the window.  

Issue Permissions on V3 Product Line Access Expert Environment Managing Permission settings for Individual Groups. Cause Limiting the Permission for users in accessing certain objects within the system for better management. Resolution Permissions can be configured for each user by following these steps: Open the API and connect to the respective instance with the relevant credentials Go to the General Configuration Tab Select the Groups Icon If creating a new Group, click the Add Group Button If modifying, select one from the list and double click to open it up Click on Add Permission and select the Object Type  Select the various check boxes to Grant or Deny access  Once completed then click on the Save & Close button to close the Editor

Issue Unable to connect Continuum I/O's to Access Expert Product Line Access Expert Environment Win 8.1 and above on Version 3 Cause The Continuum Integration has only been configured to bring in the AC-1 and AC-1 Plus door controllers as sub-devices. Resolution There is no resolution, but the Continuum I/O's are simply not compatible with Access Expert. Use Mercury 16 In/Out boards for applications that require these types of devices.

Issue DC1100 / DC1400 displays message "No Sensors Connected" or displays temperature values that are not representative of the temperatures being sensed. Environment DC1100 / DC1400 Discrete Controller and associated Sensors. Cause DC1100 / DC1400 is connected to Sensors having incompatible resistance range. The resistance range of those Sensors compatible with the DC1100 differs to that of the resistance range of those Sensors compatible with the DC1400 "No Sensors Connected" message may appear in the Controller display as a result of the Sensors connected having a resistance that is out of range compared to that of the resistance range that the Controller Sensor Inputs are designed to recognise.  Resolution Check Sensor type connected to Controller. DC1100 Controller is compatible with the following Sensors :- STC 600 D Contact Temperature Sensor                               (Original Drayton Sensor = A704) STO 600 D Outside Air Temperature Sensor                          (Original Drayton Sensor = A702) STP 600 D Pipe Temperature Sensor                                     (Original Drayton Sensor = A703) STR 600 D Room Temperature Sensor                                  (Original Drayton Sensor = A701)   DC1400 Controller is compatible with the following Sensors :- STC 600 Contact Temperature Sensor                                   (Original Satchwell Sensor = DST) STO 600 Outside Air Temperature Sensor                             (Original Satchwell Sensor = DOT)    STP 660 Pipe Temperature Sensor                                        (Original Satchwell Sensor = DWT) STR 600 Room Temperature Sensor                                     (Original Satchwell Sensor = DRT)

Issue DC1100 / DC1400 displays identical temperatures for all connected Sensors.  It is not uncommon for a temperature of 39 deg C to be displayed for each Sensor connected to the Controller. Environment DC1100 Stand Alone Optimiser / Compensator Controller DC1400 Stand Alone Optimiser / Compensator Controller Sensors compatible with DC1100 :- A701 Room Temperature Sensor A702 Outside Air Temperature Sensor A703 Pipe Temperature Sensor A704 Contact Temperature Sensor STC 600 D Contact Temperature Sensor           (Original Drayton Sensor = A704) STO 600 D Outside Air Temperature Sensor      (Original Drayton Sensor = A702) STP 600 D Pipe Temperature Sensor                 (Original Drayton Sensor = A703) STR 600 D Room Temperature Sensor              (Original Drayton Sensor = A701) Sensors compatible with DC1400 :- STC 600 Contact Temperature Sensor               (Original Satchwell Sensor = DST) STO 600 Outside Air Temperature Sensor          (Original Satchwell Sensor = DOT)    STP 660 Pipe Temperature Sensor                     (Original Satchwell Sensor = DWT) STR 600 Room Temperature Sensor                  (Original Satchwell Sensor = DRT) 39 deg C. Cause DC1100 / DC1400 displays identical temperatures for all connected Sensors.  A Sensor temperature of 39 deg C is a common value displayed. Resolution Check each Sensor is correctly connected to its appropriate "Common" Terminal of the DC1100 / DC1400 Wiring Base Check each Sensor Cable Screen is correctly connected to the Earth Terminal of the DC1100 / DC1400 Wiring Base Check that a good Earth connection exists between the Earth Terminal of the DC1100 / DC1400 Wiring Base and the site Earth Check that a good site Earth is available for connection to the DC1100 / DC1400 Wiring Base. N.B. In the event that the DC1100 / DC1400 continues to display identical temperatures for all connected Sensors following completion of the above checks then it is suggested that the Cold Start procedure is applied to the Controller and the result observed.

Issue DC1100 & DC1400 Optimiser / Compensator Controller Cold Start malfunction. Environment DC1100 Optimiser / Compensator Controller. DC1400 Optimiser / Compensator Controller Cause DC1100 & DC1400 Optimiser / Compensator malfunction preventing Cold Start procedure being undertaken.. Resolution 1.  Repeat DC1100 & DC1400 Controller Cold Start procedure. A manufacturing problem experienced with the DC1100 and DC1400 may result in difficulty applying the Cold Start procedure. Faults have been reported in respect of a number of DC1100 Controllers in particular, where difficulty has been experienced when applying the Cold Start procedure. The fault appears in those Controllers where the Enter and Exit Keys foul their respective cut-outs in the Top Cover Panel, thus preventing Cold Start from being achieved. This is due to a conflict in assembly tolerances that can cause the Keys to remain depressed after they have been pressed in, due to their being trapped by the cut-outs they should pass through. In such instances it may be necessary to undertake the Cold Start procedure a number of times before any trapped Key is released sufficiently to enable resetting of the Controller to be achieved. Actions are currently in hand to rectify this matter and the positioning of the cut-outs in the Top Cover Panel relative to the Key positions has been addressed from a design point of view. Examples of the Top Cover Panel incorporating newly dimensioned cut-outs are not due to be available for inclusion in production assemblies until Week Number 2010 45 at the earliest however. Consequently current production assemblies incorporating the existing Top Cover Panel will continue to be utilised in all newly manufactured Controllers for the moment at least. Similarly an opportunity will not arise until Week 2010 45 for any Controllers currently held in stock in S-E Sweden to be re-worked to include the new Top Cover Panel prior to their sale.

Issue TAC Valve Body published Cv values may differ markedly to equivalent Kv values.  Environment TAC Valve Body published data utilised when sizing and selecting S-E / TAC Control Valves. Cause TAC Valve Body published Cv values based on flow rates measured in U.S. Gallons per minute rather that U.K.Gallons per minute., Resolution Check published Cv value relative to published Kv value stated for TAC Valve Body. If published Cv value is within 3% of published Kv value then Cv value may be used for sizing / selection of Valve Body. If published Cv value is up to 17% higher than Kv value then Cv value should not be used for sizing / selection of Valve Body. Cv values published in older TAC Valve Body Data Sheets should be checked before considering use in U.K. valve sizing formula. Numerous TAC Valve Body Data Sheets show that for a particular Kv value, the equivalent Cv value is approximately 17% higher than the Kv value. For example, where TAC Valve Body Data Sheet shows Kv = 10, then equivalent Cv = 11.7 or in other words Cv = Kv x 1.17 Cv values published in Satchwell Valve Body Data Sheets however show the relationship between Kv and Cv as:- Kv = Cv x 1.03 or in other words Cv = Kv x 0.97 This difference in equivalent values is due to Cv values stated in some TAC Data Sheets being based on flow rates measured in U.S. Gallons per minute, while those Cv values stated in Satchwell Data Sheets however are based on flow rates measured in U.K. Gallons per minute. If flow rates are measured in U.S. Gallons per minute, then the following conversion factor applies :- Kv = Cv x 0.86, as the U.S. Gallon is smaller than the U.K. Gallon. Taking published TAC Valve Body Data Sheet information therefore, where the Cv value is stated as 11.7 and the Kv value is stated as 10, confirms that the conversion factor Kv = Cv x 0.86 ( 11.7 x 0.86 = 10 ) has been applied, further confirming that published Cv values are in fact based on U.S. Gallons and not U.K. Gallons. Consequences of this are as follows : - If it is assumed that the published Cv value is a U.K. Cv value, when in fact it is a U.S. Cv value, and the published Cv value is then used as a basis for valve sizing and selection, then this will result in a smaller Valve Body being selected than would otherwise be the case. Consequently, once installed, the selected Valve Body will produce a much higher pressure drop and correspondingly higher authority for a given flow rate than would otherwise have been the case. In practice the installation of an undersized Control Valve can result in starvation of flow to the item of plant being controlled and the potentially costly replacement of the Valve Body for another of a larger size. Similarly, the installation of an undersized Control Valve will result in a greater pressure drop being applied to the hydraulic circuit than may be desirable and could lead to an adverse effect on the performance of the associated circulating pump. It is important to ensure therefore that where both Kv and Cv values are published for a given Valve Body, the Kv value is utilised when undertaking valve sizing and selection.  This should ensure that a Valve Body of the correct size is selected. Measures are currently in place to actively remove all references to Cv values from both S-E / TAC Data Sheets and all future editions of the S-E HVAC Valves and Actuators Catalogue.

Issue NEMA 4 classed DuraDrive actuators cannot be used with the VB-7323 diverting valves Environment NEMA 4 DuraDrive actuators VB-7323 diverting valves Cause Which NEMA 4 classed DuraDrive actuators can be used with the VB-7323 diverting valves Resolution There are no NEMA 4 solutions available. Consider using the MA-318 or 481 for two position applications. No modulating spring return options are available but non-spring return gear train actuators with AV-391 (150 pound plungers) can be used when the AM-363 gasket is added.

Issue EcoStruxure Building Operation different types of licenses and all features Version 1.9 and older: Difference between Workstation standard and Workstation professional Product Line EcoStruxure Building Operation Environment All versions Cause Due to different features of each license, customer may get confused which license to order. Resolution See the version of the latest EcoStruxure Building Operation Part Number Summary document on the Exchange for all license part numbers.   Versions 2.0 and Newer Note: The licensing part numbers and structure has vastly changed starting in version 2.0 and newer.  See the search query below on the Exchange for more detail regarding the Scalable Pricing Policy that started in version 2.0. EcoStruxure Building Operation Scalable Pricing Information   Versions 1.9 and Older Note: There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing)  

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, 5.0, 6.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 EBO 2022 (4.0.3.176) Maintenance Release Jul 2022 - See release note EBO 2023 (5.0.1.86) Dec 2022 - See release note EBO 2024 (6.0.1.93) Mar 2024 - See 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. EBO 2023 (5.0.1.128 and later) New SpaceLogic and Easylogic Controller support, External Storage support for MS SQL, Some support for IPv6, BACnet protocol rev.16, Virtualized Automation Server - Edge Server added,   See release notes for details. EBO 2024 (6.0.1.93 and later) Added New Software Assurnace, Sustainability Pack, EBO Enterprise Server and Enterprise Central for Linux, OPC UA Client Support, Modbus2 Support, Visual Programming for Function Block, XLSX Report, and Touch Room Controller Support. 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