Building Automation Knowledge Base

Issue Can more than one MS41-7153 actuator be paralleled when being driven by a MNB series controller? Environment MNB series controller Several MS41-7153 actuators controlled by a common signal. Cause Series of parallel dampers are to be controlled by the same control signal. Resolution Yes several MS41-7153 actuators can be driven by the analog output from a MNB series controller. There are two acceptable methods of providing parallel control. 1. Control the first actuator using either the voltage output or current output from the controller and cascade control from the feedback AO of one actuator into the AI of the next actuator.  The AO of the last actuator should be routed back to the controller to provide feedback confirmation of the damper operation.  In this way should any damper fail, the feedback will indicate that one (or more) of the actuators did not drive to the desired position.  Using this method there is theoretically no limit to the number of actuators that could be driven from one controller AO output.  When controlling a series of actuators in this manner, you must make sure that the power to the actuators are phased correctly, especially if using more than one transformer.   2. Alternate method for use with four or less actuators.  Up to four actuators may be driven using the 4-20 ma drive from the controller.  The 500 ohm resistor should be connected across the actuator wired closest to the controller.  When using this method, and more than two actuators are being parallel controlled, the resistance of the parallel resistor may need to be increased slightly or the drive signal may need to be increased by as much as 2.5% to make up for the parallel resistance effect of the 80 k-ohm input impedance of the actuators.

Issue Can I use a uninterruptible power supply for controllers? UPS Environment site requiring constant power supply or unstable power from grid and need to take into account power supplies Cause Can I use the CX99-PSU-BATT for an ACX5720 controller? If not, then what can I use if the customer wants a UPS for each controller. Should I use a big UPS for the system and supply the controllers from it?   Resolution The CX99-PSU-BATT is 70VA 120/240VAC and really designed for the CX9900 PSU. It is suggested to get one of our APC UPS and run the proper voltage transformer to the ACX5720. The ACX 57xx series is rated with a 24VAC 90VA or 12-28VDC 50W on the power supply which I recommend due to devices which connect to this controller and require power. i.e. door readers UPS or uninterruptible power supplies are available from APC by Schneider Electric.  Background The power drawn by computing equipment is expressed in Watts or Volt-Amps (VA). The power in Watts is the real power drawn by the equipment. Volt-Amps is called the "apparent power" and is the product of the voltage applied to the equipment times the current drawn by the equipment. Both Watt and VA ratings have a use and purpose. The Watt rating determines the actual power purchased from the utility company and the heat loading generated by the equipment. The VA rating is used for sizing wiring and circuit breakers. The VA and Watt ratings for some types of electrical loads, like incandescent light bulbs, are identical. However, for computer equipment the Watt and VA ratings can differ significantly, with the VA rating always being equal to or larger than the Watt rating. The ratio of the Watt to VA rating is called the "Power Factor" and is expressed either as a number (i.e. 0.7) or a percentage (i.e. 70%). The power rating of the UPS UPS have both Watt ratings and VA ratings. Neither the Watt nor the VA rating of a UPS may be exceeded. In most cases, UPS manufacturers only publish the VA rating of the UPS. However, it is a standard in the industry that the Watt rating is approximately 60% of the VA rating, this being the typical power factor of common loads. Therefore, it is safe to assume that the Watt rating of the UPS is 60% of the published VA rating. How to avoid sizing errors Using APC sizing guidelines or and APC Configuration can help avoid these problems, as the load power values are verified. Equipment nameplate ratings are often in VA, which makes it difficult to know the Watt ratings. If using equipment nameplate ratings for sizing, a user might configure a system which appears to be correctly sized based on VA ratings but actually exceeds the UPS Watt rating. By sizing the VA rating of a load to be no greater than 60% of the VA rating of the UPS, it is impossible to exceed the Watt rating of the UPS. Therefore, unless you have high certainty of the Watt ratings of the loads, the safest approach is to keep the sum of the load nameplate ratings below 60% of the UPS VA rating. Note that this conservative sizing approach will typically give rise to an oversized UPS and a larger run time than expected. If optimization of the system and an accurate run time are required, use APC sizing and Worldwide Web configuration tools.  

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 How does one get a clean database for the Enterprise Server or Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need for clean database either for testing or start from scratch.  Resolution Stop Enterprise Server or Enterprise Central using Software Administrator Go to the location of your database using Windows Explorer. In EBO V3.2 or higher, software administrator has a shortcut button for the databse folder. For this example it is C:/ProgramData/Schneider Electric EcoStruxure/Building Operation 2.0/Enterprise Server/db Delete the following folders if (some might not exist): Configuration, Historical, Persistent, System, UDT Start Enteprise Server or Enterprise Central using Software Administrator, the system will create a new folders and files as needed. Note: Restoring a different database over the current database does not require the clean database state. Using the backup and restore procedure allows you to switch databases.

Issue Device Administrator requires CRT certificate file to add a certificate to CA Certificates. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause If you rename the filetype from .pem to .crt and add via Device Administrator, the Automation Server will still present the following alarm: Alarm Text: System alarm: unable to get local issuer certificate System alarm ID: Invalid certificate for https communications   NOTE: The alarm will be known to have originated from the Automation Server because, in the Source field, the Automation Server will be the root, and the server it is connecting to will be the last. Example: /AS01/System/Communication/Server Certificate/To/ES01 AS01 - Automation Server with the CA Certificate issue ES01 - the EBO server which is was connected as client, which generated the alarm Resolution Reference this article to find OpenSSL installed: OpenSSL installed with EBO Use and modify this command with your filenames:  openssl x509 -in ca.pem -out ca.crt​ Add the .crt certificate file via Device Administator's CA Certificates tab. Reference: CA Certificate Tab (WebHelp)

Issue Receive Error: "Unexpected file format" when attempting to open Graphic Page Environment I/NET Seven 2.41 graphic pages Cause When creating, modifying and saving graphics in revision 2.41 and then attempting to open these graphic pages in previous versions of I/NET this error "unexpected file format" is presented. Resolution This issue has been rectified in 2.41A and above. I/NET Software are available for licensed Partners to download on The Exchange Download Center.

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.

Issue The toolbar icons in PCT 2.0 are jumbled. They seems to be stacked on top of each other, making it hard to use the toolbar. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Issue with the font used by PCT Resolution Follow these steps to resolve the problem: In Windows, navigate to Settings, then Font Settings, and search for "Material Icons". Select Material Icons, then choose Uninstall. Confirm by clicking Uninstall. Close all browser windows used to access PCT, then reopen and browse to PCT again. The toolbar icons should now display correctly.

Issue When saving a Plain English program, the program disables on the following error. Array index too large or too small. Environment Plain English Manual Log Array Error Cause Program is attempting to store a value in a numerics manual array slot when the array does not exist. Resolution Determine how many array slots the program intends to use when storing values in this numeric. On the Logs page of the numeric editor make sure the size matches the number of array values being used by the program.

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

Issue Replacement for Satchwell DDT0001 Duct Temperature Sensor.  Environment Satchwell Sensor DDT DDT0001 Cause Obsolescence of Satchwell DDT0001 Duct Temperature Sensor. Resolution Replace Satchwell DDT0001 Duct Temperature Sensor with Schneider Electric STD660 Duct Temperature Sensor. The Schneider Electric STD660 provides the same functionality as the Satchwell DDT0001, differing only in its appearance, dimensions and terminal identification. The Schneider Electric STD660 Terminals are not polarised.    

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 Create a report of all expired cards Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause A custom report and its configuration are needed to find all expired cards at the site Resolution This video demonstrates how to create and configure a report to find all expired cards in a system   Create a User Report: 1. In Security Expert Client, go to Reports|Setup|User and Add a new (or use an existing) report. 2. Configure the desired Report Type and Sorting 3. Go to the Columns tab, click the Add button and select Columns.  Make sure to have: -Expiration date of badge AND/OR Expiry date 4. Save your report   Please note: The "Expiration date of badge" column pulls the date from Users|Users|Extended Tab|Expiration date of badge. The "Expiry date" column pulls the date from Users|Users|General Tab|User expiry date/time section's End date.   Customize the User Report's layout: 1. Go to Reports|Setup|User| General Tab| Default user report filter and click the "Edit in report view" button 2. Right-click "Expiration date of badge" (or "Expiry date") column and select the Filter Editor 3. Change the "And" condition (in red) to "Or" 4. Change Equals to DateTime Operators: Is Yesterday 5. Click "+" sign in green circle to a line and repeat changes 5 more times for the following: - Is Earlier This Week - Is Last Week - Is Earlier this Month - Is Earlier This Year - Is Prior This Year 6. Click Save Report Layout

Issue How to properly configure Time Zone and UTC Offset settings in Cyberstations and controllers. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Controllers Cause There are a number of locations for time configuration settings, creating uncertainty as to what needs to be set, and where, to maintain the correct time in all devices. Resolution How to sync controller time with WS time with Server time. Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and regional settings are correct. [This has no effect on time synchronization but does have an effect on what time alarms and events are written to the database as well as when alarms will be delivered to Cyberstations] Confirm the SQL Server PC time zone (GMT settings) and regional settings are correct. [same as 1 above] In Continuum, the Workstations Device object's Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes.) In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note1: To synchronize controller time to Workstations time a program needs to be created in one WS that sets the Date object of the Netcontroller (IP level controller) with the lowest ACCnet ID. This controller will then push any time changes out to all other IP level controllers and down to its subnet controllers (i2’s or b3’s). See Time sync controllers to workstations for details on this. Note2: At 38 minutes past the hour the Netcontroller will push its time down to its subnet (aka Field Bus) controllers. Note3: When time is set in the Netcontroller with a reload of the controller, the UTC settings of the WS doing the reload, and the Network folder the controller is in, are accounted for and the controllers time is set with these UTC settings taken into account. When time is set with a PE program using the WS Date object, this does not take into account the UTC settings of the various locations and just sets the controller Date object to the exact value of the WS Date object. If the controller is in a different time zone than the WS setting its time, then it will now have the wrong time in it. To compensate for this, it is suggested that time offsets must be added to the Time Sync program to accommodate those networks in a different time zone than the WS. Other UTC setting locations and what these settings effect IP level BACnet Device UTC Offset The UTC offset value on the Time tab of the BACnet Device object is only used when the BACnet time synchronization method is being used to set time. This setting then follows the BACnet specification where it needs to be the negative value of the GMT setting. For example, if the BACnet device is in the GMT+10 time zone, then set this offset to -(10*60) = -600. Note4: If using the PE program method, the UTC offset value on the Time tab of the BACnet Device object does not change how time is set in the controllers. However, if the UTC offset value on the Time tab of the BACnet Device object is changed, it will change the current time of the controller to coincide with the new time zone until the time is set again in the controller, or the UTC offset value is removed. UTC offset in controller configuration Time Settings webpage This doesn’t change how the time of the controller is set. It is used to set the time of sent email messages when using the SMTP option on this controller.

Issue Time Zone and DST when syncing time to an NTP server Time differs from NTP server with x hours. DST is not following NTP server time. Environment TAC Xenta 701, TAC Xenta 711, TAC Xenta 731,TAC Xenta721, TAC Xenta 511, TAC Xenta 527 NTP server Cause NTP provides UTC, no information about time zones or daylight savings ( DST)  is sent. So if you don't set the correct time Zone and DT settings the time will be set to UTC time in the device. Resolution Log in to Xenta server Go to  Configuration- Time- Regional Settings Set correct information

Issue Pins 4 through 7 across the top of the Automation Server are labeled as "Operator Panel" although there is not an Operator Panel part available. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Cause There is no explanation of what the AS Operator Panel contacts are for? On front of AS:  Operator Panel Terminals Term 4 RET Internally connected to ground Term 5 10V 10 VDC max. 120 mA Term 6 Tx/Rx+ RS-485 communication Term 7 Tx/Rx- RS-485 communication Resolution At one time there were plans to create an Operator Panel so terminals were reserved on the Automation Server for local OP connection, however, these plans were not implemented. The next generation Automation Server Premium (AS-P) does not have the Operator Panel label, and today most operators use Webstation or Workstation.

Issue The Insight Sensor and Multi Sensor Ambient Light Sensor require calibration before they can be effectively used. Product Line EcoStruxure Building Operation. Environment Insight Sensor. Multi Sensor Cause When setting up a new Insight Sensor or Multi Sensor device, the default settings for Gain and offset may result in inaccurate readings. Calibration is necessary to ensure accurate data collection based on the specific installation area. Resolution To perform the calibration, the following two tasks need to be carried out manually: Calibrate the Light Sensor: Conduct the calibration process in an environment without any daylight for optimal results. Set the light to 100%. Measure the lux level at the reference point using a lux meter. Adjust the gain settings on the sensor to match the measured lux level. Linearize the Feedback Signal: In some cases, lights may not provide a linear feedback (lux level) as the output increases. To compensate for this non-linearity, the signal from the controller is linearized before being sent to the output. During the optimization phase, the controller incrementally increases the output in 10% steps, measuring the adjacent lux levels for each step. The maximum lux supplement is calculated by subtracting the lux level at 100% output from the lux level at 0% output. After the optimization phase, breakpoints are determined and verified by re-running the test. If the results fall within the maximum difference limit compared to a linear signal, the calibration test is considered valid. Remember, performing the calibration process without any daylight present will yield the best results.  

Issue SPP920 Datasheet, Technical Information and Installation Instructions Product Line Field Device Environment SPP920 Differential Pressure Switch Cause No information available for the SPP920. The Sensor catalogue says it is supported by Huba. Resolution Either click link www.hubacontrol.com and search for 630. or the Technical information can be downloaded here. Installation Instructions can be downloaded here. Mechanical connections are: P1 = High Pressure (discharge/flow), P2 = Low Pressure (suction/vacuum) All of the various pressure range options come with the following options: - EPDM diaphram material - Brass Case - Spec Cover PG9 - IP65 Rating - Bracket Type A

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue In BAS and Sigma, what batteries and PSU cards can be used in a x96 controller.? Product Line Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue What features are included in Building Operation evaluation (demo) licenses? Product Line EcoStruxure Building Operation Environment Building Operation evaluation license Cause The features included in evaluation licenses are not shown in the documentation. Resolution License Administrator (Software Evaluation License) After adding the evaluation license in License Administrator,   Click on the "Diagnostics" Tab. Click on "Refresh the list". Local licenses list generates. Example of generated list: Local licenses: -------------------------------------------------------------------- Trust Flags: FULLY TRUSTED Fulfillment Type: TRIAL Status: ENABLED Fulfillment ID: LOCAL_TRIAL_FID_498 Activation ID: SC_57LRIHRFBOXC28SGYTPKCH98WIRKMWE Product ID: NAME=EcoStruxure Building Operation Demo License;VERSION=5.0 Suite ID: NONE Expiration date: 01-Feb-2024 Concurrent: 0 Concurrent overdraft: 0 Hybrid: 0 Hybrid overdraft: 0 Activatable: 1 Activatable overdraft: 0 Repairs: 0 Feature line(s): server.mssql (Version 5.0) client.zoning (Version 5.0) client.dashboard (Version 5.0) server.ec.auth.saml (Version 5.0) server.ws.generic.consume (Version 5.0) server.dig.signed.docs (Version 5.0) server.alarms.snmp (Version 5.0) server.ec.es (Version 5.0) server.device.es (Version 5.0) server.ws.ews.history (Version 5.0) Sigma.Server (Version 4) server.mqtt.rw (Version 5.0) graphdb.base (Version 1.0) server.esignature (Version 5.0) server.enterprise.base (Version 5.0) server.ws.ews.consume (Version 5.0) client.cad.import.tool (Version 5.0) smartdriver.license (Version 5.0) server.timescale (Version 5.0) client.script (Version 5.0) server.es.as (Version 5.0) client.graphiceditor (Version 5.0) server.device.as (Version 5.0) server.ws.ews.serve (Version 5.0) server.es.auth.saml (Version 5.0) server.enterprise.central (Version 5.0) client.functionblock.view (Version 5.0) client.station (Version 5.0)   Refer to the Webhelp EcoStruxure Building Operation Software Feature License String Description topic for an explanation of the license feature strings. Device Administrator (Embedded Evaluation License) After adding the evaluation license to the Device Administrator (see the article How to activate a demo license on an Automation Server at EBO 2022) follow the steps to view the available features: Click on the Entitlements. Click on Product Licenses. - The individual features are then shown as column headings The best way to see all the features available is to right-click on the license name under Product Name and choose Add/Remove columns.   A Select columns popup is then shown, and the available features are much easier to read.