Building Automation Knowledge Base

Issue Unable to drag and drop the Application folder into the include types box while performing a search of application files.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation v3.0.x  Building Operation Workstation v3.1.x  Cause Searchable interface not implemented on the Application folder (nor on other devices like b3). This is a known issue in v3.0.x and v3.1.x Resolution Rather than using the left mouse button to drag the application folder, right-click the application folder to drag and drop into the include types box. This is to be fixed in 3.2.1.x.

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.  

Issue Some AS-P controllers do not have a heatsink installed where others do. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Cause Originally the design of the AS-P was to be universal and comply with various standards with one design. The standards that have a strict temperature requirement on components are related to Smoke Control and Access Control. In 2019 we decided to streamline the production of AS-P and only use the heatsink on those versions where it is required. AS-P with heatsink installed. AS-P without heatsink installed. Resolution The AS-P SMK and AS-SSC versions will still have the heatsink all other models after week 50 of 2019 will come without heatsinks. Products without heatsinks can be identified by a suffix on the individual box that the product came in. A suffix -A is with heatsink and suffix -B is without a heatsink, 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 Services for assistance. Issue For various reasons, it may be necessary at times to change a b3's Device ID (Object ID) to avoid a duplicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) BACnet Cause There is little or no formal documentation on steps to change the Device ID of an existing B3 controller. Resolution As seen in the screenshot below, once a b3 is added to the network, its Device ID, EBO Object ID, can not be changed.  The reason for this is that the Device ID references the device and objects contained within it.  Once the ID is changed, such references will become orphans. To successfully give the b3 a different Instance/Device ID the b3 must be deleted from the MSTP Network in the Building Operation database and recreated   Write down the b3's Serial Number, MAC Address, Model, and BACnet Name before deleting it. Right-click and Export all BACnet Objects within the b3's Application Folder to file (.xml) Delete the b3 from under the MSTP network. Re-create the b3 manually using its S/N, MAC, Model, Name, etc but enter the new Device ID Commission/Download the b3 to get the new ID to take effect Import the File (.xml) exported in step 2 back into the newly created b3's Application Folder Commission/Download the controller again Important: References to the old Device ID will no longer work and must be re-created.

Issue BACnet tuning policies improperly applied can cause BACnet network problems Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series AX / N4 Jace Cause Configuration parameters in the BACnet tuning policies can initiate high polling rates, force high volumes of writes, reads, and apply confirmed COV to BACnet proxies in the Jace / ENC. Resolution The following video will help us, Configure the "DefaultPolicy" as well as creating additional tuning policies for BACnet proxies   Apply tuning policies to regulate BACnet network utilization

Issue Remote Factory Reset of SmartX IP controller MPX RPC IPIO Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation EasyLogic RP-C Building Operation EasyLogic RP-V Building Operation EasyLogic RP IO Expansion Module Building Operation EasyLogic MP-C Cause From v3.1 there is a facility to remotely Factory Reset a SpaceLogic BACnet/IP devices (formerly known as SmartX) and EasyLogic BACnet MS/TP devices. A quick look at the process and what versions of SmartX controller firmware are required Resolution Remote Factory Reset fails if the Controller is at v2.00. Remote Factory Reset operates correctly if the Controller is at v3.00 or higher. A Remote Factory Reset on a Controller with Static IP is best avoided. Although a Factory Reset is now possible, it should not be considered standard work process, but it shows that using DHCP serving of IP addresses does have advantage if a factory reset is required.

Issue Need program example of Macro Block for Function Block program. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Macro Block Library is intended as an example and may need to be adjusted to the actual application. Resolution A Macro Block Library is included in the installation of the Function Block Editor. Inside the Function Block Editor, right click in an empty space and select Load Macro. If you do not see the Macro Block Library directly, please navigate to  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 3.1\WorkStation\Function Block Editor Here, you can select Macro Library Function block to find different Macro Blocks:                  Macro Block Library Macro Block Library for TAC Xenta series Macro Block Library Xenta700 Macro Block Library For TAC Xenta 700 series Macro Library Function Block Macro Block Library For Function Block Editor Process Models Process Models Library For TAC Xenta series Process Models Function Block Process Models Library For Function Block Editor Process Models Xenta700 Process Models Library For TAC Xenta 700 series User Library Reserved location for user made Macro Block The first three folders in the list above (Macro Block Library, Macro Block Library Xenta700 and Macro Library Function Block) each contain the following sub folder structure: Air handling Control Function Calculation Common Efficiency Energy Psychrometric Heating Control Function Miscellaneous Function SNVT Timers The other four folders contain macro blocks without any sub folder structure, i.e. they are located directly in the folders.

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.

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.

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. One workaround is to create a Search or Watch View and add the signals the user should be able to change or add the points to a graphic. Set permissions to the Search, Watch window, or graphic.

Issue How to properly share background images across multiple Security Expert Client machines. Product Line Security Expert Environment Security Expert Cause It may, in some instances, be required or best practice to have a single location to store Floor Plan background images, this provides easier management of where these files are kept when using multiple clients.  Below is an example of how to set up a network share of background images. Resolution There are two methods for using Floor Plan background images across multiple client machines. Method 1 - Copy the images to each PC Set the background image to the local image file. Copy that image file to each client PC and save it in the same local network folder. Method 2 - Share the images folder on a network share that all client PC's can view. Ensure all PC's are in the same Domain or Workgroup. In each client PC, have configured an Admin user or the same user with access to the network location on the server. On the server, share the image folder with the user in step 2. Floor Plan Properties In the Floor Plan map, use the network path to the shared folder/file. Background File On the client PC's ensure the same user in step 2 is created and can see the network share by browsing to it. Network Share

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 How to use RoamIO to set the Infinet ID of Infinet device to zero before re-deploying the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Service Tool Cause Need a way to set the Infinet ID of Infinet device to zero before re-deploying the device. Resolution  This video demonstrates… Tell if the i2 device has an Infinet ID assigned by observing the TD/RD LEDs on the device. Use the RoamIO to connect directly to the i2 device and reset its Infinet ID to zero. Confirm by visual observation of the device's TD/RD LEDs that the ID has been successfully set to zero.

Issue What is the procedure for upgrading firmware in an I/A Controller? Product Line TAC IA Series Environment Workplace Commissioning Tool I/A Series MNB Cause Improvements to MNB firmware require upgrades to be made periodically to the controllers. Resolution This video demonstrates how to upgrade MNB devices with the I/A Commissioning Tool.

Issue How can Workplace Commissioning Tool be used to backup projects and restore of I/A devices? Product Line TAC IA Series Environment I/A Series WorkPlace Commissioning Tool I/A Series MNL controllers I/A Series MNB controllers  Cause Define the procedure for backups/restore in Workplace Commissioning Tool Resolution This demostration shows how to perform backup and restore procedures using Workplace Commissioning Tool

Issue Who-has Broadcasts are causing a large amount of BACnet network traffic Product Line TAC IA Series Environment I/A Series MNB I/A Series WorkPlace Commissioning Tool Wireshark Cause Determining BACnet network issues caused by Who has? broadcasts Resolution The objective of this video are to Demonstrate how to troubleshoot a Who-has Broadcast Explain what initiates a Who-has Broadcast

Issue When importing a file from TAC Menta into StruxureWare Building Operation Functional Block Editor, the import of the application file fails. Environment TAC Vista TAC Xenta StruxureWare Building Operation Cause The following characters are not allowed in object names in StruxureWare Building Operation. • / • " • ? • * • ~ • White space is not allowed in the beginning or the end of an objects name. • . (period) is not allowed in the beginning of an objects name. Colon (:) is not allowed either, but will automatically be replace by an underscore (_) when importing   In TAC Vista, signal names could contain the character "/". In SmartStruxure, this character is not allowed. Resolution Remove illegal characters from object names in the Function Block program.

Issue When trying to upgrade a SmartX server from 3.0.x.x to any hotfix build, you get the following errors: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Device Administrator Cause This is an issue within 7z. The path becomes too long on the unzipping of it. In 3.1 and onwards, only the GUID is used as the folder name. In 3.0, its is the file name + GUID which causes the path to become too long. Resolution Rename the firmware file so that it is shorter in length.

Issue Can a schedule or calendar be printed? Environment StruxureWare Building Operation site Cause Desire to print a schedule or calendar either from AS or ES Resolution Neither Schedules nor Calendars can be printed from Workstation or Webstation using Building Operation

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 PCT client can't start properly with "Hardware virtualization is not enabled" error. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) (All Versions) Cause Hardware Virtualization is Disabled or not available for PCT Resolution  Install "Intel® Processor Identification Utility" then verify the status of "Intel® Virtualization Technology" from the Utility. Using the table below, you can see if your processor supports Intel® Virtualization(provided by Intel).  The above information can also be found on Intel® Virtualization Technology web page If Virtualization is disabled in BIOS then enable it from BIOS else identify other software utilizing the Virtualization and stop the application.  Use Win key or press the Windows Start button Type: cmd Select Run as Administrator  Verify command prompt window title bar is Administrator: Command Prompt Type: shutdown /r /fw/ /f  Press enter and the computer will shut down immediately forcing all applications to close (/f) and restart (/r) into firmware interface (/fw)   If the issue persists, the following article may provide the answer Knowledge Base article - PCT error Hardware-virtualization is not enabled-Please-enable.