Building Automation Knowledge Base

Issue A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site. The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses." Product Line EcoStruxure Building Operation Environment EBO Enterprise Server 2.X and newer EBO Workstation 2.x and newer Cause The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.  Resolution In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing. Troubleshooting Steps: Restart the Enterprise Server. Restart the License Server (if on a different machine as the ES). If required, restart the ES again. Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step. If these steps have not resolved the issue, then open a support case with your local country support organization.  For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement. 

Issue How to add Web Service and create Simple XML Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add XML files and how to add to a project or site How to create values from the XML Files added How to make a graphic that uses the values from XML Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: Are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Weather for a particular location data using Simple XML: Select New > Interface > Web Service > Simple XML Specify the URL for this data (to find the weather for your area, Google XML data Make changes to polling, alarm, retry interval Choose Create Now you can Create a value from that Simple XML Web Service by highlighting and select New > Value > and type of value. Select Analog for temperature, String Value for wind direction and so forth. One can add as many of the values as desired. The Simple XML List View would look like the below screen capture. Lastly for Simple XML Web Service a graphic is created and the values which come from the XML Web Service are place on the page. Also check out the SmartStruxure - Web Services - Simple XML Interface Quick-Help video on the Exchange.

Issue BACnet MSTP Wireshark capture Product Line EcoStruxure Building Operation Environment Schneider Electric StruxureWare Building Operation AS using MSTP for BACnet Cause Example of Wireshark capture and WriteProperty in MSTP    Resolution Using Wireshark, a bacapp.confirmed_service == 15 filter is applied which shows only BACnet WriteProperty packets Below is a screenshot of the Wireshark screen after applying the filter. I have Requests (REQ) and Acknowledgements (ACK) shown: Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be 0.00 Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be a value of 100.00 Filters which may be useful: Capture Filters   udp port 47808 BACnet/IP packets on UDP port 47808 udp port 47808 or udp port 47809 BACnet/IP packets on UDP port 47808 or 47809 Display Filters   bvlc || bacnet || bacapp all BACnet packets bacnet BACnet NPDU packets bacnet.mesgtyp BACnet Network Layer (router) packets bvlc BACnet/IP packets bvlc.function == 0x0b BACnet/IP Broadcast packets bacapp APDU packets bacapp.confirmed_service == 12 readProperty packets bacapp.confirmed_service==14 readPropertyMultiple bacapp.confirmed_service == 15 writeProperty packets bacapp.confirmed_service==16 writePropertyMultiple bacapp.confirmed_service==1 confirmedCOVNotification bacapp.confirmed_service==5 subscibeCOV bacapp.unconfirmed_service == 0 I-Am packets bacapp.unconfirmed_service == 8 WhoIs packets bacapp.unconfirmed_service == 2 unconfirmedCOVNotification packets bacapp.unconfirmed_service==3 unconfirmedEventNotification bacapp.unconfirmed_service==6 timeSynchronization     mstp.frame_type>2 exclude all token passing mstp.frame_type>127 view all proprietary traffic mstp.frame_type==0 only token passing mstp.frame_type==1 only poll for master mstp.frame_type==2 only poll for master responses bacapp.instance_number==[BACnet ID] all traffic from/to a specific ID mstp.dst==[MAC address] all traffic to a specific MSTP address mstp.src==[MAC address] all traffic from a specific MSTP address ip.dst==[IP address] all traffic to a specific IP address ip.src==[IP address] all traffic from a specific IP address      || (between filters) combines above filters (or)  && (between filters) combines above filters (and)   Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com  

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

Issue Steps to backup within StruxureWare/EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a StruxureWare Building Operation server backup set. Resolution Concerning the backup and comparing SQL to the proprietary database that StruxureWare/EcoStruxure creates begs the question, are these backup complete? StruxureWare freezes the database while a backup is in progress in different ways. For configuration changes, StruxureWare Building Operation queues up the changes until the backup completes. For historical data, StruxureWare Building Operation buffers the data based on the limits of the buffer size. A stop of the ES is not necessary, nor is a stop of an AS. Because of this freeze and buffering, the data is put into that backup folder referenced in the pdf you sent. Three rules to remember: Restores of backups must be same software revision Do not rename the backup set A StruxureWare/EcoStruxure Building Operation backup should not be renamed after it has been created. When creating a backup, give the appropriate prefix to the standard name format.     The backup file will be shown as below. Should the backup name need to changed, then either create a new backup, or, zip up the backup using the new name.   Backups default to every Sunday morning 1:00am Here is the procedure for backing up an AS or ES: In Workstation, in the System Tree pane, select an Automation Server (AS) or Enterprise Server (ES) On the Actions menu, click Backup. This opens the Backup Options window In the Include column, select the servers that you want to include in the backup In the Backup content column, select the type of data you want to backup for each server: Select All Data to back up both the historical and configuration databases. This combined option protects the configuration, historical data, and custom object type data for a specified date and time Select Configuration only to back up the configuration database and custom object type data. This data option protects the configuration data for a specified date and time In the Backup set description column, type a brief description up to 255 characters to help identify the content of the backup Click Backup Verify that each backup succeeded and click Close Backup Files of ES: The backup data files are stored in the C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Login to AS from WorkStation and navigate to System > Backup and Restore > Backup sets> Local. Then Right-click on the backup file and Save To... (then select a folder on your HDD) Note: Let this not be confused with the 'Starting a Project Tutorial [101248].pdf' in section 5.1 page 44, where it describes the user simply doing a raw copy of the database folder from within Windows Explorer. This can be mistaken with the orderly backup that uses the inbuilt StruxureWare backup facility. This copy procedure described has no chance to freeze the database. The user can just do it at any random time and StruxureWare has no idea that the copy has been made. A sample database should be created using the Backup/Restore functions of the system, not by just doing a raw folder copy as the server may be in the middle of transactions to various files in that folder. A copy of this folder could be used, but only while the SE.EnterpriseServer.exe process has been stopped. However, it is recommend using the system’s backup facility to accomplish this (Not all items are backed up such as Alarm data. The Backup/Restore help section of StruxureWare Building Operation Guide discusses what is and isn’t backed up).

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 Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch StruxureWare Software Administrator; Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare Software Administrator. Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric\StruxureWare X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing StruxureWare, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db). Launch StruxureWare Software Administrator again, click Start Service, and then OK. Launch StruxureWare WorkStation and log into the enterprise server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the enterprise server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the automation server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue When attempting to trust a self signed certificate, the option to permanently trust the certificate is not enabled. When viewing the certificate, you see the message "Bad server certificate" in the field "Issued by" Refer to WebHelp Article 10326 for further information about certificate types Product Line EcoStruxure Building Operation Environment Certificates Cause There can be various reasons why a certificate can not be trusted, and many or these are described in SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS. In this specific case where you see the message "Bad server certificate", the cause is that the certificate is not deemed trustworthy. First of all, you need to check what the reason behind the certificate being flagged as bad is. This is easiest done by examining the "CRL Distribution Points" property of the certificate, to determine which service is checking or affecting the certificate. In this example, we can see that it is ZScaler (a proxy server provider) is listed, so the reason why the certificate is deemed as bad, is most likely because the certificate is self signed, and that is not accepted by the company policy. If disabling the usage of a proxy server on the PC you are working on allows you to trust the certificate, you can confirm that it is an issue with the proxy server not allowing the self signed certificate. For more information about how e.g. ZScaler handles certificates, refer to the How does ZScaler protect SSL traffic article. Resolution Either reconfigure the proxy to allow the self signed certificate, or (the better option) get a proper CA signed certificate. For more information about preparing and importing a CA signed certificate, refer to Preparing and importing a signed CA certificate.

Issue Creating binding templates. Product Line EcoStruxure Building Operation Environment Binding templates for Script and Function block programs. Binding template examples:  Type Binding Template Examples Path Matching Binding Templates and Syntax Path Matching Binding Template Examples  Cause 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. 2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. 3 - Binding Template Types examples Resolution 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. Under the system folder of the AS or ES there is a folder called "Binding Templates". In here you can create custom templates by right clicking and selecting "New", "Binding Template". To create a generic template that will bind both inputs, outputs, values and other object types follow these steps: Press Next and the following screen appears: Select All Types and press Next: Click twice on the Add Rule icon (Green +) then enter the three rules as follows: Press create and the new IO Binding template will be created.  If you have used a common naming convention in your points and within the programs, you will be able to use this template to bind all the points and values to your programs. Drag the AS across to the IO Binding template (as below) and it will match all of the point names and use Requested value attribute for the output points. This example shows 2 IO Binding templates, as one was created at the AS level and another at the ES level. Only 1 is actually required to provide this functionality. You can subsequently edit the binding template and it will show as follows:   2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. It is common for a system to consist of many controllers that have been created from the same import file. This will mean that there are many instances of the same names being used, but this is not an issue until a graphic containing several controllers are to be bound. Create a "Path Matching Binding Template" as shown above and configure as shown in the following screen shot. Notice that the Binding candidate has /Application/ between the "Unit" and "Point" to match the tree structure.        The screen shot below shows the site system tree structure, with part of the graphic binding page. Note that for the binding template to work, the bind names used in the graphic must be unique. eg. L6W1_CHB_006 (Unit) and ReturnAirTemp (Point).     For an Export of this template, click Binding Template Export 2013-08-15 083240.zip. 3 - Binding Template Types examples see the Online Help. An additional resource is the Exchange Community in particular the following Knowledge Reinforcement Session Also check out the SmartStruxure-Binding Templates-Lesson 1-7 Quick-Help video on the Exchange.

Issue A repository of objects available somewhere for sharing TGML graphics such as Smart Widgets (Power Objects), Camera, Door, Lighting, Reader, override, etc. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Smart Widgets. Cause Graphical interface of power object, such as a Power Meter, Power Objects, Camera, Door, Lighting, Reader, override, etc. for viewing in TGML graphics mode. Resolution These objects should appear on the StruxureWare Building Operation Community Site. However, there is an ongoing centralized effort in producing more objects in a uniform way and the developers have not yet seen the devices they developed objects for. One of these developers has made objects for these devices: PM710, PM9, PM800, ION6200, Compact NSX. There are standardized updates in progress for these and also for the PM210. The community is the best place to get these. PSS does not have a repository of these type of objects.  

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.

Issue License needs to be activated or repaired but there is no Internet access on the computer that the license is being hosted on. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator  Cause There is an inability to move the computer to a location with Internet access, activate or repair the license, then move it  back to the site. In other situations the IT Department is so strict that they will not allow internet access on the computer just for licensing activation. Resolution SBO Offline Activation Tool There SBO Offline Activation tool posted on the Community outlines the step by step process to perform an offline license activation. It can be accessed here: SBO Offline Activation Tool. Click on "Instruction and Help" in the tool for the step by step process and other helpful videos/charts.  SBO Offline License Repair The same SBO Offline Activation tool used for activation can also be used to repair an offline license. Download the tool here: SBO Offline Activation Tool. After launching the offline tool, click on the "Special Operations" menu and click on Repair License.  If this does not repair the license, then please contact PSS for further troubleshooting assistance. 

Issue When PC based firewall's are used, some configuration in the license system and in the firewall are required to be made. In some cases, the error below when logging into Workstation appears: License server machine is down or not responding (Error code -15 or -96) Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The TAC license (taclic) vendor daemon by default uses a random port each time it's started. This setting makes it difficult to handle in a firewall. Also the various EcoStruxure programs using the license system needs to be allowed in the firewall, as well as the ports used by the license system. Here is a simple explanation of how the license request from a client is made. Resolution Make sure there is a valid license installed on the license server. For more information read Requested license not available for Enterprise Server, Workstation or editors The easiest way to configure Windows firewall, is to run the SBO Firewall Config tool on all PC's having EcoStruxure software installed. For any questions regarding the use of this tool please contact the developer, details in the tool. In order to manually make the configuration follow the steps below. For more information on how to create Windows firewall rules, read Creating Inbound and Outbound Windows Firewall Rules.   On the server PC Make the port used by the vendor daemon fixed. Follow Define the port used by the taclic vendor daemon guide to do that. On the PC having the license server installed, open the following TCP ports in the firewall both inbound and outbound.  80 443 4444 2170 27000 through 27009 (If a user defined defined port has been used other than 2170 for the vendor daemon then use that instead of 2170)   On the client PC On the PC having EcoStruxure software installed using the license server on a remote PC, make these exceptions in the firewall: Allow ports TCP 80, 443, 4444, 2170 and TCP 27000 through 27009 both inbound and outbound. (If you defined a port other than 2170 for the vendor daemon then use that instead of 2170) Allow the following programs: SE.Graphics.Editor.exe SE.SBO.Script.Editor.Proxy.exe SE.SBO.ScriptEditor.exe SE.SBO.WorkStation.exe SE.WorkStation.IA.WptEd.exe tam32.exe They are typically located here: On 32 bit OS: C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.X\WorkStation On 64 bit OS: C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation 1.X\WorkStation

Issue What specification should BACnet MS/TP cable meet? Product Line Andover Continuum, EcoStruxure Building Operation Environment MS/TP BACnet devices Cause Often an incorrect cable type is used when wiring MS/TP devices causing unreliable communications. Resolution The BACnet Controller Technical Reference defines the following cable specification for a MS/TP cable: RS-485 Cable Specifications: Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Ohms Velocity of propagation: 78% Capacitance: <12.5 pF/ft (~ 41pF/M) between conductors and < 22 pF/ft (~72pF/M) between the conductor connected to ground and the next conductor. An example of a cable that meets this specification is Belden 3105A. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue There have been questions about how the new EcoStruxure Building Operation 2.0 demo license works with the new scalable pricing structure. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and up All previous builds of SBO 1.9 and below Cause Understanding what the EcoStruxure Building Operation evaluation license will allow to function in the newer versions of the product.  Resolution The EcoStruxure Building Operation Evaluation License is a temporary license used when a database is being brought online before the permanent license has been deployed or on engineering laptops. All authorized Schneider Electric employees and partners can download the file from the Exchange Extranet. The file is updated every quarter as each one has an expiration date. The functionality of the demo license has not changed in version 2.0 and newer. This license file will still allow functionality and engineering of a database to take place as long as the file is valid. The only difference is the new warning banner that will be present until permanent licenses are installed.  Note: With the new scalable pricing starting in version 2.0, once the evaluation license is removed from the site, a license is needed for each Automation Server attached to the Enterprise Server.  More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info. 

Issue After upgrading from EcoStruxure Energy Expert (formerly Power Manager) from version 1.0 to 1.x or newer, the licensing no longer works. Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Energy Expert (formerly Power Manager) License Administrator Power Monitoring Expert Cause There can be some confusion on what licenses are required to run Energy Expert. There are also differences between version 1.0 and 1.x or newer licensing.  Resolution EcoStruxure Energy Expert License In order to use Energy Expert, an Energy Expert license is needed to be purchased before the previous 90-day trail license expires.  The EcoStruxure temporary license (evaluation) is only for EcoStruxure Building Operation software and does not include Energy Expert   It is important to remember that EcoStruxure Building Operation licenses are needed to work along side Energy Expert (e.g. Workstation, Enterprise Server, etc). The EcoStruxure Building Operation licenses need to be activated separately.  How to activate, release and/or transfer a license in EcoStruxure.   Energy Expert Version 2 and 3 Licensing and Upgrading If upgrading from a previous Power Manager 1.x site to Energy Expert 2.x or 3.x a new license(s) will be required. In order to obtain your new license(s), please follow the procedure found in TPA-EBO-19-0001.00 - EcoStruxure Energy Expert v2.0 License Upgrade. (Full support ends 2022 and limited support ends 2024) Energy Expert Part numbers and Licensing The part numbers for version 1.x or newer are listed below. PSWPMNCZZSPEZZ -  Base Energy Expert license PSWDENCZZNPEZZ -  PME license entry range PSWDMNCZZNPEZZ - PME license mid range  PSWSANCZZSPEZZ -  Standard PME. license For a full list of both current date and obsolete part numbers please download the following spreadsheet https://ecoxpert.se.com/pme-digital-power-launch)   Activating a License Full guidance for activation of your licenses can be found on Page 55 of the Energy Expert 3.0 Solution Guide The Energy Expert 3.0 installer and documentation, can also be found here EE 3.0

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as the Deploy Power Manager for SmartStruxure Solution in a Day document.  Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange. General Always install the EcoStruxure Energy Expert software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator.  Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to EE. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process.  See StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills. The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.   Selecting Between Architecture 1 and 2 The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement. Most of the Schneider Electric meters and circuit breakers are fully supported by EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) It is recommended to use interval trend logs to log the raw data coming in from the meters.  The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. EE Dashboards and Reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into EcoStruxure Energy Expert (EE) as it can be calculated later based off of the 15 minute trend log value.  If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to EE to avoid the lagging between Extended Trendlogs and Trendlogs.    ETL StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs. For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with your web server address and port as needed) in the settings. For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True. The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name.    The Target Measurement field is very important to set correctly as it will not bring the data over to EE correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manager for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use. 

Issue For EBO Active Directory (Windows Domain) integration, do EBO support usage of "nested groups"?. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause EBO are using Windows API and ask if the user is a member of a certain group.  Resolution Windows API should respond “yes” if the user is part of a group that is part of another group, which is configured in EBO. So this is up to how the Windows AD responds to the Windows API and not on the EBO side.   For more information, please see Integrating Windows Active Directory user accounts with EcoStruxure