Building Automation Knowledge Base

Issue After correctly following the process outlined in Setup External Log Storage using MSSQL., EcoStruxure Building Operation (EBO) server fails to connect to the external database, generating the following System Alarms:  Unable to connect to data source Login failed for user The system alarm specifically details an issue with the ODBC SQL Driver as below: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium (AS-P) External Log Storage [MSSQL]  Cause The system alarm details indicate an issue with the ODBC SQL Driver, specifically: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" This suggests a compatibility or configuration issue with the ODBC driver or connection string.   Resolution The following has been seen to correct the issue: Verify User Credentials Ensure that the username and password used for the ODBC connection are correct. Note: SQL Server credentials are case-sensitive, so double-check for any discrepancies in letter casing. Remove any uppercase for the username. In some cases, using only lowercase letters for the username in the ODBC connection string has resolved the issue, e.g,. Instead of "My_User" use "myuser"

Issue Cannot activate a license on an Automation Server although the entitlement works on other Automation Servers. The Device Administrator output is similar to the following:   Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: =V(BACK_OFFICE%DEBACK_OFFICE+]\fK%MDEVICEID|0}~;DEVICEID/jlSk\}K qq7!vi%DCH'~A%05pQWN]G|3^Jk+yaz_Kx/:Dy&w F7BWWN#`Ex|6S.d<Y^nV~@?*C.D0])"KO?[pS#GH|aMe+i|@4's9kNE\7gfocfVbRf$1VuH>sdp_JN6%4B.n|Zm$]wi9M|F8#Hrw~/L4%XU<?8o="P1S$uW6Fu5vAsAz|l>8.@XA|.'[v_ekh_P}c7 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause When an Automation Server fails in the field an RMA (Return Material Authorization) request is made, and the license is returned for re-use in the replacement Automation Server. Once this occurs the serial number of the faulty Automation Server is blacklisted to ensure that it cannot be licensed and reused. Resolution If the device was mistakenly added to the blacklist please supply the Automation Server serial number to Support. If an RMA number does not exist in the licensing system for this Automation Server, the support team can make a request to have the server removed from the blacklist.

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 How are Elsys LoRaWAN sensors configured with a smartphone using NFC Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause All Elsys sensors are equipped with NFC for easy configuration with a smartphone. There is a requirement to configure these sensors using a Smartphone or tablet using Elsys 'Sensor Settings' application. Resolution Download the ELSYS “Sensor Settings” application from Google Play or the IOS App store and install it on a smartphone or tablet.     Ensure the mobile device supports NFC. Enable NFC on the device and start the application. Position the mobile device directly on the NFC antenna of the sensor. Ensure both devices remain close and stationary to maintain optimal connectivity. Remove the mobile device. The current settings will be displayed in the application. Set the 'Timebase' to 120 seconds using the application. Remember to revert it to 600 seconds after commissioning!    Make note of the following sensor keys: DevEUI: The unique ID of the sensor, found in the blue panel at the top. AppEUI: Application ID (8 bytes or 16 hex digits). Default is 0, can be changed if needed for the application. AppKey: Application unique key (16 bytes or 32 hex digits) that is the encryption key used for messages during every over-the-air activation. Tap the sensor's NFC antenna to transfer the new settings after making the desired changes. Ensure the application confirms the updated settings. Wait for the sensor to reboot, indicated by the LED flashing. The sensor settings should now be updated. Validate your settings by reading the NFC data after the sensor has restarted. Verify that settings have been applied by using the ‘Read’ functionality in the app and touching the sensor’s NFC antenna.    Remember to change the 'Timebase' back to 600 seconds after the commissioning is completed!

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x or later directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers AS-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS  Note: Upgrading ES from 1.x gives the ability to host the maximum quantity of field devices / controllers at the Enterprise Server (600). Also, when a system is upgraded from 1.x, it will be provided with an unlimited (bounded by the maximums stated in the Architectural Guidelines) client license for connections to the Enterprise Server that has been upgraded.   The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP30010 ES Upgrade from 3.X to EBO 2022 or later (i.e. to the current EBO version) with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 or later These licenses need to be activated using Device Administrator.   For each AS-P (non secure boot AS-P and AS-P-NL), one of the following bundles would be required for each AS-P.   SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full SXWSWASPUP30BP Full Bulk pack for upgrading AS-P-XX from EBO 3.x to EBO 2022 or later, contains 125 pieces of SXWSWASPUP30FU. For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP30SD Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   If the “SXWSWASPUP30EN Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Enhanced” license was purchased for an AS-P classic, and later it requires an  full license. SXWSWXUP00ENFU ASP Bundle upgrade - Enhanced to Full Would need to be purchased.   For the AS-Bs (AS-B-24, AS-B-24H, AS-B-36, and AS-B-36H), one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full, would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP30SD ASB Upgrade – Standard license is all that is required.   For the additional AS-P classic one of the following licenses would be required. SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   For the additional AS-P secure boot one of the following licenses would be required. SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required. SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. If an additional AS-B classic was added one of the following licenses would be required. SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs     Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x or later, one of the following licenses would be required to upgrade to EBO 3.x first:   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x or later:   SXWSWECUP30005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP30010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2024”   For information on software and features that require licenses  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work.   Important Note: The SIM must not have a Username, Password, or PIN. These features are not supported. Refer to Steps to follow to unlock SIM PIN when using SIM Card under Flex server The user must ensure that no firewall is applied by the SIM provider. If a firewall exists, it may block connectivity. We recommend using SIMs without any firewall restrictions. Ensure the data plan of the SIM should not be less than 2GB per month for approximately 100-200 streams. Issue This article provides information on the SIM cards that are currently supported in EcoStruxure Building Activate and are added to the central database to support field deployment of Flex servers. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause This eliminates the need for manual support for the already validated SIM operators individually on each server. Resolution Below is the list of the Network Service Providers whose APN exists in the backend and have already been added: MCC code (Country Code) Operator APN 260 play {"generic": "internet"} 260 plus {"generic": "mbb.mobi-data.com"} 732 claro {"generic": "internet.comcel.com.co"} 454 smc hk {"generic": "Smartone"} 520 ais {"generic": "internet"} 240 tele2 se {"generic": "mbb.mobi-data.com"} 260 t-mobile {"generic": "internet"} 262 t-mobile {"generic": "internet.v6.telekom"} 505 telstra {"generic": "telstra.internet"} 204 nl kpn {"generic": "matooma.m2m"} 208 208 28 {"generic": "datapro"} 234 voda uk {"generic": "wap.vodafone.co.uk"} 901 901 40 {"generic": "internet.m2mportal.de"} 208 free {"generic": "free"} 208 bouygues telecom {"generic": "mmsbouygtel.com"} 208 sfr {"generic": "sl2sfr"} 208 orange {"generic": "orange"} 268 vodafone {"generic": "internet.vodafone.pt"} 268 nos {"generic": "umts"} 405 vi india {"iot": "IOT.ZENATIX.COM"} 404 vi india {"iot": "IOT.ZENATIX.COM"} 405 ind airtel {"iot": "iot.com"} 404 ind airtel {"iot": "iot.com"} 724 tim internet {"generic": "timbrasil.br"} 724 vivo {"iot": "smart.m2m.vivo.com.br", "generic": "zap.vivo.com.br"} 724 claro {"generic": "claro.com.br"} 310 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 440 fl1 {"generic": "soracom.io"} 302 bell {"generic": "mnet.bell.ca.ioe"} 302 rogers {"generic": "M2Minternet.apn"} 302 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 404 idea {"generic": "Internet"} 431 etisalat {"generic": "mnet"} 430 etisalat {"generic": "mnet"} 424 etisalat {"generic": "mnet"} 424 du {"generic": "du"} 405 404 11 {"iot": "IOT.ZENATIX.COM"} 405 vodafone {"iot": "IOT.ZENATIX.COM"} 405 airtel {"iot": "iot.com"} 404 airtel {"iot": "iot.com"} 404 vodafone {"iot": "IOT.ZENATIX.COM"} 404 404 11 {"iot": "IOT.ZENATIX.COM"} 404 jio {"generic": "jionet"} 405 jio {"generic": "jionet"} Additional Information Ensure the SIM card is active and properly inserted. Verify the antenna cable is securely connected to the board. Confirm the SIM card has no firewall restrictions and meets the data plan requirements.  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work. Issue SIM card not being detected and internet is not connecting automatically when SIM card is inserted inside the Gateway.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Some network service providers have a username, password and SIM PIN set by default when they issue the SIM to the customer. If the Gateway is using the SIM for internet, it requires any username, password and SIM PIN to be disabled before inserting the SIM inside the Gateway.  Resolution Contact the Network service provider directly to disable the username and password. The Network service provider can disable the username and password from the backend. For disabling the SIM PIN follow the below procedure: Steps to follow to unlock SIM PIN An example YouTube video on the steps detailed below can be seen at: How to unlock your SIM Card Upon receiving the SIM kit (note down the PUK number and also note down the SIM PIN if available) Insert the SIM card to a Mobile device/cellular device Type in the SIM PIN from the Step 1 and Unlock the SIM Navigate to the settings page – Network section - SIM settings - SIM PIN - Disable the SIM PIN option SIM CARD SETTINGS           SIM PIN DISABLED Reconfirm if the SIM PIN is disabled by reinserting the SIM from the SIM tray and check if it asks for PIN. If the SIM PIN is successfully disabled, it will not ask for SIM PIN at startup. If it still asks, repeat Step 4. Insert the SIM inside the Gateway SIM Slot and check for network connectivity and that the gateway goes online. After inserting the SIM card properly, power up the gateway and allow the gateway to boot up. This process may take up to 5 minutes. Once completed, the device should come online and can be provisioned through a partner portal   In case the SIM PIN is unavailable An example YouTube video on the steps detailed below can be seen at: How to Unlock Sim Card / Sim locked by Pin Code or PUK Code  Insert the SIM card into a Mobile device/cellular device Type in incorrect PIN more than 4 times till it asks to enter PUK code. Contact the Network Service Provider and perform the verification and obtain the PUK Code for the SIM from the Network provider directly Type the PUK code into the mobile device in the PUK code page Navigate to the Network settings - SIM PIN - Set a SIM PIN inside the settings Use this SIM PIN to Disable the SIM PIN lock. Reconfirm that the SIM PIN is disabled by reinserting the SIM from the SIM tray and check that it does not request a PIN.

Issue The "Change set error" occurs after trying to save a LonWorks network variable binding in SmartStruxure. Product Line> EcoStruxure Building Operation Environment Workstation LonWorks Network Cause The LonWorks bindings have become corrupt and need to be rebuilt. Resolution Rebuild LonWorks Bindings Right click on the LonWorks Network. Go to Advanced > Rebuild LonWorks Bindings. Select Yes.

Issue Attempting to add a Building Operation ES license using the entitlement ID results in an error indicating that the server cannot be contacted. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Device Administrator Cause The ES computer does not have an Internet connection Resolution To activate a license using an entitlement ID, an Internet connection is required to validate with the Schneider Electric main license server. Follow these steps: Ensure Internet Connectivity: Verify that the ES computer has a stable Internet connection. Refer to Documentation: Consult the following resources for detailed instructions: How to activate, release and/or transfer a license in EcoStruxure Building Operation License server and port used to reach Building Operation licensing server Additional Information: For further assistance, visit the Schneider Electric Building Automation Knowledge Base or contact support.  

Issue The SP90 Actuator alarm "BV:22 Temperature Sensors Missing or Interchanged" is triggered. Can we simply swap T1 and T2 in the configuration to fix this, instead of physically swapping the sensors? Product Line Field Devices Environment SpaceLogic SP90 Series Smart Actuator Cause The installer has installed the temperature sensors in the incorrect pipes. Resolution Firmware versions V439 (for actuators products marked V1xxx on the product label) and V539 (for actuators marked V2xx on the product label) introduced MSV:42 (T1 input) and MSV:43 (T2 input) which enable the temperature sensors to be swapped.   You are able to select each as: 1: Disabled 2: Supply temperature 3: Return temperature   If the SP90 actuator is at a lower firmware revision, it can be upgraded. Contact Product Support for the firmware files and upgrade instructions.

Issue General Continuum instability is followed by the following error when viewing Graphic panels. "Pinpoint: Failed to call pILiveData->GetLiveData(). ACDataServices has an error." Product Line Andover Continuum Environment Continuum Cyberstation Cause Continuum has become unstable due to modules not starting up properly. This can be evidenced by looking at the Windows Application Event Logs for "Send Email" errors when alarms occur. This may then be followed by Continuum applications starting to crash and post errors. Resolution Remove "email" and "page" entries in Event Notifications if there has not been an Email client installed and configured to email alarms. Set Windows virtual memory settings to 4096. Ensure time synchronization between Cyber and CX. In Continuum General preferences set the Time Interval Between Requests to 100 (default is 30). Set COV increment for noncritical points to non-zero numbers (default is 0). Upgrade to 2.03. If already at 2.03, a reinstall of Continuum may be necessary or at least the pre-requisite 'Visual C++ 2005 redistributable'. Also refer to: Crash of ACCDataServices on start-up or run 

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue Fire Panel unable to display the Media Gateway Card version in system information. Product Line ESMI Fire Detection. Environment FFSULH1007. Cause Panel message output on Media Gateway Card TCP/IP port not functioning and impacting BMS integration with the panel.  Resolution The Media Gateway Card firmware needs to be updated. Follow the steps below to update the Media Gateway Card firmware.   Prerequisites An SD card and SD card reader is required to make a bootable SD card for the firmware update files.   Prepare the SD card The first stage to update the firmware of the media gateway card is to prepare and install the firmware file onto the SD card. The media gateway card requires a micro-SD card. The firmware file is approx. 320MB, so select an SD card with suitable memory size. Format the SD card. Open up Win32Diskimager software. You should see the screen appear below. Click on the open file tab and then select the firmware file. When the firmware is selected it will populate the image file box. Click on the ‘Write’ tab and you should then get a pop-up screen shown below. Click on the ‘Yes’ tab. The firmware will now install onto the SD card. When you see the pop-up screen ‘Write Successful’ appear click on the ‘OK’ tab. The firmware is now loaded onto the SD card. Close down the Win32Diskimager software and eject the SD card form the PC. Install the Firmware Install jumper link onto the middle and top pin of X7 (as per the image below). There is a sliding cover on the socket. First slide the cover to unlock it, then hinge it up. Place the SD-Card in the socket. Hinge down the cover, then slide it to lock it as below The media gateway must be restarted to initiate the installation of firmware. This is done by pressing the reset button, shown in the picture below. The Media Gateway card has a set of 6 LEDs that indicate the status of the card. During normal operation one of the LEDs flashes regularly once each second. After a few seconds you will see a moving pattern progressing through the six LEDs. This indicates that the installation is in progress. The installation will take a few minutes to complete. Note: During this time the panel may display a fault condition that the media gateway card is not present or not working correctly. You can ignore this fault indication. When the firmware installation on the media gateway card is complete, the pattern displayed on the six LEDs will change. Instead of a moving pattern progressing through the six LEDs, all six LEDs will flash on and off together. Once you see this pattern, with all the LEDs flashing together, you should uninstall the jumper, remove the micro-SD-card, and then press the reset button. The media gateway will restart then running the newly installed firmware. It will take a few seconds for the media gateway board to achieve its normal operating state. If the panel displayed a fault indication that the media gateway board was missing, this fault should clear. The ESMI ULTIMA panel now needs to be rebooted to accept the updates from the media gateway card.13. Once the ESMI ULTIMA panel has initialised the firmware installation is now complete.  

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue Even though the curve block is set to range between 0-100, the block just stays at a fixed output somewhere in the curve output range. Product Line TAC Vista Environment Vista Workstation Cause The curve requires the first entry of the X value to be the lowest value, and then the subsequent values to be larger than the previous X entry. Resolution Adjust the order of the XY entries on the curve block so the first entry in the X will be the lowest value. Example of Incorrect Curve Here is an example of a Curve that will not work. Note the first X entry is -2 and the last X entry is -6.  Example of Correct Curve To correct this curve, -6 is the lower number, so this should be the first X entry. Here is an example of the curve that has the correct X entry order.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Note: Always completely power OFF the panel whenever inserting or removing hardware in the panel. Issue Not able to see the network panels status, trouble messages, events, cause and effects etc. Product Line ESMI Fire Detection. Environment FFSULH1009. Cause Networking issues can significantly impact the performance and reliability of the Esmi Ultima system. This article provides troubleshooting steps to resolve common networking problems. Resolution The following network-related troubles can occur on the Esmi Ultima Fire Alarm Control Panel. See the detailed descriptions below for explanations on each trouble message.   Trouble Message Description Network Communications Trouble This event indicates there is no communication between this panel and its neighbor. This could be caused by a configuration error (such as using the wrong baud rate), a wiring error, or damage to the wires connecting the panel to its neighbor. If this trouble occurs on one link on the panel, then the panel is still in communication with other panels on the network. If this trouble occurs on both links on the panel, then the panel is no longer in communication with other panels on the network. Note: make sure remove the 0 ohm resistance from the network card. Unexpected Network Node This event indicates a panel has been detected on the network that is not in the configuration. This is a configuration error and should never occur once the network has been properly configured. Network Card Missing This event indicates that the panel is configured for networking, but there is no network card installed, or it is installed incorrectly. This trouble may also occur if the network card processor fails. Connection Error This event indicates that the panel has failed to get a meaningful result for the link impedance measurement. This may occur if stray leakage current enters the link wiring from elsewhere, or if there is a component failure or missing jumper on the network card. This event may also be shown when the network is disconnected or when the NET OUT + wire is disconnected. Network Panel Missing This event indicates that another panel is configured but has not been found on the network. This may occur if the missing panel is switched off or disconnected from the network. This fault will also occur if there is no communication between a panel and either of its neighbors on both links. In this case, the panel will show multiple instances of this trouble; one for each other panel on the network. Network Node Double Addressed This event indicates that more than one panel on the network has the same node number. This is a configuration error and should never occur once the network has been properly configured. Full Short Circuit Trouble This event indicates that a short circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. Full Open Circuit Trouble This event indicates that an open circuit has been detected by the link impedance measurement. This indicates a wiring error, or damage to the wires connecting the panel to its neighbor. The following two troubles are optional and are not included in the default firmware build. Partial Short Circuit Trouble This event indicates that the link impedance measurement has detected an impedance below the normally expected range. Partial Open Circuit Trouble This event indicates that the link impedance measurement has detected an impedance above the normally expected range.

  Issue After transitioning TAC INET Access to Security Expert, SP-C health status shows the message "Ring-loop failure at reader expander".   Product Line EcoStruxure Security Expert, TAC INET Environment  Security Expert SP-C   TAC INET Access Control Cause This message indicates that the ring-loop connection is not made.  For the ring-loop connection, the opposite end of the INET subLAN must be connected to Reader 2 on the SP-C. Resolution This message can be ignored if an INET subLAN loop is not used. The Ring-loop Failure error can be avoided by running a jumper wire from Reader 1 pin D0 to Reader 2 pin D0, and another jumper wire from Reader 1 pin D1 to Reader 2 pin D1 on the SP-C that is hosting the INET subLAN If an INET subLAN loop is used, this message indicates a break in the ring loop.    Reference Guide I/NET Access Control Transition to EcoStruxure™ Security Expert (Hardware            Guidelines for Transitioning from I/NET Page 23)

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Having issues with the panel's networking and unable to operate the touch screen or receive trouble messages on the screen. Product Line ESMI Fire Detection. Environment FFSULH1009. Cause The display touch screen may not be working. Resolution You can identify the current situation by checking the LED status as described below:    LED Status LED indicators provide diagnostic information to identify communication.   LED Label  Name  Color  Description LED 1 Heartbeat Red Identifies functional status. LED 2 Tx Comms Green A blinking green light indicates that the module is transmitting data. LED 3 Rx Comms Green A blinking green light indicates that the module is receiving data. LED 4 Trouble Yellow A flashing yellow light identifies an error condition. LED 5 Not In Use Green Not In Use LED 6 Not In Use Green Not In Use LED 7 Not In Use Yellow Not In Use LED 8 Comms for SPI Bus Green Communication present when flashing LED 9 Full Duplex Yellow Full duplex (on) half duplex (off) LED 10 Ethernet Speed Red 10MHz (off), 100MHz (on) LED 12 Communication Green Communication present when flashing   Refer to ESMI Ultima Networking Troubleshooting for further assistance with network related problems

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 It is sometimes necessary to move a previously configured Infinet i2 device from one Infinet network to another in the same parent Automation Server. EcoStruxure Building Operation does not provide an automatic way to move an i2 device; it must be done manually. Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Cause Guidance on steps to move Infinet i2 device from one Infinet network to another in the same host Automation Server Resolution In this example, we are going to move multiple Infinet i2 devices from the Infinet network on COM-A to the Infinet network on COM-B.   Backup Make sure to make a backup of the Automation Server before attempting the steps below. This is in case there is a need to revert the changes for whatever reasons. Export Devices from COM-A From COM-A Infinet network, display a List View of the devices, making sure to have columns displaying the Infinet ID and Serial Number. Write down the Infinet IDs and Serial Numbers of the devices to be moved. In the List View, multi-select the devices to be moved, right click and perform an 'Export', leave the Export Reference Filter at default (Export). After successful export, right click on the selected devices again and delete them from COM-A Infinet network. Prepare COM-B for Import From COM-B Infinet network, display a List View of the devices, making sure to have columns for Infinet ID and Serial Number. Observe the Infinet ID column, and compare with the notes taken above of the moving devices' Infinet ID, for IDs that are already in use in COM-B, you will need to assign a new ID to the device moving from COM-A Infinet network to COM-B, update your notes to include an available ID on COM-B. (see example below of what the notes might look like)   Import Devices to COM-B ***  In the System Tree, select the COM-B Infinet network and perform an import of the XML file created via export above. Physically move the devices from COM-A Infinet to COM-B Infinet. When doing so, avoid introducing duplicated Infinet IDs into COM-B Infinet. Make sure to power down the devices you are moving, connect them to COM-B Infinet, and only then power up the devices. On power up, the devices perform an ID check and stay off the bus if they detect their IDs are already in use. Configure Devices in COM-B From COM-B Infinet network, display a List View of the devices making sure to have columns for Infinet ID and Serial Number. Right click each device moved from COM-A Infinet to COM-B Infinet, and select "Properties", in the "Advanced" tab, enter the appropriate Infinet ID and Serial Number for the device then click "OK". In the List View, right click the device from previous step again, select "Device->Commission", after successful commission the device should go ONLINE Final Steps After all the moved devices are online, you should download ALL (whether moved or not) the devices to have their programs recompile and rebuild their Import/Export tables. Fix any references that were lost due to devices changing Infinet network and Infinet ID *** NOTE Due to an issue that was corrected in EBO 6.x, import may fail with error "Invalid InfinetId", the workaround for this problem is to manually create the Infinet devices on the destination port using the appropriate name, serial number and Infinet ID, then do the import selecting the option to merge on conflict.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue If you are having trouble with the screen operation, you may need to re-calibrate the touch screen. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Cause During shipping, the touch screen calibration may become misaligned. Resolution To calibrate the touch screen, do the following: Hold down the function button on the back of the main PCB and press and release the reset button, continue to hold down the function button firmly until the calibration screen appears this can take up to a minute Once the calibration screen has appeared you will be prompt with 5 crosshairs which you must press in turn. Note: Please note when pressing these crosshairs ensure you use your hand as it has been known to cause issues using tools or stationery as pointers

Issue It is not possible to login to an Automation Server and it fails with the error "Domain Controller version too low' for certain users. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Remnants of an EcoStruxure Building Operation domain exist in the controller where it has not been removed completely and it is set as the Default Logon Domain. Resolution Login with Administrative Rights: Use a user account with Administrative rights in the Local or another domain explicitly using the Domain name. Delete Partial Domain: Once successfully logged in, delete the offending partial domain. Retry Login: Attempt to log in again. Additional Information: Ensure that the domain is completely removed to avoid future login issues. Verify that the Default Logon Domain is correctly set after removing the partial domain.