Building Automation Knowledge Base

Issue The 6 character PIN for the SmartXKiosk has been forgotten so the user cannot exit Kiosk mode Note the PIN is case sensitive Product Line EcoStruxure Building Operation Environment SmartXKiosk Advanced Display v1 Advanced Display v2 SmartX Controller Cause The 6 characters PIN for the SmartXKiosk has been forgotten or lost and the user cannot locate it. Resolution In order to reset your SmartXKiosk PIN, follow the steps below:   In the SmartXKiosk application, click on Exit Kiosk Mode in the bottom right corner of the screen. In the Exit Kiosk Mode window, click on Forgot PIN?. An 8 characters or 15 characters Session ID will be generated.  Take note of this Session ID.    Open a ticket with Support to request a SmartXKiosk PIN reset and provide them with the Session ID. Once Support sends you back the Recovery PIN, click Continue on the Session ID window. In the next window fill in the Session ID from step 2. and the Recovery PIN that Support has provided. Click Continue. You can now reset your PIN. Enter your new 6-digit PIN number and confirm it before clicking Submit. The PIN is case sensitive. It must be exactly 6 characters, otherwise an error will occur.  Important Note: The Session ID generated and the Recovery PIN provided to you by Support will expire at midnight on the day that the Session ID was generated.   Note: For Advanced Display v3 please see How to recover the password for Advanced Display version 3

Issue DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED is illuminated. Environment Stand alone discrete Controller in Alarm mode. DC1100 Optimiser / Compensator Controller. DC1400 Optimiser / Compensator Controller. Cause DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED has been triggered by the occurrence of one of the following conditions: Sensor Input is short circuit or open circuit and / or out of range. Boiler Temperature at least 10 deg C above Boiler High Limit value. Boiler Temperature below Boiler Low value after one hour. Compensated Flow Temperature below Flow Low value after one hour. Resolution DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed and / or cleared using the following procedures. VIEW ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to VIEW ALARMS CLEAR ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be cleared as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to CLEAR ALARMS Using Up and Down Arrow Keys Select Pass Number (0112) and ENTER In the event that an Alarm is not cleared by the above procedure and the Alarm LED does not extinguish then the Sensors and / or installation in general should be checked further. DC1100 Optimiser / Compensator Controller overview may be viewed here DC1100 Optimiser / Compensator Controller details and menus may be viewed here DC1400 Optimiser / Compensator Controller overview may be viewed here DC1400 Optimiser / Compensator Controller details and menus may be viewed here

Issue The following error is generated during the SQL Configuration step for 1.8 Reports Server Product Line EcoStruxure Building Operation Environment WebReports Installer Cause This can happen for various reasons: Possible cause 1 The Microsoft .NET Framework installation is damaged after installing Microsoft SQL Server. Possible cause 2 In one of the steps during SQL installation, we have to configure NT AUTHORITY\SYSTEM. If user fails to change this and move ahead with default user then create database step would fail. Possible cause 3 The operating system is not using English as its selected language. Resolution Solution 1 Quit the WebReports Installer Package Remove/reinstall or repair .NET Framework 4.5 (Available from Microsoft .NET download site or direct download - WebInstaller - OfflineInstaller) Repeat the installation of WebReports Solution 2 Set the SQL server service log on properties to "Local System" (NT AUTHORITY\SYSTEM) Restart the SQL server service Repeat the installation of WebReports Solution 3 Replace the WebReports OS with an English version of Windows. 

Issue EcoStruxure Building Operation Demo Database Package Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site Cause EcoStruxure Building Operation Demo Database Package and going between releases. Resolution All current and previous sales packages/demo databases can be found on the Exchange for download. Note: The Demo Database package is a sales and marketing tool for your use "as is." It is not supported through Product Support Services (PSS). If you have product specific technical issues such as installing the software applications (e.g. License Administrator, Enterprise Server) PSS may be able to help. However, PSS does not support the Demo Database contents or features. The Demo Database can be re-installed to return to its original state.

Issue In the Workstation, old alarms are showing in the alarm pane. Recheck does not remove, and the only option left is to "Hide". The same goes for disabled alarms. Is there a way to erase or scrub these 8-month-old alarms? When checking disabled alarms, there are a lot of alarms that have been disabled, but no one has disabled any alarms. When right-clicking on the alarms to get the context menu, most of the alternatives are greyed out. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.2 or higher Cause First, check the disabled cause to see what disabled the alarms. If it is "user," a person has disabled them. If it is "system," the system has automatically disabled them because the alarm object has lost its monitored value. Resolution Alarms in the alarm view "Recheck" command does not help then try the "Alarms Integrity Check" commend, please see LL Removing invalid alarms  Check the source path on the alarms, do they point to actual alarm objects? If the alarm objects that triggered the alarm in the first place still exist, you should be able to disable them then just enable them again. If you cannot, use the disable button in the alarm viewer then you can use the Disable alarm property in the editor (assuming version 1.2 or higher). If you can’t disable them then try to trigger them back and forth once. If the alarm objects don’t exist anymore, create alarms that would fit the source path, then just trigger those. After that, it should be safe to delete the alarm objects again. Basically, the alarms you create will take ownership of the old alarms in the viewer. Also, add the column Type in the alarm viewer and see what type they are. It would be helpful to know what the Source path and System alarm id (if there is one) are. Remove old Alarms in Alarm Pane Disabled alarms If the monitored values are not used anymore delete the alarm object that monitors the value If this is not enough make sure the path exists in the system, it can be needed to recreate the alarm in the correct path meaning the folder structure needs to be recreated. There is also the choice of right-clicking on the Alarm which gives the following menu: From this menu, one can Disable the alarm or alternatively, Hide the alarm. To view Hidden or Disabled alarms once they are not shown in the Alarms window, select one of the two Icons from the Alarms window icons as shown below:

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 How to migrate ebo_db from an old PostgreSQL/TimescaleDB PC to a new PostgreSQL/TimescaleDB PC Product Line EcoStruxure Building Operation Environment PostgreSQL TimescaleDB pgAdmin Building Operation Workstation Cause When using External log Storage (the TimescaleDB in PostgreSQL server) in EcoStruxure Building Operation, it is often required to migrate the TimescaleDB (ebo_db) to a new PC or a different HDD due to the hard-disk space issue.   Resolution Stop the External Log Storage (TimescaleDB) from all the EBO servers (ES & AS’s). Using the attached zip file, extract the XML TimescaleDB Search Export and import this to the root location of your server.   The resulting search results will provide ALL servers' Timescale objects and show the status of the Event and Trend configurations. allowing you to multi-select and change the Event and Trend configuration settings quickly.  Use the CRTL key to only select the relevant servers. Alternatively, follow the steps below to locate these properties manually.    Note the Export is for version 3.2.3 Expand the ES Server, expand the System folder, and expand the External Log Storage folder. Right-click the TimescaleDB and select the Properties. Disable the Event Configuration & Trend Configuration and save. Repeat the above operation for all the other servers (AS’s) that are enabled for the External Log Storage. Create a new database in the destination External Log Storage server PC using the “EBO External Log Storage Installer” tool. Refer to page 5 “Database Management” section of the “EBO External Log Storage Installer.pdf” document for detail. Backup the “ebo_db” from the source TimescaleDB server PC using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html ), or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail. Copy the DB backup file to the destination TimescaleDB server PC and restore the database using the pgAdmin4 tool (refer to https://www.pgadmin.org/docs/pgadmin4/development/restore_dialog.html ). DB Restoration may take a couple of minutes to a couple of hours depending on the size of the database. DB restoration results may show an error caused by pre-existing information in some tables, but it can be ignored. Once DB restoration is completed, make sure to check the timestamp of the oldest log data and the latest log data to verify the result. Start the External Log Storage (TimescaleDB) from all the EBO servers (ES & AS’s) using the search provided in Step 1 or manually as follows: Expand the ES Server, expand the System folder, and expand the External Log Storage folder. Right-click the TimescaleDB and select the Properties. Change the Database name, Host address, User name, and Password for the new (destination) External Log Storage server PC Enable the Event Configuration & Trend Configuration and save. Repeat the above operation for all the other servers (AS’s) that were disabled in the above step 1.

Issue Configuration of BACnet Foreign Device Registration Product Line EcoStruxure Building Operation,  Andover Continuum Environment BACnet IP  BBMD Foreign device Cause  Foreign Devices registration can be confusing Resolution When configuring a Foreign Device Registration on a B/IP BACnet Network. The Foreign Device only needs to register with the one BBMD on its B/IP Network Segment. The BBMD that has the Foreign Device registered with it creates a table called FDT (Foreign Device Table) internally which is different from the BDT(Broadcast Distribution Table) that the BBMD uses to communicate with other BBMDs.   Once the FDT confirms the Foreign Device, it is up to that BBMD to distribute BACnet communications to and from the necessary BBMD's in its BDT. and the all Foreign Devices in its FDT.  In this way the Foreign Devices does NOT perform Broadcasts.

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Can the Advantech touch screen be used as a Sigma server? Environment Sigma WinCE Advantech Touch screen Panel mounted Cause System has been installed without a Sigma server. Resolution The Advantech touch screen, or any other WinCE device can only be used for general display functions, low level editing, contingency logging review and time updates, it does not have the functionality of a Sigma server. To review the latest Release note, please click HERE. To review the WinCE User guide, please click HERE.

Issue Making a cable / adapter by using the cable guide as a reference can be confusing. Product Line TAC Vista Environment Vista Menta Download Wizard Cause Without knowing to use a Ribbon (Rollover) Cable, or the correct pins of RJ45 and DB9, it can be difficult to build this cable and adaptor. Resolution Note: Pay particular attention to the pins numbers, this view is the inside of the adapter! This is the pinout to be used in conjunction with a "ribbon" type cable. A Ribbon (Rollover) Cable has inverse ends. For example, Pin 1 of one RJ45 will be Pin 8 at the other end, Pin 2 will be 7, Pin 3 will be 6 and etc..                                    Here is a Diagram which highlights the path of TxD RxD and GND from the PC to the Xenta Controller. Use and Ohm meter to check the continuity of connections. If you are having communication problems, please see Verifying Serial Port Communications with loopback test   for further troubleshooting tips.                Alternatively, a cut ethernet cable can be wired to a DB9. DO NOT use an Ethernet Cable with the above adapter. 1. Use a standard 586B RJ45 ethernet cable pictured below.                2. Connect RJ45 jack to a DB9F according to the following diagram.

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 Need to replace and upgrade AS (Classic) to AS-P-NL. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Building Operation Automation Server Premium non-LON (AS-P-NL) Cause From EBO v3.2 the AS-P-NL is available, there is a need to upgrade an AS (Classic) but the AS is only supported up to v3.1. Resolution A lower version of EBO can be installed into the AS-P-NL e.g. from v2.01, but this must only be for the purpose of upgrading the database.   Therefore the upgrade path can be as this example shows, there is a requirement to upgrade an AS from v1.6: Upgrade AS v1.6 to v3.1.x) . Backup the AS. Install v3.1.x) on AS-P-NL ( x needs to be same as in step 1). Note: Installing 3.1.x on an AS-P_NL is only for the purposes of upgrading the database, the following steps 4. and 5. must be completed . Restore backup on AS-P-NL. Upgrade to v3.2 or later.   For details regarding upgrade paths see article - Upgrade path from version 1.0 to current version 

Issue Need a description of Zigbee error codes Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause No list of error codes available Resolution Here is a list of all possible error codes Error Code (HEX) Error Code (Decimal) Error Description   -2 Device offline (communication initialization after changing Ext. Network ID in ZVC)   -1 Device not bound 0x00 0 Success. Operation was successful. 0x01 1 Failure. Operation was not successful. 0x02 - 0x7d 2 - 125 Reserved by Ember 0x7e 126 Not authorized. The sender of the command does not have authorization to carry out this command. 0x7f 127 A reserved field/subfield/bit contains a nonzero value. 0x80 128 Malformed command. The command appears to contain the wrong fields or invalid field. 0x81 129 Unsupported cluster command. The specified cluster command is not supported on the device. Command not carried out. 0x82 130 Unsupported general command. The specified general command is not supported on the device. 0x83 131 Unsupported manufacturer cluster command. A manufacturer specific unicast, cluster specific command was received with an unknown manufacturer code, or manufacturer code was recognized but command is not supported. 0x84 132 Unsupported manufacturer general command. A manufacturer specific unicast, ZCL command was received with an unknown manufacturer code, or the manufacturer code was recognized but the command is not supported. 0x85 133 Invalid field. At least one field of the command contains an incorrect value, according to the specification. 0x86 134 Unsupported attribute. The specified attribute does not exist on the device. ( Zigbee Module not fully compatible with Room controller and FW of MPM) 0x87 135 Invalid value. Out of range error, or set to a reserved value. 0x88 136 Read only. Attempt to write a read only attribute. 0x89 137 Insufficient space. An operation failed due to an insufficient amount of free space available. 0x8a 138 Duplicate exists. An attempt to create an entry in a table failed due to a duplicate entry already being present in the table. 0x8b 139 Not found. The requested information could not be found. 0x8c 140 Unreportable attribute. Periodic reports cannot be issued for this attribute. 0x8d 141 Invalid data type. The data type given for an attribute is incorrect. Command not carried out. 0x8e 142 Invalid selector. The selector for an attribute is incorrect. 0x8f 143 Write only. A request has been made to read an attribute that the requester is not authorized to read. No action taken. 0x90 144 Inconsistent startup state. Setting the requested values would put the device in an inconsistent state on startup. No action taken. 0x91 145 Defined out of band. An attempt has been made to write an attribute that is present but is defined using an out-of-band method and not over the air. 0x92 - 0xbf 146 - 191 Reserved by Ember 0xc0 192 Hardware failure. An operation was unsuccessful due to a hardware failure. 0xc1 193 Software failure. An operation was unsuccessful due to a software failure. 0xc2 194 Calibration error. An error occurred during calibration. 0xc3 - 0xff 195 - 255 Reserved by Ember   256 Device offline   257 Device profile does not match selected device widget in Building Expert

Issue During a Vista 5.x.x installation, failure can occur during the SQL installation portion of the install. This solution could encompass many different SQL installation errors; however, one that is known and verified is shown below: Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Here is another common one:   Failed to create or configure database in SQL Server ([1802] CREATE DATABASE failed. Some file names listed could not be created. Check related errors.) If you have previously uninstalled Microsoft SQL Server, data files for the database may still exist in the SQL Server data directory. Remove the files manually and click Retry or click Cancel to abort installation. Product Line TAC Vista Environment TAC Vista Server 5.x.x Cause Uninstalling and reinstalling the software can leave pieces of SQL behind. Even if you try to uninstall everything in Add/Remove Programs, left over portions may cause the TAC Vista installation not to be successfully installed. The Program Files\SQL Server directory is flagged for compression or encryption. Installing Vista version below 5.1.5 on a Windows 7 64bit machine will cause this error. Resolution Please check the Windows Event log for the specific installation error. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes for information on viewing the Windows Event Log. Consult Log file of SQL installation when installing Vista Server for information on viewing the SQL Server installation log. If the Event log reveals Error 28001, the sa password must meet SQL Server password policy requirements, please refer to the solution provided in Error 28001 - sa password complexity error when installing TAC Vista 5. If not, then please proceed with the resolution below: If the SQL Server installation log file complains that the Program Files\SQL Server\ directory is flagged for encryption or compression then right click on the directory and select properties. The advanced option exposes the check boxes for compression and encryption. If the folder is flagged for compression the it will be visible in blue instead of black font. Remove the encryption or compression flags and apply then reinstall. If the PC operating system is Windows 7 64-bit, install Vista 5.1.5 or higher. Resolution below will not solve the issue. In most cases this is caused by MSXML 6.0 parser. This software is commonly installed by programs using SQL, and also during the TAC Vista installation. If this can't be removed using Add/Remove Programs, you can download a program from Microsoft that cleans up and removes this software (and others). It is called Windows Installer Cleanup. Link to download: msicuu2.exe. NOTE: Microsoft recently removed this utility from the downloads section of their support site. They have this to say about the utility: While the Windows Installer Cleanup utility resolved some installation problems, it sometimes damaged other components installed on the computer. Because of this, the tool has been removed from the Microsoft Download Center. Use this utility with care at your own risk.   In most cases TAC Vista will install successfully after removing MSXML 6.0 parser. For alternative solutions see SQL Express install fails on MSXML 6 and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed .

Issue Sigma 4 05 Sigma Compact Edition supports the following hand-held devices: iPAQ 114, iPAQ 214, iPAQ 2490b, Dell Axim X51 These devices are no longer available, so what can be used? Environment Sigma WinCE Hand-held devices Compact Edition Cause Supported hand-held CE devices, such as the iPAQ 114, iPAQ 214, iPAQ 2490b, Dell Axim X51 are no longer available. Resolution The ever-changing PDA market has continuously caused problems, by obsoleting devices and creating new ones. This led to us always trying to catch up. With Sigma 4 05 Sigma Compact Edition, it was decided that a method to future proof must be found. This release does not support any additional devices, but it now supports the use of a "Mini PC", Netbook, Notebook etc. To review the release note for the Sigma Compact Edition 4.05 Click Here. To review the User guide for the Sigma Compact Edition 4.05 Click Here.

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue Unable to read the Analog Inputs / Universal Inputs values in StruxureWare Building Operation. Product Line EcoStruxure Building Operation Environment Xenta I/O Modules Xenta  421A, 422A, 451A, 452A as standalone LON nodes StruxureWare Building Operation (SmartStruxure) Cause When using the Xenta Input Output modules 421A, 422A, 451A, 452A as stand alone Lonworks node, the UCPTConfiguration must be set to the necessary integer value for the required input, by default the values are set to zero so can not be configured. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network Expand the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the nciInput(x) variable within that module Set the value of Absolute count to one of the following : 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication   Up to SBO Version 1.7.x     SBO Version 1.8.x and on in the "Variable Fields" tab overwrite the string "Min" with for example 6 

Issue During Energy Expert installation an error is shown, and the floating license manager is never installed Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) Installation Cause "Error 1722" occurs due to a conflict between the version of Java installed on the PC and the version included in the EE installation package Resolution Uninstall all versions of Java from the PC Install the JavaRuntime manually from the install media "..\setup\SetupSupport\Licensing\JavaRuntime\x86\jre1.7.0_02.msi" Run the complete installation again

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