Issue What are the basics steps when setting up the Engage Mobile application to use it for the first time? Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause The Engage mobile application enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. Resolution Below are the basic steps when setting up the Engage Mobile application to use it for the first time:  First create and configure the Occupant App Menu object. Make sure Bluetooth is enabled for the RP-C. Download the Engage mobile application and connect to the RP-C Available on App Store and Google Play To see details for every step please see video:   ... View more

Issue When a TGML graphic is opened from Webstation and the user right clicks on a value in the graphic to open properties, it can take up to 20 seconds before the properties dialog is displayed. During the 20 seconds the working area is just grey. Product Line EcoStruxure Building Operation Environment Building Operation Webstation 2.0.4 and earlier versions Cause This problem only occurs when the signals in the graphic resides in a TAC Xenta; The problem has not been observed with Modbus or BACnet signals, and is only present in Webstation, not in Workstation. Resolution This issue is fixed in EBO 3.0. There is also a hotfix for version 2.0.4. It is labelled 2.0.4.5801. Contact you local technical support organisation if you need the hotfix. ... View more

Issue When "Engage App BLE Filtering" set to "True" in an RP-C it is not possible to connect to the RP-C via Bluetooth using eComission SmartX controller mobile application. How do I set "Engage App BLE Filtering" to "False"? Product Line EcoStruxure Building Operation Environment Building Operation eCommissioning Tool Cause A factory reset of an RP-C will set "Engage App BLE Filtering" to "True". The "Engage App BLE Filtering" is also set to "True" when upgrading the RP-C from firmware version 2 to version 3. Resolution The only way to set "Engage App BLE Filtering" to "False" is to use the  eCommission SmartX Controllers mobile application connected to the RP-C using an IP connection.   ... View more

Issue Can an export file from one version of EcoStruxure Building Operation(EBO) be imported to another version of EBO?  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Export files are in general NOT backward compatible. A Script or Function Block Program that is exported from for example version 3.1.x is NOT guaranteed to import successfully into an earlier release Resolution Starting in version 3.0.x, import files exported from a later release than where they are imported will be denied. An export file from 3.1.x cannot be imported in 3.0.x. An export file from 3.0.x can however still be imported in 2.0.x, but it' s not recommended, and it may fail to import successfully. In version, 3.1.x import files exported from versions older than version 1.3, will be denied. Starting in version 3.2.x, import files exported from versions older than 1.8.x will be denied. ... View more

Issue Is it possible to set software permissions for a Public Value in a Menta or Function Block program in  EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Public values in Function Block Programs (FBP) or Menta programs are not seen as objects but as attributes of the FBP or Menta object. Resolution It is not possible to set software permission on point level for a Menta program or Function Block Program, only on the Module level. ... View more

Issue When looking in the EcoStruxure Building Operation Architectural Guidelines for the maximum number of Xenta and LonWorks devices per server is a TAC Xenta I/O module placed under a TAC Xenta 300/400 counted as a LonWorks device? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The SmartX Server or Enterprise Server doesn't know that the TAC Xenta I/O module exists if it is placed under a TAC Xenta 300/400. The SmartX Server or Enterprise Server only communicates with the TAC Xenta 300/400 and not the TAC Xenta I/O modules under it.  Resolution No, the TAC Xenta I/O module does not count as a LonWorks device in the EcoStruxure Building Operation Architectural Guidelines if placed under a TAC Xenta 300/400. ... View more

Issue After conversion from TAC Vista to EcoStruxure Building Operation (EBO) the System alarm "Log full" is seen in the Alarm list for trend logs in TAC Xentas Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause This issue is only seen after conversion from TAC Vista to EBO and probably caused by a calculation mismatch between the Extended Trend log (ET log) in EBO and the Xenta trend log. Resolution To get rid of this issue a "Clear trend log" must be done on the Xenta trend log and then a download completed on the TAC Xenta. Before doing the "Clear trend log" make sure that all log values are saved in the ET log Right-click on the ET log go to "Activation" and "Force transfer" Right-click on the Xenta log go to "Activation" and do a " Clear trend log" Right-click on the TAC Xenta go to "Commission", mark the option "Application download" and click "Commission" ... View more

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"   ... View more

Issue When doing an "import Trend Logs" in TAC Vista Conversion Tool only HTTPs works and not HTTP. When using HTTP the error message below is shown: "Log on to Building Operation server failed because Failed to access the server, a network error occurred" Product Line EcoStruxure Building Operation Environment TAC Vista Conversion Tool version 3.1.1 Cause This is an issue fixed in TAC Vista Conversion Tool version 3.2. The issue is that the "Import Trend Logs" tab looks at the HTTP/HTTPS settings of the "Convert Database" tab instead of its own. Resolution Use TAC Vista Conversion Tool version 3.2 when available. Workaround: Set the HTTP/HTTPS settings on the first tab(Convert Database) even if "Import of trend logs" is done. ... View more

Issue When a TGML graphic is opened from Webstation it takes 30-120 seconds, depending on the number of values in the graphic, before the values appear in the graphic. It takes a long time before the actual graphic is opened. When the same graphic is opened using Workstation, it only takes a few seconds before the values in the graphic are updated. The problem is seen when Webstation is connected to the Enterprise Server (ES) if connecting directly to the SmartX server the values come in fast. Example of how it looks in Webstation before the values come in: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and earlier Cause For every value in the graphic Webstation need to read the type of the value to know what kind of object it is and that is what takes time. This information is cached in Workstation and that is why the values are updated much faster in Workstation than in Webstation. This is changed in Webstation version 3.1. Now the type of information is cached in Webstation also. The first time the graphic is opened from Webstation it will take the same period of time as before. After that the type is cached and the values will be updated much faster the next time the graphic is opened. Resolution Upgrade the ES (Webstation is a part of the ES installation) to version 3.1 or higher ... View more