Building Automation Knowledge Base

Issue Where can I find help on TGML scripting and advanced features? Which javascript functions are supported and how do these impact performance. Product Line TAC Vista Environment TAC Vista TGML graphics editor 5.1.7 Cause More advanced graphics often require scripting and the engineer needs to know which functions are supported. Resolution In the TGML editor under Help there is a section called TGML Format Specification. Details of scripting methods as well as examples can be found here. Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue Can I take a 26 bit Wiegand Hexadecimal Card Number format and find out what the Facility Code and Card Number are? Product Line TAC INET Environment 26 bit Wiegand Hexadecimal Card Cause Need to discover the Facility Code and Card Numbers Resolution Yes you can do this. This document will show you the process on how to determine these values: 26 Bit Wiegand Format Also see Conversion from I/NET hexadecimal code to Continuum Facility/Card Number for an Excel utility to perform this conversion.

Issue How can Continuum be setup to read the 32 bit serial number from a Mifare smart card for use in access control? Product Line Andover Continuum Environment Using iClass serial number readers: R10, R15, R30, R40, RK40 Custom Wiegand, AccessFormat array Custom Format Cause Mifare smart cards that have been provided and programmed by others may not have the keys available to allow a reader to access the data on the card. Without sending the cards away for re-programming how can the card still be used for access control. Resolution The HID iClass readers (R10, R15, R30, R40, RK40) have the ability to read the 32 bit serial number from a Mifare Smart card. These readers will output a single 32 bit Wiegand string representing the card serial number. To use this on Continuum: Create a numeric point called "AccessFormat" and define it as a manual array with 19 entries. Create a Plain English program in the controller to fill up the array with values as per the Mifare Serial Number spreadsheet. In the door configuration select "Custom Format" and ensure one of the 4 site codes is set to 0. Swipe the card at the reader and open a list view of Events, this will show the card number as the serial number from the card. Create a new Person with card type Custom Wiegand, Site code 0 and set the Card number to the serial number as read in the list view. This may be a 9 or 10 digit number. Notes: If using card numbers in Plain English Programs or displaying in Pinpoint Graphics, you will be restricted to using a maximum of 6 digit numbers (maximum card number being 999,999). See Loss of resolution on metering points when the number is 7 digits or longer for details on this restriction. The old style Personnel editor will not allow the entry of site codes of 0. Use Personnel Manager or set attributes in List Views of Personnel.

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 Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

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 What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

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 AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.

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 Configuring the Workplace Tech encrypted LON Tunnel Client  Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.10.4 Click for WorkPlace Tech 5.9.4 information I/A Series N4 Jace Cause How to handle the encrypted LON tunnel for single and multiple LON networks in the latest version of Workplace Tech, 5.10.4.  Understanding possible errors during tunneling. Resolution The following video will help us, Apply the Encrypted LON Tunnel in an N4 Jace Configure the Tunnel Client for use with multiple LON Networks on a single Jace Understand the change in workflow from Workplace Tech 5.9.4 and 5.10.4

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