Issue While editing a graphic, the editors components categories and menu options are too small to be used. This happens when Windows display scaling is not set to 100%. Product Line EcoStruxure Building Operation Environment Graphics Editor High Resolution monitor (4K) Scaling Cause An issue has been identified with how the default scaling used by Windows affects the Graphics Editor in EcoStruxure Building Operation 2.0 and later. Resolution Follow the steps below to work around the problem Update Windows with the latest available updates Update .NET Framework to latest version Change the compatibility settings of the Graphics Editor as outlined below   Open the Graphics Editor application file location   Open the properties for the Graphics Editor application   Override the DPI scaling 

Issue Is there a quick reference I can search to find out what features are included in a particular license When manually adding my Product during offline embedded license workflow, how do I know which Features is included and in what quantity?  Product Line EcoStruxure Building Operation Environment Building Operation EBO 2022 v4.03 and lower  Embedded Offline Licensing Offline Activation of Licenses Workflow Cause Currently, no information lists features for each Product name listed in the Part Number Summary for EBO 2022.  A documentation defect (QC 49762) has been raised, which should resolve this.  This article has been created to assist somewhat during this process while waiting for this to be corrected.  The recommendation, if possible, is to perform license activation online to avoid having to enter this detail.   Resolution Important Note: This information is no longer valid for EBO 2022 (Maintenance Release 4.0.4) and EBO 2023 and greater.  The details below are still provided for reference only and are not needed for these later versions.   Attached are two documents that provide version 3.0 and 4.0 License details.  The documents contain all searchable details, including: Product Name Features Part Numbers     Additional details required for Device Administrator "Feature Name" offline entry:   SpaceLogic Server license details Feature Name (seen in Device Admin) License name (seen in Features document) Description / Comments Automation Server server.as.base   SmartDrivers smartdriver.license   SNMP Notifications server.alarms.snmp   Personal Dashboard client.dashboard   TimescaleDB server.timescale   MQTT Publish/Subscribe server.mqtt.rw Enables EBO, as MQTT Client, to publish data on an MQTT Broker and to subscribe to the same data. Serial Modbus server.modbus.rtu Allows SmartX server serial communication - Modbus RTU Serial MS/TP server.bacnet.mstp Allows SmartX server serial communication - MSTP ES Connection server.connect.to.es Allows SmartX server to be hosted by an Enterprise Server Server I/O server.io Allows SmartX server to use IO Field Devices server.device.as Allows SmartX server to host one field device SAML Authentication server.as.auth.saml   Zoning client.zoning Enables use of zoning tools BACnet IP server.bacnet.ip Allows SmartX Server to communicate using BACnet IP Software Assurance software.assurance         Feature Name (Automatically included with bundle licenses)   client.webstation Allows Webstation to log on to an AS   server.cloud.customer Cloud connectivity - Checked by Cloud SMS (Production)   server.as.scalable Included in the license that allows SpaceLogic servers upgrades. i.e. Standalone to Standard etc.   Example: Product Name: ASP-NL Bundle upgrade - Full to ASP Full    Search the document for the product name in the attached document. In this case, the version 4 document.  Below is the result seen in the document: From this, the associated Features and Quantity are shown. In Device Administrator, then add the respective features and quantities when adding the product manually to the Entitlement. Use the above table to correlate between Feature Name and License Name. The example shown below:  

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. The following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Update Catalog To use the catalog, copy and paste the KB number into the "search".  Always select the 32-bit version of the update. Visio 2010 32 bit KB3114872                Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020                Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit Visio 2016/2019 32 bit KB4484333 NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue Creating an Extended Trend Log for b3 (Infinet i1/i2) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet i1 & i2 Controller Building Operation Automation Server, AS, ASP, ASB Extended Trend Logs (ETLs) Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3/i1/i2 devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create For Infinet systems always refer to Infinet under the hood otherwise the creation is as the Webhelp for creating BACnet B3 Logs In theory it would be possible to create the Extended Trend Log in an ES (where there is more storage capacity), but this could introduce other timing and bandwidth issues, so it is usually best to keep the first Extended Trend Log in the AS, then extend this to a second Extended Trend Log in the ES, as shown. (the second ETL in the ES scan use smart logging in the usual way) If significant logging is required then External Log Storage should be considered. (the B3 or i1/i2 logs still need to be collected via Extended Trend Logs)    

Issue Capturing packets from Zigbee Standard Security Network shows packets marked Bad FCS or Encrypted Payload Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Room Controller Cause Zigbee Standard Security Networks implement multiple keys to encrypt data for the Zigbee Network and each device Resolution This resolution assumes you have a Zigbee adapter that can capture packets in Wireshark.   Ensure zigbee_pc_keys are available in each profile you are going to use to analyze the Zigbee packets. The file location is generally: %AppData%\Roaming\Wireshark\profiles\<Profile Name>\zigbee_pc_keys   Open Wireshark and configure the Zigbee adapter NOTE: Please substitute your adapter name if not using the TI CC2531 adapter. Open Wireshark Click the gear next to the 'TI CC2531 802.15.4 packet sniffer' Select the known channel (11-26) and click Save Click on 'TI CC2531 802.15.4 packet sniffer' to start capturing Update formatting to resolve Bad FCS packets Go to Edit -> Preferences -> Protocols Select IEEE 802.15.4 Depending on your Wireshark version, check or "TI CC24XX FCS Format" or set FCS format = "TI CC24xx metadata" Add default link key for Zigbee Alliance Go to Edit -> Preferences -> Protocols Select ZigBee Set Security Level = AES-128 Encryption, 32-bit Integrity Protection Click Edit next to Pre-configured Keys Click + and Enter Wireshark Key from below, Byte Order = Normal, and Label Enter the Zigbee Alliance Default Link Key Key = 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 Key Value = 5A6967426565416C6C69616E63653039 Remove colons (:) for entry into Wireshark ByteOrder = Normal Label = ZigbeeAlliance09 Find and add Standard Network Key Ensure you have configured the default transport key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Find Standard Network Key Look in the Info column for the Transport Key and select it Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Standard Network Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use Descriptive label because you will have Network Key per Zigbee Network, so includes Device, PAN ID, and NetworkKey, ie ASP087_12345_NetworkKey Find and add Trust Center Link Key PER device Ensure the following are configured: formatting, transport key, and Standard Network Key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Since this is per device, one can include the Network Address for the device. Example: If the network address of the device is 0x2074, the display filter would be: zbee.sec.decryption_key and zbee_nwk.addr == 0x2074 Find Trust Center Link Key per device Using the Info field, find the pair of Request Key and Transport Key. The Request Key will have Source = Device Network Address, and the Transport Key will have the Destination = Device Network Address. Click on the Transport Key packet Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Trust Center Link Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use a Descriptive label because you will have a Key per device, so includes Device, Network Address, and Trust Center Link Key, ie TH907-01_0x2074_TCLK

Issue How to add a third party LonWorks device? How to create a LonWorks device template? Why is a device template not available after import? Product Line EcoStruxure Building Operation Environment Building Operation version 1.8 and above Building Operation WorkStation Cause In order to add a third party device, need to create a device template (XIF file) for it. Device templates must be created in the server that the controller will created under. If a third party controller is going to be added to an AS-P that is associated to an ES, then the template must be created when logged into the AS-P directly. Resolution To import a device template   Log in to the SmartStruxure Server in which the device will be added underneath. In Workstation, Right mouse click on the Server and select LonWorks then import device Template. In the XIF file box, select the XIF file to import. Click Import. In the Template Name field, type a name for the template. Click OK. In the Import Device Template box, click Close. Now, this third party device template will be listed when adding a device into the LonWorks network. Note: If the device template refers to NVT or CPTs not on your system, you will be prompted to import necessary resource files. When the resource files have been imported, the device template import restarts. When finished, the device template is imported and available when creating a new device.

Issue Using Modbus TCP and Modbus Serial (EIA/TIA-485) on an AS together? Product Line EcoStruxure Building Operation. Environment AS-P Modbus TPC Modbus Serial Cause Communicating with two third party devices simultaneously. Both are using the Modbus communication protocol. One is Modbus TCP, the other Modbus Serial (EIA/TIA-485). Resolution Modbus TCP and Modbus Serial (EIA/TIA-485) can be used together on an AS-P. This configuration is supported and has been used many times.

Issue How to populate customized information on the SpaceLogic Sensor display Product Line EcoStruxure Building Operation Environment SpaceLogic Living Space Sensor Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation Workstation Cause Additional information required on how to customize information to be displayed on the SpaceLogic sensor Resolution Note: This feature may not work in controller FW V4.00.x, due to know issue Custom value text is not displayed and/or updated on the SmartX sensor device, in this case please upgrade controller firmware to V5.00.1 or higher. Before starting, make sure the Integrator Menu icon and the custom information page have been activated: The Integrator Menu icon can be configured under "SmartX Sensor Device/ Display/ Button and Scene configuration" as shown in the screenshot below: Turn on "Allow custom information page" under "SmartX Sensor Device/ Display /Advanced" tab. By doing this, the custom information page is created under the Integrator menu icon of SmartX Sensor Display:        To show how to add custom information to the custom information page of SmartX Sensor display, create a sample script program, where DI1 is a digital input and Status1 is a string output. numeric input DI1 String output Status1 If DI1 = on then Status1="running" Else Status1="not running"​   In this program, when DI1 is on, the Status1 gets the string value of “Running”, otherwise the Status1 gets the string value of “Not Running”. DI1 is bound to a Digital Value (Green Arrows) under the Application folder and Status1 is bound to the CustomValueText1 (Red Arrows) as shown below:   Open the Watch pane, under the View tab, and add Digital Value and CustomValueText1 (access it through the “SmartX Sensor Device/ Display/ Basic” tab) to it.  When the Digital Value is Active the Custom value text 1 shows “Running”. On the SmartX Sensor, navigate to the custom page through the Integrator menu icon, this will show the “Running” string. Likewise the “Not Running” string would be populated on the SmartX Sensor custom information page screen when the Digital Value is Inactive.  

Issue With the same time interval as the trend log, the traffic on the LonWorks network increases for a short period. This can be seen by a spike in the LPA log when viewing the bandwidth. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Lonworks Cause The LonWorks traffic increases with the same time interval as the trend log. Resolution To ensure we could log values in the trend log from a LonWorks device, a subscription is set up about 30 seconds before the value should be logged. After the value is logged, the subscription is removed until the next log interval. A good solution to flatten a spike caused by this issue is to stagger the times of the LonWorks trend logs. This will ensure the subscription for all the logs do not happen at the same time.

Issue When comparing values of Modbus registers within WorkStation and Modscan the values do not match. Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server. Building Operation Automation Server. Cause The third-party Modbus device does not support single register requests. Modscan was set to poll 10 registers as a group poll and giving the correct responses. The Modbus request in the Enterprise Server or Automation Server was polling individual register one at a time. This resulted in incorrect responses from the third party device Resolution Add a Modbus register group to the Server then add the Modbus points to this group. This will cause the Server to poll multiple registers in 1 request and get the correct response from the third party Modbus device.   For more information on Modbus grouping refer to the EBO Webhelp Modbus Register Groups topic

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 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. This also means a TAC Xenta I/O placed under a TAC Xenta 300/400 does not count as a  Hosted Node or Connected Product.

Issue Need to configure SMTP settings to use a Google SMTP server Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no SMTP settings configured by default Resolution Note: As of May 30, 2022 please also consult Less secure apps & your Google Account 

Issue How to decrease the amount of LonWorks network traffic by using throttling. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause EBO servers could generate a lot of communication on the LonWorks Network. Throttling could be activated to decrease the amount of traffic. Resolution To decrease the amount of LonWorks Network traffic, it is possible to activate Basic Bandwidth Throttling. The setting is found under the Advanced tab for the properties for the Lonworks Local FT-10 Interface.   Picture showing default settings.   This video will show how to activate Basic Bandwidth Throttling and what impact this could have on the amount of LonWorks Network traffic.   At the end of this session you will be able to: Set up Basic Bandwith Throttling for the LonWorks network  

Issue Need to know the maximum length of a DNS name for an EcoStruxure Building Operation server Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server Domain Name System (DNS) Cause Configure DNS names for EcoStruxure Building Operation servers and need to understand if there are any limitations Resolution Domain names (including the names of domains, hosted zones, and records) consist of a series of labels separated by dots. Each label can be up to 63 bytes long.  The total length of a domain name cannot exceed 255 bytes, including the dots. Please see the Address section of EcoStruxure BMS Server Communication for additional information. 

Issue Delete Lonworks Device Templates Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server LonWorks devices Cause Some templates are preloaded with the software; if the particular device does not have a supplied template, you can upload an XIF file. This is done by selecting File/LonWorks import/Device Template and then importing the XIF from the manufacturer. An unused Device Template causes no harm to the system; however, there may be a desire to remove a Device Template. Resolution EBO 3.x and later Device Templates can be added and deleted in all device types using the Resource Manager - Device Templates tab SBO 1.x and  EBO 2.x Device Templates cannot be directly deleted from Building Operation WorkStation, however, they can manually be deleted from the  Enterprise Server file system. When a device template is imported, you should understand if the template should be located in the Enterprise Server or an Automation Server.   If the device template is located in an Automation Server, it can only be removed by upgrading the Automation Server using the Device Administrator (you can stay with the current release). If the device template is located in an Enterprise Server, it can be removed using the following process. Locate the template path in the Building Operation database (e.g., C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.3\Enterprise Server\db\UDT\public\public\lon\devicetemplates) Note: in newer releases, the path has changed slightly, e.g., For V1.8.1: C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.8\Enterprise Server\db\UDT\pu\public\lon2\devicetemplates   Delete the two template files named Pidxxxxx, where xxxxx are the numbers or letters in parenthesis behind the device template's name visible in WorkStation. After deleting the templates, you may need to restart the Enterprise Server.

Issue Analog Producer value located in an RP-C controller cannot command light object(BACnet type: crs-lighting-output) or blind object(BACnet type: crs-blind-output) located in another RP-C's CRS expansion module. Analog Producer Value, Status flags: Fault and Reliability: communication-failure.     Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause Light and Blind objects support only two priorities (1 - Force, 2 - Normal). An error will be returned by the RP if the Priority in the Write request from the Producer Value is outside this range, ex. Priority 16. Resolution In the Analog Producer Value, set the default priority for writing to 2 (normal) or 1 (Force), as shown in below screenshot:  

Issue The extended trend log contains approximately 50% of the configured storage capacity. For example, only 250 entries are in the Trend log view even though the ETL is configured for 500 entries.   After the ETL runs long enough to fill up the 500 entry capacity, ONLY 250 entries are shown in a Trend log list view. (see below)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause An extended trend log (ETL) includes an equal number of internal entries hidden from view; these entries are overhead incurred in the operation of the ETL. For example, each time a transfer takes place, an internal entry is added. Depending on the specifics of the configuration (i.e., Maximum Transfer Interval), the percentage of internal entries for a given ETL relative to its full size varies. From EBO 3.2.3, the internal entries of an ETL are hidden, and no information is provided to give any visibility into how much storage is being used by internal entries. Resolution The solution is to increase the size of the ETL to ensure there is enough storage capacity for data and overhead. Typically, the size must be doubled (in this case, 1000) in the particular ETL to make sure 500 entries of data can be stored.  Although these transfer events are hidden, it is possible to identify these events by adding the Sequence number column in the trend log list.  It is also possible to decrease the overhead amount stored in the ETL by increasing the "Maximum transfer interval" in the ETL properties, as shown in the screenshots.  Here it can be seen that by increasing the Maximum transfer interval to 1 hour for an interval log of 5 minutes that ONLY 1 'overhead' record (sequence # 565) is added per 10 entries.   Using this or a similar setting will allow to reduce the storage requirement of the ETL.

Issue When a Zigbee device is imported to EBO there is a lot of different configuration settings for the device, like the below settings for the Wiser Radiator Thermostat: How do I know what the different settings do? Do we have any documentation explaining that?  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RPC) Cause The different objects under the Zigbee device like "Thermostat" and "Power Configuration" is coming from something called clusters and a cluster is defined in the "Zigbee Cluster Library Specification". For example the "Remote sensing" attribute for the "Thermostat"   Look like this in the "Zigbee Cluster Library Specification" When joining a Zigbee device it will specify what cluster it support and that information is what will be used when building the import file which is imported to EBO. Resolution EBO doesn't know anything about the functionality of the Zigbee device. Instead it gets information from the device what clusters it supports, and will make sure the correct objects and attributes for the different clusters are created in EBO so it is possible to set all configuration parameters in the device. So to know what the different settings actually do in the device please contact the manufacturer of the device.

Issue RP-C-16B-230V Transformer 24Vac output Product Line EcoStruxure Building Operation Environment SmartLogic SmartX IP Controller RPC-16B-230V Cause More details about the internal transformer power supply required. Resolution The voltage regulation of the transformer is around 15%, thus if the "230Vac supply" is towards it's upper tolerance (230Vac +10%, 253Vac) the no load voltage of the "24Vac output" can be about 30Vac. If the RPC power supply is 230Vac, then the no load voltage of the 24Vac output will be around 28Vac With the 224Vac output" half loaded, the voltage is around 26.5Vac With the "24Vac output" fully loaded the voltage is around 24Vac See SpaceLogic - Hardware Reference Guide

Issue As per RFC 4510 The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Do EBO servers support LDAP protocol? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Need to know if EBO supports LDAP protocol. Resolution EBO doesn't support LDAP protocol. EcoStruxure Windows based BMS servers (Enterprise Server/ Enterprise Central) support integerationto Windows Active directory. The Active Directory integration is not using LDAP directly, but the NetLogon service on the Windows OS that ES/EC is running on.  This connection enables inherited user account groups from the Windows Active Directory to EcoStruxure Building Operation software, and allows users to log on to WorkStation with their Windows user accounts. Refer to: Windows Active Directory User Groups and Integrating Windows Active Directory user accounts with EcoStruxure - Communities For EBO 2022 or higher, Authentication using SAML 2.0 is also supported (Edge Server, AS-P, AS-B, ES and EC) . This enables configuring WebStation to use single sign on (SSO) using Federated Authentication, refer to: Federated Authentication. SAML Authentication feature requires license.