Building Automation Knowledge Base

Issue Unable to use the “Contact Open” nor the “Battery Low” statuses of a SED-WDC-G-5045 on EBO.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause The SED-WDC-G-5045 points (Contact Open, Battery Low and others) are not exposed individually but in a string of 10 points, bit 0 to bit 9.     Resolution 1. Add a: New object / Program / Script program. 2. Rename it to identify it, in this example it has been renamed Script program SED 3. Right-click on it, click on Edit, Script Editor window will open 4. Paste the below 4-lines script 5. Save 6. Change the “Type” from “Floating” to “Boolean” 7. Save 8. Close Script Editor window   Numeric input IASZone Numeric output ContactOpen, BatteryLow ContactOpen = (IASZone Bitand 2 ^ 0) > 0 BatteryLow = (IASZone Bitand 2 ^ 3) > 0       9. Right-click on “Script Program SED”, click on “Edit bindings” 10. Drag the “IAS Zone” point and drop it on the “Input / IASZone” bindingSave     12. Create a Digital Value 13. Bind it to the Contact Status point from the” Script Program SED” output. 14. Save      

Issue When launching Workplace Tech or Workplace Tech Editor (EBO), the Workplace Tech ribbon does not appear or displays an error indicating it has not executed. Product Line TAC IA Series, EcoStruxure Building Operation Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause Smartware Studio 360 release 5.1.540 and later contains a 64-bit version of the Microsoft Access database.  It was modified to allow for installation with either Office 32-bit or 64-bit.  Workplace Tech and Editor requires a 32-bit version of Visio.  Microsoft normally does not allow 32-bit and 64-bit applications to be installed on the same OS.  Because of this, the COM Add-in for the Workplace Tech ribbon can fail. Resolution The Microsoft Access DataBase engine can be uninstalled in the Programs and Features of Windows.  For Studio 360 to function properly, it will need to be reinstalled.    

Issue Proper handling and preparation of existing .vsd files help eliminate the crashing and lockup of the Visio application. Product Line EcoStruxure Building Operation, TAC IA Series Environment Workplace Tech Editor EcoStruxure 1.9.x - 3.2.3 Workplace Tech 5.9.1 - 5.9.4 Visio 2013, Visio 2016 Note: This does not apply to Workplace Tech Editor EBO 2022 (and newer) and Workplace Tech 5.10.x Cause The product is affected by the version of Visio in use as well as the file size and unused objects in the drawing. Resolution When using Workplace Tech 5.9.x with Visio 2013 or 2016, the file has to be opened in "Compatibility Mode." DO NOT CONVERT. Illustration 1 While the .vsd file is open in Visio, not in Workplace Tech, use the "Reduce File Size" option and select the boxes in Illustrations 1&2. Illustration 2 In Visio 2016, after opening the "Inspect Diagram," (Illustration 3), select the first 3 boxes in the "Reduce File Size" option (Illustration 4). Illustration 3 Illustration 4 Save the file for use in the Workplace Tech Project or to be imported into your AS-P as a .vsd. Add the "cleaned" file to your project or import it to Workplace Tech Editor. Make sure the Visio 2013 or 2016 is at the most recent version and build. You can find this under the file/account/About Visio. If Version 1802 is available in your Microsoft Office update Channel, use it. Version 1801 was used in testing. For Visio 2013 Build 15.0.4971.1000 MSO 15.0.5007.1000 was tested (Illustration 5) Illustration 5

Issue Need to upgrade sites with Report Server to EBO 2022 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher. Resolution Since WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher, there is a Data Migration Assistant (DMA) tool available which read data from a WebReports 3.x and write it to External Log Storage. You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature.  When the External Log Storage feature is activated and configured, WorkStation and WebStation display the historical data in the event and trend views from the External Log Storage. Any server in the system can be configured to write historical data to the TimescaleDB database.   Data Migration Assistant (DMA) Tool can be downloaded from here. License required: External Log Storage requires license, refer to Software and Features that Require Licenses and Part Number Summary and Hardware Software Matrix  Hardware and Software requirement for External Log Storage: Ensure that the hardware and software requirements for TimescaleDB (www.timescale.com) and PostgreSQL (www.postgresql.org) are met. High-performance SSD storage is required and additional CPU/RAM capacity is required for larger EcoStruxure BMSs. As an example, at least 64 GB of RAM is recommended for systems with 100 EcoStruxure BMS servers. Refer to: Information Technology System Planning Guide (se.com) Merging Log data: External Log Storage decreases the amount of extended trend logs retained on the EcoStruxure BMS servers. You can merge log data from an extended trend log to the source log in External Log Storage. For more information, see Merging of Trend Log Data. Enhanced Reporting (XLSX Report Templates): The EcoStruxure BMS servers (3.2 or higher) provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there. Refer to: Examples for the new native EBO Notification Reports - Communities (se.com)  

Issue Is it possible to edit a document object like a text file from WebStation? Product Line EcoStruxure Building Operation Environment Building Operation WebStation Cause From WebStation, it is only possible to view a document. Resolution No it is not possible to change a document object from WebStation.   For other differences between WorkStation and WebStation, see the online help topic WebStation and WorkStation Differences

Issue EBO can't overwrite notification report file. "System alarm: File access error: sharing violation:" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Notification file is used by another program and "Uniqueness" paramter is set to "None" so EBO can't write on it, ex, Microsoft Excel opens the notification report.  Resolution Make sure that notification report is not used be another program, ex. Microsoft Word or Excel. If the program locking the notification file is not known, Windows Resource monitor can be used to know which process is locking the file, as below: Press Windows key+R to open "Run" dialog box. In "Run" dialog box, write “resmon” and pres Enter. In Resource Monitor "CPU" tab, expand "Associated Handels"  In "Search Handels" box, write the notification file name. In "Image" tab, note the process name. To end the process which is locking the file, Right-click on the process and then click on “End Process”. It is also possible to append or prepend a timestamp to the file name, so EBO can generate a new file each time.

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue How to create custom reports in Building Operation WebReports Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Custom reports are typically created by modifying another report and then saving these changes. Typically used are the factory-supplied reports as the base for a new report then enter the filtering criteria that are required to be used in the new report. Assign a unique name to the custom report and save the new report as a dashboard or prompted report.  There may be a need to create a report not based on any of the standard reports provided in these Report Packs, this article covers this process. Resolution To create a non-factory-supplied report within WebReports it is necessary to use an editor.  Since WebReports use Microsoft Reporting Services it is recommended to download the Microsoft SQL Server 2008 R2 Report Builder 3.0 or MS MSQL Server 2012 Report Builder.  This is a free tool provided by Microsoft that provides an intuitive report authoring environment for business and power users. This download provides a stand-alone installer for Report Builder 3.0.  Please note that Product Support does NOT provide support for Report Builder.  After downloading and installing the Report Builder application, the steps are as follows:  Each of these steps is also located on the Building Management System WebHelp site, a link for each of these steps is provided for additional reference and guidance. Start Report Builder and create a new blank report, see Creating a Basic Report for the steps.  After Creating the report create a data source that connects this report to StruxureWareReportsDB, see Creating a Data Source for these steps Then create the Data set, so add to the report which tables, views, stored procedures, and fields from the StruxureWareReportsDB are required to use in your report, see Creating a Dataset for these steps. This data can then be added to the custom report as required.  See Setting Up a Report for an example of setting up a report. See Adding an Image to a Report  on how to add images to the report  The new report now must be deployed to the Reports Server where it can be accessible to WebReports. To complete this procedure use SQL Server Reporting Services Report Manager. See Deploying a New Report to the Reports Server to view these steps in detail.  Finally, the report must be synchronized in WebReports to be deployed and therefore appear in the WebReports Reports Tree. Use WebReports with a Web browser to complete this procedure.  See Synchronizing WebReports with a New Report for the steps to complete this. Once all these steps have been completed successfully the new Report should be visible in the tree - the placement of these reports will depend on where they have been uploaded in step 5 above.  See the image below:

Issue The room controller is replaced on-site, and you need to copy the same configuration of the faulty Controller. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 SSL SE7000 Cause The wrong file format might have been used Resolution This Video explains detailed steps to copy the configuration to a new or a replacement controller:   Please note that the older controller will probably have an older firmware version, and thus, you might have to downgrade the new controller to the same version. Also, note you can’t downgrade to below 2.0.0. If the older controller has a version before 2.0.0, this solution will not work and will have to configure the new one manually. Only After the configuration has been transferred successfully you can upgrade the controller to a new firmware version.

Issue A new feature in EBO 3.2.X where the value is grayed out when the binding on the priority of a BACnet object matches the BACnet Default priority level Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Missing Release note documentation about the new feature added to EBO 3.2.X. Resolution In EBO versions prior to 3.2.X, when a bind in Priority matches the Default BACnet Write Priority, the values can be changed without forcing. From EBO 3.2.X, users need to force the value, let it change, and then un-force it. The following screenshots show this feature in more detail. The following image shows the Default BACnet write priority has been set to 16. Now, for example, if a program output is bound to Priority 16 of an analog value: The value property would be greyed out and has to be forced if changes are needed.   This is a new feature in EBO 3.2.X which is not mentioned in the Release Notes documentation.   Hint: A defect # 45570 has been documented in Release Notes 3.2.X about “Webstation - BACnet analog value's value property is not greyed out when there is a bind to the default priority.”. This issue has been fixed in EBO 4.0.X.   

Issue The automation server password policy is grayed out making it unavailable to make configuration changes. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium   Cause When an Automation Server is attached to an Enterprise Server, all of the password policy configurations are inherited from the enterprise server. Therefore the AS settings cannot be changed.  Resolution The password policies of the Automation Server must be administered from the ES when it is connected to an Enterprise Server.   In order to make changes to the password policy settings in the Automation Server directly, it must be detached from the Enterprise Server. Note: For EBO V 1.9.X and lower, the password policy settings can be located under Control Panel > Security and Communication > Security settings area. For EBO 2.0.X and higher, the password policy settings can be located under Control Panel > Security and Communication > Password policy.

Issue Resource Advisor platform, which serves as a repository for water, gas, and electric invoices, enabling customers to focus on evaluating metered data. Assisting organizations that are committed to sustainability. Setup information. Product Line EcoStruxure Building Operation, EcoStruxure Resource Advisor Environment Building Operation Automation Server Premium Building Operation Enterprise Central Building Operation Enterprise Server Cause Information on setting up Resource Advisor is not available for download Resolution Click this link for an overview of Resource Advisor. Attached is a more detailed document including EBO Setup Guide and links for additional Resource Advisor information.

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 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 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

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 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 After editing an MNL-800 application with the WorkPlace Tech Tool Editor, an error is displayed indicating that the application file could not be saved. Product Line EcoStruxure Building Operation Environment Building Operation Workstation >1.4 Building Operation WorkPlace Tech Editor Cause The name of a LON Network Variable (nvi or nvo SNVT) or a LON controller configuration constant (nci SNVT) contains a space. Echelon standards do not allow spaces in network variables or configuration constant names. Resolution Edit the application file removing any spaces or other non-supported characters from network variable and configuration constant names. More information is contained in the SBO WebHelp topic "WorkPlace Tech Editor"

Issue Detailing configuration and starting DWiz on a computer running EcoStruxure for Buildings Operation. Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Xenta 281 Xenta 301 Xenta 401 Cause DWiz (Download Wizard) was a part of the TAC Vista installation, but not so commonly used in EcoStruxure Buildings Operation, and therefore no longer included in the Start menu. It is however still installed and could be started from Windows File Explorer. Resolution   Verify the Com port used. If your computer does have a serial port, this is normally Com1 or Com2. If you are using a USB to RS232 adapter (like Aten), you could get a much higher number. The program requires a port number between 1 and 9. You may need to change the port number. This could be done via Windows Device Manager. In Windows File Manager, go to the directory where EcoStruxure Buildings Operation Workstation is installed. Here you will find DWiz.exe as well as MentaSetup.exe. Start MentaSetup.exe, adjust Com Port, select Apply and Close. MentaSetup        5.  Now it should be possible to start DWiz.exe located in the same directory.

Issue How to troubleshoot a communication issue with the Sigma interface Is there a log available within the ES that shows the Sigma communication between Sigma controllers and the ES Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Workstation Building Operation Enterprise Server Cause When troubleshooting Sigma issues in an ES it can be helpful to see the communication between the Sigma controller and the Sigma interface in the ES to help identify this issue. The trace log within the ES is available and is configured as described below in the resolution. Resolution The level of logging for Sigma in the Trace Log needs to be increased: Open Workstation and navigate to [ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.sigma" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Sigma issue, then perform these steps now. e.g. If ifs a graphics issue then run the respective graphic. Retrieve the log by right-clicking [ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Sigma decoder can be used to assist in viewing/debugging the Sigma trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3).   Note: If the ES is restarted for any reason whether by manually stopping in the Software Administrator or other, the nsp.pin.sigma will default back to 'Information'.