Building Automation Knowledge Base

Issue How to register a BACnet device as a Foreign Device with ES/AS Product Line EcoStruxure Building Operation Environment ES AS WS BACnet Cause Documentation Resolution Before a device can register with ES/AS, the ES/AS has to be configured to assume the BBMD role by creating the BBMD under the IP Network of the BACnet interface. You can then examine the BDT00001 entry for the IP address and port your foreign devices will use to register. Configure the device to register as a foreign device with the ES/AS, in this example we have configured a bCX4040 using its configuration web page. (Note, in order to configure a bCX as a foreing device you must first disable the BBMD option in the bCX) If the device registration was successful, the device's IP address will appear in the foreign device table (FDT) of the ES/AS    

Issue Connecting to an ES that is on another machine through WorkStation and trying to force a BACnet input or output point located on a b3, connected to an AS-P, causes WorkStation to freeze. The only way to get out of freeze is by ending the system task in Windows.   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v2.0.2.x Building Operation Automation Server v2.0.2.x Building Operation Workstation v2.0.2.x Continuum b3xxx Controller any version Cause EBO v2.0.2.x has communication issues when connecting to an ES that is not on the machine you have WorkStation on.  Resolution Upgrading to 2.0.3.45 or later will resolve this

Issue Every item shown in the Objects window of the TGML editor can be considered a Node. In the figure shown below, this relatively simple TGML page has 14 nodes. Nodes are hierarchical with parent and children nodes. One important concept when scripting in TGML is finding the desired node. Examples of this are: Changing the color of a rectangle when a bound signal is offline Writing a new value to a text box every time the database value updates Opening a new page when the user left clicks on a component Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation TAC Vista TGML Graphics Editor Cause Within a script, there are two functions that will pinpoint a specific node, but have very different applications. These are: getTarget() getCurrentTarget() An example function of how to use these functions is: function click(evt){ target = evt.getTarget(); } Resolution getTarget() - returns where an event is coming from getCurrentTarget() - returns the parent of the script Both examples below chart the differences between the two functions using the screen capture below. If the bind object in the figure above changes its value, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Bind Component B Bind Rectangle C Bind Bind If the user clicks on the rectangle in the figure above, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Rectangle Component B Rectangle Rectangle C N/A N/A Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue Why do Continuum controller MAC addresses have less than 12 digits as required by IT Departments? Product Line Andover Continuum Environment ACX, bCX, CX level controllers NC2 Cause Leading zeros are removed from the MAC addresses of all Continuum controllers Resolution The MAC address is listed as the attribute "Ethernet Id" in Continuum List views. The digits do not display leading 0's, so all Continuum controller addresses start 0:40:11.... To provide the 12 digit MAC address you will need to restore the leading 0's as required by IT departments. e.g.. 00:40:11:0e:00:00. See How to locate a computer's MAC address to obtain a computers MAC address.

Issue Unable to download MP-V Flow Balance Data object to a controller using download all Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The inability to use download all is a protection added to prevent overwriting any flow balance data inadvertently Resolution All Flow Balance Data Object properties are downloaded by explicitly downloading the Flow Balance Data Object as shown in the video below    

Issue "Enable incoming http communication" option is grayed out and cannot be unselected. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When Building Operation Workstation is connected to the SmartX Server using a HTTP connection, the option to disable incoming HTTP connection is unavailable.     Resolution Use HTTPS in Building Operation Workstation to connect to the SmartX Server to allow this option to be unselected. Refer to the Online Help Topic: Disabling Incoming HTTP Communication

Issue Want to create reports from an AS Environment Automation Server Cause To be able to create reports you will have to have an ES and a reportserver installed. However you can export a trendlog to XML or CSV and create you own report with a thirdparty software. Resolution Install an ES and a reportserver or export a trendlog to CSV or XML and use a thirdpart software to create your report.

Issue Unable to change the password of the Administrator account. The Access Expert application will not start following a change to the Administrator user account. Product Line Access Expert Environment Access Expert Software Cause The administrator account is a special account used by the services associated with Access Expert. Any attempt to change the password of the Administrator account will render the application unable to start. Attempting to open the properties of the Administrator accounts results in Access Expert trying to create a new administrator user account. Resolution Under no circumstances should the Administrator account password be changed.

Issue Procedures and processes to secure I/A Series Niagara 4 Systems Product Line TAC IA Series Environment  I/A Series Niagara 4 Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara 4 system.  While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara 4 system more secure by carefully configuring and using: Passwords System Passphrase Platform Account Management Station Account Management Role and Permission Management Authentication TLS and Certificate Management Module Installation Additional Settings External Factors Please note that while all of these steps should be taken to protect your I/A Series Niagara 4 system, they do not constitute a magic formula. Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn’t mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it. Note: Schneider Electric strongly recommends upgrading to the latest I/A Series N4 version maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build-included documentation to understand the behavioral impacts of the security enhancements and JACE hardware platforms supported. Download the Niagara 4 Hardening Guide_2023 for more details.

Issue Understand methods for integrating Security Expert with Active Directory for creation and management of Operators and Users. Product Line EcoStruxure Security Expert Environment Security Expert Active Directory SX-AD-OPR SX-AD-USR SX-DB-SYNC Cause Security Expert Active Directory Integration provides synchronization and authentication for Active Directory users enabling organizations to leverage on the user management and security policies that Active Directory provides. This article looks at the details between each integration option. Resolution There are four options for Active Directory Integration. 1. Default Windows Authentication option. This allows for logging in to Security Expert with the Windows User account credentials which could include AD users if on a Domain. Operator object must be created in Security Expert and configuration of windows authentication option has some specific steps to be followed for it to work. Unable to login to Security Expert using Windows Authentication Remember to use syntax "<domain>\<username>" for the username when configuring the Operator for a Windows user ON a  Domain. Remember to use syntax "<computername>\<username>" for the username when configuring the Operator for a Windows user that is NOT on a Domain. No extra license is required for this. 2. SX-AD-OPR : License for adding Security Expert Operators from AD. Security Expert Operators will need to be added manually using the following steps: Navigate to Operators and click Add. Check the Windows Authentication box. Click the ellipsis adjacent to the User Name. Use the Active Directory Users window to search for the AD credentials you wish to use. Once the Operator has been added, you may check the Windows Authentication option when logging in. 3. SX-AD-USR : License for adding Security Expert Users from AD. This will allow an active directory domain windows group to be periodically polled for updates that will in turn update the Users in Security Expert. Individual options for importing users, disabling user if AD user is disabled, disabling user if AD user is deleted. Only user names are imported, other than this only action can be disabling of users in Security Expert. No other details can be updated or added. See application note AN-141 Security Expert LDAP User Import Configuration. 4. SX-DB-SYNC : Data Sync Service with Powershell script. Powershell script pulls user details out of AD and writes to a CSV file that the Data Sync Service then imports into Security Expert. Can perform more functions than SX-AD-USR as any attribute from AD users can be mapped to any attribute in Security Expert users. Will require use of powershell experience as the sample script will likely need to be tweaked. Here is a really good video Using Data Sync to Transfer Information from Active Directory to ProtegeGX on using Windows Active Directory as a source of Users/Operators for the Data Sync Service. It provides a good overview of how this is accomplished and how easy it can be to setup. See Security Expert Data Sync Service and sample Powershell script SXFetchADUsers.zip attached  

Issue Unable to determine whether the Enocean device in hand is compatible with MPM controllers Unable to add more devices to a MPM controller Product Line EcoStruxure Building Expert Environment Multi-Purpose Manager Cause Some pre-configured icons in the "Add Devices" list have a name but do not have a specified Enocean profile or vice versa. Resolution The Following devices are embedded in the MPM firmware and require no scripts to integrate with an MPM. All Devices in the below list (except for Enocean relay) are outbound devices (i.e. devices that are only able to send telegrams to other devices) MPM Sub-device list Description Compatible Schneider-Electric Products CO2 Sensor A5-09-04 CO2 Sensor SR04 CO2 (LSS442510) (868MHz) Door/Window Sensor D5-00-01 Single Input Contact SED-WDS-U-5045 (902MHz) 10020032 (LSS10020032) 10020042 (LSS10020042) 10020047 (LSS10020047) Double Rocker Switch F6-02-01 Light and Blind Control – Application Style 1 EDRPU-W-EO (902MHz) 10020048 (LSS10020048) (868MHz) Enocean Relay Inbound profile   Enocean Switch Light and Blind Control – Application Style 2 ESRPU-W-EO (902MHz) 10020049 (LSS10020049) (868MHz) Enocean Thermostat Obsolete   KeyCard Switch F6-04-01 Key Card Activated Switch SED-KCS-U-5045 (902MHz) Light Sensor A5-06-01 Light Sensor Range 300lx to 60.000lx 10020047 (LSS10020052) Light Sensor A5-06-02 Light Sensor Range 0lx to 1.020lx SED-LLS-U-5045 (902MHz) LSS10020053 (868MHz) Motion Sensor A5-07-01 Occupancy Sensor with Supply Voltage monitor SR-MDS Bat SED_CMS_U_5045 (902MHz) Thermostat A5-02-05 Temperature sensor Range 0°C to +40°C SED-T00-U-5045 (902MHz) 10020046 (LSS10020046) 10020033 (LSS10020033) Thermostat A5-04-01 Temperature & Humidity sensor Range 0°C to +40°C and 0% to 100% SED-TH0-U-5045 (902MHz) 10020041 (LSS10020041) SR04 rH Thermostat A5-08-01 Light, Temperature and Occupancy sensor Range 0lx to 510lx, 0°C to +51°C and Occupancy Button SR-MDS Thermostat A5-10-03 Room Operating Panel: Temperature Sensor and Set Point Control SR04 P (LSS226172) Thermostat A5-10-05 Room Operating Panel: Temperature Sensor, Set Point and Occupancy Control SED-TS0-U-5045 (902MHz) Thermostat A5-10-10 Room Operating Panel: Temperature and Humidity Sensor, Set Point and Occupancy Control SED-THS-U-5045 (902MHz) Thermostat A5-10-12 Room Operating Panel: Temperature and Humidity Sensor and Set Point SR04P rH(LSS252331) Thermostat A5-10-19 Room Operating Panel: Humidity, Temperature Set Point, Temperature Sensor, Fan Speed and Occupancy Control   -The maximum number of devices added to each MPM is 49 -The maximum number of EnOcean devices added to each MPM is 49 -The maximum number of EnOcean devices with the same EEP added to each MPM is 49 .This only applies to firmware 2.13.1 and later, the limit for previous firmwares is 20. An Exception is the following limits for devices/widgets per MPM 20 EnOcean Switches 20 EnOcean Relays 4 EnOcean Thermostats The Devices in the next table do not have a pre-configured icon in the devices list, however, scripts can be used instead and can be found below (Please read PDF first) Enocean Scanner Enocean device driver Valve driver Enocean profiles supported in script EnOcean Equipment Profile (EEP) Description Example of Compatible Devices (EEP A5-38-08) Central Command Gateway Plug-in 15 Amp 120V 902Mhz 5-Wire 6A Relay 24V 902Mhz 3-Wire 6A Relay 120/240/277V 902Mhz (EEP A5-11-01) Lighting Controller 15A-20A 120/277/347V 902Mhz (inbound profile: A5-11-01) 15A 120-277V 902Mhz (inbound profile: A5-11-01) (EEP A5-10-04) Temperature Sensor, Set Point and Fan Speed Control Thermokon SR04PS (EEP A5-02-14) Temperature Sensor Range -20°C to +60°C Thermokon SR65TF (EEP F6-03-01) 2 to 4 Rocker Switch (Light and Blind Control) Push-button, 2-gang (EEP A5-20-1) Battery Powered Actuator Thermokon SAB02/SAB05     Din Relay 1 channel (inbound profile: F6-02-02)     PWM 230V valve driver (inbound profile: A5-02-05) PWM 24V valve driver (inbound profile: A5-02-05)

Issue Windows Authentication must be applied consistently for Security Expert, SOAP, and Data Sync Service to work. Product Line Security Expert Environment Security Expert Microsoft Windows Cause If Windows Authentication is enabled in Security Expert (this is done during installation with a checkbox) then it must also be enabled in SOAP and Data Sync Service. Resolution Windows authentication is NOT enabled by default in Security Expert. This is a tick box on Security Expert installation. When you install SOAP you also need to select this (another tick box). However, Data Sync Service (DSS) is created with no options during installation. To enable or check the Windows Authentication setting for Data Sync Service, see below. If installation has already been completed and you need to verify if Windows Authentication is enabled for each component you must follow the steps below.   1. Security Expert Thick Client/Server   There are two options for setting Windows Authentication for Security Expert Thick Client/Server. Option 1. Edit the Security Expert Data Service config file “SecurityExpertSV.exe.config” using a text editor. This file is located in C:\Program Files (x86)\Schneider Electric\Security Expert. Locate this line: <netTcpBinding> <binding name="Binding1" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"><security mode="None"/> <readerQuotas maxDepth="32" maxStringContentLength="90000000" maxArrayLength="90000000" maxBytesPerRead="90000000" maxNameTableCharCount="90000000" /> </binding> </netTcpBinding> security mode= “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing. Option 2. Rerun the installation process and select “Modify” and then set the enabled flag tick-box or make sure the tick-box is not checked, depending on what is required.   2. Security Expert SOAP   There are also two options for setting Windows Authentication in SOAP. Option 1. Edit the SOAP service “Web.config” file located in C:\inetpub\wwwroot\SecurityExpertSOAPService with a text editor. Locate this line: <netTcpBinding> <binding name="Binding1" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"><security mode="None" /> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> </binding> </netTcpBinding> Again, security mode = “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing. Option 2. For SOAP you also have the option of uninstalling and reinstalling and selecting the check box (or not) to enable Windows Authentication during the install process. The installer for SOAP currently does not support “modify” or “change” operations.   3. Data Sync Service   Edit two config files using a text editor. Both files are located in C:\Program Files (x86)\Schneider Electric\Data Sync Service. In “DataSyncServiceConfig.exe.config” locate this line: <netTcpBinding> <binding name="NetTcpBinding_IService" openTimeout="00:10:00" receiveTimeout="00:21:00" sendTimeout="00:21:00" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> <security mode="None" /> </binding> </netTcpBinding> Again, security mode= “None” denotes that Windows Authentication is not enabled. If Windows authentication has been enabled during installation then this entry will be missing.   4. Summary   In order to properly run SOAP and Data Sync Service with a Security Expert system, there are four config files that must be consistent. SecurityExpertSV.exe.config Web.config DataSyncServiceConfig.exe.config DataSyncService.exe.config All four must either contain the text <security mode="None" /> or all four must NOT contain that text.

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 When upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager Cause The proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link  

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 Download Service fails to start after an upgrade to v.4.2.251 Product Line EcoStruxure Security Expert Environment Security Expert Server v4.2.251 Cause Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501; (VC++ 2013 Redist v12.0.0.30501.0) is not installed. This package is a pre-requisite to installing Security Expert v4.2.251. It was needed for extending the Suprema integration but did not get added to the installer for that version. This is now packed with the Security Expert installer. Resolution There are two options to resolve this; 1. [Preferred Option] Install the current release of Security Expert. This required package is now included in all new versions of the Security Expert installation file. 2. Install the package from Microsoft before installing Security Expert 4.2.251. Locate the file on the Microsoft site https://www.microsoft.com/en-nz/download/details.aspx?id=40784. Download and install vcredist_x86.exe, the 32 bit version (because Security Expert is a 32 bit application), before performing the upgrade.

Issue The modbus RS485 connectors on the MPM-UN are marked MOD A & B, the documentation does not state the polarity. Product Line EcoStruxure Building Expert Environment MPM-UN Modbus Cause Documentation does not state the polarity of the Modbus connectors. Resolution Connect the Modbus device to the A-B connectors on the MPM. Connect the positive lead to connector A and the negative lead to connector B.

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 Issues upgrading Automation Servers (AS, AS-B, AS-P) connected to an Enterprise Server (ES) from versions prior to 2.0.x to a version that is 2.0.x. ES and one Automation Server will upgrade but no others connected to that same ES will upgrade and will show an error while attempting to download the new software.  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v1.9.x Building Operation Enterprise Server v1.9.x   Cause If the Automation Servers within the ES environment are not uniquely named, and/or are the same name as the ES, an error will be received if upgrade is attempted stating "Deploy upgraded database failed". Resolution As found within the Enterprise Central section of the 2.0 Release Notes, "All servers must have unique names".   *NOTE* Renaming the Automation Server will break any paths to that Automation Server, as such they will need to be corrected.   Follow these steps to address this issue: Prior to upgrading any devices within the environment, check for and find any servers with non-unique names Detach the Automation Server (with the naming identical to the ES or any other server) from the ES Rename the Automation Server with a unique name Correct any binding path issues Reconnect Automation Server to the ES Upgrade the environment to 2.0.x

Issue The property list for an Analog Input / Output or Binary Input / Output object in the WorkPlaceTech application shows a "Process Time" parameter: OR instead of a "COV Increment" parameter" Note that for Binary I/O objects, the COV increment is implied as any change of binary value and is not displayed. Environment MNB series controller WPT application file MNB series controller with firmware release 1.4 or newer WorkPlace Tech Tool software, release 5.5 or newer Cause Prior to firmware version 1.4, the MNB family of controllers did not support COV Subscription functionality. Resolution The existing I/O object must be deleted and recreated, using the WorkPlace Tech Tool software release 5.5 or newer, to allow the use of the COV Increment parameter.

EBO doesn't support save from controller for B3s

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

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 Integrating MNL-VAV controllers into the EBO system successfully Product Line EcoStruxure Building Operations, TAC IA Series Environment Building Operation Automation Server Building Operation Automation Server Premium I/A Series MNL VAV Cause Lost flow balancing values during integration Lost S-link offset calibrations Resolution Use the following steps to bring a controller into the Automation Server with all data intact. Using WorkStation connected to the AS/AS-P; right click on the LonWorks Network and select New then Device. Choose the appropriate device object type from the list for the MNL-VAV controller being added, give it a name and click Next. Type in the Neuron ID or use the Service pin method to identify the controller. Check the box next to “Commission” and the radio button next to “Keep current configuration in the device” and click “Create” then click “Close” when complete. Right-click on the new device object in the tree and select MNL and then “Backup flow balance information”. When this is complete notice the blue circle with a white checkmark next to the nciHighFlowCal and nciLowFlowCal SNVT’s indicating the AS-P DB contains the balance data from the controller. If special S-link offset values exist in the controller right click on the device object in the tree and select MNL and then “Backup S-link offsets”. Right-click on the controller device object and select MNL and “Assign application” and click on the appropriate application file for this controller and click on “Assign”. Right-click on the controller and select MNL and “Download application”. Click on “Close” when complete. Right-click on the controller and select MNL and “Restore the flow balance information” Right-click on the controller and select MNL the “Restore S-link offsets”. Verify all data is correct and the controller is functioning properly.