Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue Unable to log in to the report server via a web browser after successfully installing the WebReports package. No explanation is given as to why the login was unsuccessful.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Report Server Cause The most probable cause is that there is no connection with the ES. Without a connection to the ES, the Web Reports Server cannot confirm the account being used to log in is valid. Resolution Note: Report Server (WebReports) is not supported in EBO 2022 or higher.   Test the connection with the ES On the same PC as the ES is installed on, try logging on via Building Operation Workstation. If this is successful, try logging on to the Enterprise server from the same server as the Web reports server is installed on. To check the URL and port settings, open the Software Administrator on the ES server PC. If step 2 (above) is unsuccessful, go to step 3. Otherwise, go to step 4. Check the firewall setting on the 2 PC,s. Ensure that the ports used by the ES (Check the Software Administrator for information about ports) and the Web Reports Server are not blocked. Re-run the WebReports Installer (link to documentation). Pay particular attention to the Reporting agent section. Make sure that the Enterprise Server URL and port number are the same as that shown in the ES' Software Administrator. Once installation is complete, logging in to the WebReports web server should be possible. If there is still no contact with the ES the network should be checked. A network protocol analyzer (such as Wireshark) can be used to identify the cause of the problem.

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue TimescaleDB Installation Errors - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% - ERROR: could not get 'pg_config --pkglindir' : exit status 1 Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.x External Log Storage TimescaleDB (third party)  Cause Missing environment variable paths in Windows is detailed in section 9.4.4 PostgreSQL and TimescaleDB Installation in the EcoStruxure Building Operation 3.0.1 Release Notes. Assistance in how to add these variables is described below. Resolution Using the EBO External Log Storage Installer tool available on the Community, there is no need to make any manual configuration, as the tool executes the installation without the need for e.g. environment variables. Alternatively, you can manually set these as detailed below: You can either view a video showing how it is done:  or follow the instruction below view, add and modify the environment variables from the Control Panel as follows:  In the Control Panel select System and Security Select System Select Advanced system settings Select Environment Variables. In System variables, highlight Path and click Edit. For the error - ERROR: could not get 'pg_config --pkglibdir' : exec: "pg_config": executable file not found in %PATH% Add the New path 'C:\Program Files\PostgreSQL\11\bin' to the environment variable. For the error -ERROR: could not get 'pg_config --pkglindir' : exit status 1 Add the New path 'C:\Program Files\PostgreSQL\11\lib' to the environment variable. You should see something similar to the following after TimescaleDB has been successfully installed.

Issue SmartStruxure uses two different function block programs. Menta Editor is used for Xenta programmable controllers while Function block editor is used in the Automation or Enterprise server. The two programs are not interchangeable and do have several differences. Product Line EcoStruxure Building Operation Environment Function Block Editor Menta Editor Cause There are several differences between Function Block Editor and Menta Editor that are important to know. Resolution Download the relevant version of the Function Block Editor and Menta Editor Difference Guide from Exchange. This guide will cover the following topics: An overview of Function Block programming The programming differences Function Block Editor and Menta Editor differences Program Conversion Importing Xenta programmable controller programs Building function block programs to I/Os Binding values Binding values using a binding template Time schedule and alarm blocks Trend logs Overview of Function Block Editor Block differences

Issue TAC Vista interface stops  Environment Vista StruxureWare Building Operation TAC Vista SmartStruxure Interface 1.0.0  Cause When acknowledging an Vista alarm in SmartStruxure, the TAC Vista SmartStruxure interface stops.  Resolution Please download and install the latest Vista hotfix versions for your system from the Exchange.

Issue What are the limitations of Building Operation Web Services? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Version 1.3 Cause Due to the XML response rate (XML file information send to Building Operation), it has some limitations. Resolution General Guide in the Technical Reference Guide: The limit for the whole XML response is 100 kb, which includes manually created values. The limit for a string value is 10 kb, which includes manually created values. The maximum number of values created in the Web Server interface is 200. The recommended limit for XML elements in the Web Service interface is 100 The recommended number of Web Service interfaces in an Automation Server XML elements at a polling rate of 60 seconds. is 2. Additional Information: Maximum number of Web Services in an Automation Server Also refer to Architectural Guidelines for your respective version in use.

Issue StruxureWare for Building Operation User Interface Matrix Environment SmartStruxure Cause Need information about which User Interface Option has which features Resolution You can download the User Interface Matrix from The Exchange Download Center: User Interface Summary

Issue LNS plug-ins are needed in order to configure certain application specific controllers. Product Line EcoStruxure Building Operation Environment Workstation Open LNS Server Cause Many application specific controllers can be configured through Workstation but this can be very time consuming. Starting with Version 1.4.0, SmartStruxure is now able to support LNS plug-ins. Key points and features Click SBO v1.4 Activation Key for OpenLNS Server - SmartStruxure solution - PA-00285 to download the StruxureWare Building Operation v1.4 - Activation key for OpenLNS Server product announcement. Echelon OpenLNS Server must be installed on the computer that plug-ins will be used. LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC STR 350 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure TAC Xenta devices using TAC 100 plug-in 5.1.9 or later. (earlier versions won't work) LNS Server plug-ins can be used at the workstation to configure third party LON devices. The LNS plug-in capability will only work if the device does not require to be online to configure. If the manufacturer's plug-in requires active communication with the device then the plug-in implementation will not work. StruxureWare Building Operation database is automatically updated to any changes created with the plug-in. Resolution For LNS plug-ins to work in SmartStruxure, Echelon OpenLNS Server must be purchased and installed on the computer where plug-ins will be used. Purchasing Echelon OpenLNS Server An activation key must be purchased in order to install Echelon OpenLNS Server. The activation key is available to purchase through Schneider Electric using the part number SXWSWLNSX00001. The activation key can be purchased through standard product ordering procedures. After ordering, the activation key will be sent to you via email within a few days. Installing Echelon OpenLNS Server WARNING: You can not install OpenLNS Server on the same computer as TurboLNS without upgrading Turbo to Open. You will now be converting any TurboLNS databases to OpenLNS if they are opened on this computer. Once you have purchased the OpenLNS activation key and received it via email from Schneider Electric then you can now install Echelon OpenLNS. Double click on the executable to start the OpenLNS install wizard. Click Next. Select 'I accept the terms in the license agreement' and click Next. Fill out the information and enter you activation key. Click Next. Click Install. Click Next. Click Finish. NOTE - At step 7 above, if the PC is not connected to the internet, the registration may require an email to be send manually to Echelon to register the licence code.  Uninstalling Echelon OpenLNS Server Make sure you reference the OpenLNS Server License Guide here for information on how to return the OpenLNS license in order to use it again.   Registering LNS Plug-ins Note: Before registering LNS plug-ins, they must be installed on the computer first. If working with TAC Vista Xenta 100 and TAC STR 350 controllers, the plug-ins must be version 5.1.9 or greater. ZBuilder is included in the TAC Vista 100 download. These can be downloaded off of the Extranet in the same place as the SmartStruxure software. See LNS plugins for SmartStruxure 1.4 are not included in the release, but downloaded separately for more information. In SmartStruxure Workstation, go to the Control Panel. Click on 'LNS Plug-in Registration'. In the 'Available LNS Plug-ins' field, select the plug-ins you want to register and then click the right arrow to move to the 'Registered LNS Plug-ins" field. Click the save icon on the System tab. Note: If registering the TAC Xenta 100 plug-in, you will be prompted to select the devices you want to register. Then click OK.   Using the LNS Plug-ins Note: All changes made in the LNS plug-ins are offline configuration changes. The LNS plug-in support in SmartStruxure will not support devices that are required to be online for plug-in use.  Right click on the controller, click Configure... The LNS server is checked for a matching device template and the current device configuration is saved to the LNS server. Click Next. Double click on the plug-in listed in the window. This will launch the LNS plug-in. Make configuration changes to the controller and then save or exit the plug-in. Click Next. Click Next. The configuration changes that have been made will be listed in the window while they are being saved to the LNS server. Click Finish. Now the configuration changes that were made in the LNS server need to be downloaded to the controller. Right click on the controller in Workstation and select 'Download device configuration'.

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 Straight S-Cable and angle (L-shaped) S-Cable difference Product Line EcoStruxure Building Operation Environment Automation Server Automation Server Power Supply Automation Server I/O Modules Cause The description in the datasheets / installation instructions may not be sufficient to understand the difference(s) between the two types of S-Cables. Resolution January 2013 Update - The straight connector S-Cable has been discontinued. Refer to Product Announcement PA-00238 for details. The straight S-Cable (part number SXWSCABLE10001) and the angle or L-shaped S-Cable (part number SXWSCABLE10002) works the same in terms of functionality. Both are 1.5 meters in length. The difference is whether the connectors is a straight out type or an angled type. This will probably affect the installation. See the images below Straight type Angle or L-shaped * Note: The straight S-Cable is currently not available and all existing and coming orders for straight S-cable (SXWSCABLE10001) will be replaced with the L-shaped S-cable (SXWSCABLE10002) until further notice. Refer to TPA-SBO-12-0004 01 for details.

Issue Software Licensing for Continuum 2.0 & StruxureWare Solution Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Site integration with the StruxureWare Solution Continuum Cyberstation software & Licensing Cause Request for Software Licensing compared to the Hardware key.  Resolution There is a Ordering and Activation document available on the Buildings Exchange Download Center. A link is provided below: Ordering and Activation of Software License for Continuum v2.0 Software license is a dedicated license per workstation and locked to both the hardware and the operating system. Recommended not to install on old hardware. Software licensing is available for both new and existing installations after Continuum 2.0.  A Hardware key is required in order purchase a software license.  This is because the Continuum features and options are purchased with the physical Hardware key, not with the keyless license.   When purchasing the Keyless license, the serial number of the Hardware key is submitted along with a License Information file (c2v) that has been created on the workstation that is to be licensed.  The License Information file is created using the Hasp Key Utility.   Continuum installations pre version 2.0 (e.g. v1.94) who wish to upgrade to v2.0 and would like to benefit from Software Licensing feature must download and install the required files. Those are outlined in the document above. Note: For Continuum Interface for SmartStruxure Solution the demo StruxureWare Building Operation license has all required features. Your Continuum 2.0 key must have the Advanced Webserver feature enabled.You can use the Continuum Interface Server for any Continuum installation: Standalone or Multi-User (LAN). All existing Andover Continuum configurations are supported in the Continuum Interface Server.  

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue Unable to activate the AD-Link on a SmartX Advanced Display Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V1 Building Operation Advanced Display V2 Cause Changes to the license server made current AD-Link software inoperable Refer TPA-SBO-17-0009.00 for details about the issue Resolution Note: Advanced Display V1 is discontinued. Effective July 31, 2023, Service Support for Advanced Display v2 will also be discontinued. The licensing server responsible for activating AD-Link and Kiosk features will be decommissioned. After this date, no new Advanced Display v2 could be commissioned as the mentioned server will be decommissioned. Advanced Display V3 can replace it. Refer to: PA-00923   The issue is solved in a new version of AD-Link To install a new version of AD-Link, there is a need to first uninstall the old version of AD-Link Go to the settings page on the SmartX Advanced Display Tap on "General" Tap on "Security" tab Tap on "Device administrators" Un-tick the AD-Link Uninstall the old AD-Link app   You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app You will first need to uninstall the old version of AD-Link. To uninstall the old AD-Link you will need to un-tick the AD-Link in the device administrators tab,   In the settings page you will be able to go to the "General" tab and then "Security" tab, then "Device administrators"  In there you will see the AD-Link, untick it.  You should now be able to uninstall the old AD-Link app

Issue A Xenta 102-AX accepts a 0-5V input on all external inputs. If Universal Input 3 is designated as CO 2 , the range of the input needs to match the range of the sensor. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Universal Input 3 CO 2 sensor Cause The default setting (a gain of 1/1) results in 0V = 0ppm 5V = 1023ppm (1023 is a resolution of the onboard analog to digital converter.) Resolution Refer to page 3-66 of the TAC Xenta 102-AX Software & Hardware Manual for more detail. Calculate the required gain for the range of the CO 2 sensor. Ensure the sensor outputs a 0-5V signal. Note the CO 2 level at 5V. In this example, 2000ppm. Divide the maximum CO 2 reading by the analog to digital converter bit resolution (1023). Multiply the result by 1000. (2000 / 1023) * 1000 = 1955 Locate the value for Universal Input 3 SCPTgain. There are four locations to alter this value: Xenta 102-AX Plug-in Go to the Browser Tab > Xenta102AX > UnivIn3 Sense > SCPTgain > multiplier. Over on the right, enter in 1955/1000 and hit Set Value. LonMaker or LNS browser Open the browser window by right clicking on the 102-AX in the drawing and selecting Browser. Look in the Functional Block column for UnivIn3Sense. In that category is a point called SCPTgain. Click on it and then enter up top 1955/1000. Hit the red down arrow to download the value to the device. Enable monitoring on the nvoCO2sensor value or reopen the browser to view the new CO 2 value. Vista Workstation Go to the 102-AX.UnivIn3_Sense module and locate the SCPTgain point. Double click it. By Multiplier enter 1955 and by Divisor enter 1000. StruxureWare WorkStation Go to the 102-AX and click on UnivIn3Sense module and in the Variables tab locate the nciGainUIx point and expand it. For Multiplier, enter 1955 and save. For Divisor, enter 1000 and save.

Issue Cannot see a SE7300 Room Controller when connected to a BACnet MS/TP network. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7000 Series SE7000, SE7200, SE7300, SE7600, SE76x7 Ex Viconics branding VT7000 Series Viconics room stats with BACnet communications Cause Units are shipped from the factory with the BACnet network disabled. Resolution Power up the unit. Press the middle button down for 8 Seconds (It is either the Override or °C/°F Button depending on model). Enter the password if it has been set, or leave as the default 0 for no password (as shipped from the factory). Use the down key to find the "Comm Addr" value. By default this is set to 254 BACnet communications disabled. Adjust this to the desired value within the valid range of 1 to 127, but also ensure it is in the range of your BACnet Max Master setting on the connected system. Once set, power off/ on the unit to change the address to the new value. The unit should now be visible on the BACnet MS/TP network.    Note: The SE7xxx Room controllers will auto baud to match your MS/TP network, there is no baud rate setting to adjust. Also any password set on the SE7xxx controller must be temporarily disabled to allow the middle button to operate correctly. For further information on installing the Room Controllers please see SE7000 Series Installation Instructions.

Issue Upgrading  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Guidelines for upgrading to higher releases Resolution Non-Sequential Upgrades: Versions 1.9.1 and Newer Starting in version 1.9.1, non-sequential upgrades can be performed from versions 1.5.X and newer. Please refer to the "Upgrading" section of the Release Notes for the software version you are upgrading to. The "Upgrading" section will direct you to prior release notes that you need to read through before upgrading and point out items with limited runtime compatibility during the upgrade process.  NOTE: If upgrading a system at 1.5/1.6/1.7/1.8 with LON devices, please be aware that there are special steps that must be taken to prepare the database for upgrade. These steps can be found in the Release Notes as well.  Sequential Upgrades: Versions 1.8.1 and Older For versions 1.8.1 and older, the upgrade process is sequential. In other words 1.2.0, 1.3.0, 1.4.0, 1.4.0.4020, 1.5.0, 1.6.1 The upgrade process can be found in the System Upgrade Reference Guide. The primary released versions were 1.0.0.161 1.1.0.362 1.2.0.767 1.3.0.938 1.3.0.10100 SP1 1.3.0.20011 SP2 1.4.0.4020 1.4.1.68 1.5.0.532 1.6.0.250 (RC) 1.6.1.5000 1.7.0.255 (RC) 1.7.1.89 The minimum upgrade path would be: 1.0.0.161 Official Release 1.1.0.362 Official Release 1.2.0.767 Official Release 1.2.0.2207 1.3.0.938 Official Release 1.3.0.10100 1.4.0.4020 1.4.1.68 Official Release 1.5.0.532 Official Release* 1.6.1.5000 Official Release 1.7.1.89 Official Release Note: On one site, the AS would not upgrade from 1.5.0.532 to 1.6.1.5000. Going to the 1.6 RC resolved the issue.   1. In order to upgrade to 1.5 the site must be at 1.4.0.4020 or higher. Some sites may be still running at 1.4.0.818, which was the original 1.4.0 release. Although this is not officially supported and will not be tested, it is likely to experience the same upgrade as one from 1.4.0.4020. 2. An upgrade from 1.4.0.4020 to 1.5 will NOT offer any runtime compatibility, while an upgrade from 1.4.1 to 1.5 will offer runtime compatibility. Consequently, for a site to maximize its operational status through the upgrade, we have two different upgrade scenarios as described below. a. 1.4.0 to 1.5 – this process flow is designed to allow as much of the plant as possible to continue to operate through the entire upgrade. For the first three steps of the process the Enterprise Server will continue to aggregate the alarms from all of the 1.4.0 Automation Server. Once the halfway mark is reached the Enterprise Server can be upgraded and will begin to aggregate the alarms from the 1.5.0 Automation Server.              i. Upgrade one WorkStation in order to be able to communicate directly to any of the 1.5 Automation Server that are upgraded in b below.             ii. Upgrade 50% of the Automation Server             iii. Upgrade Enterprise Server and all but one WorkStation             iv. Upgrade the remaining Automation Server             v. Upgrade the remaining WorkStation b. 1.4.1 to 1.5 - In this process, we can take advantage of the support for runtime compatibility and the Enterprise Server will receive alarms from both the 1.4.1 and the 1.5 Automation Server.             i. Upgrade Enterprise Server and all but one WorkStation which can be used to talk directly to unupgraded Automation Server if configuration changes are needed             ii. Upgrade Automation Server             iii. Upgrade final WorkStation Note: some sites have experienced issues with the ES restart after upgrade because of the .Net Framework 4.5 upgrade and port 80 usage. Adjusting this port to an available port resolves the problem. The conversion log may indicate an upgrade warning similar to warning shown below, this warning can be safely ignored, and furthermore the upgrade program corrects the problem in the 1.5 database.           :02:11  WARNING:      Property PFE202_PF601.SI in (~/BACnet/Application/ELE/GRAPHIQUES/ECLUSES CD S4/PORTES_CE_S4) is not defined in the new system, skip           PFE202_PF601.SI. <script src="chrome://dce.addin/content/content_javascript.js"> </script>

Issue There are "Local Network: and "By Network" options that allow to just connect to the local network or just a b3 Environment RoamIO2 Bacnet Windows7 Windows 2008 Cause By default, the RoamIO2 Bacnet Service Tool has "Local Network" and "By Network" options which may attempt to access all bacnet devices across the entire bacnet network depending on what is selected. This includes all controllers connected to a routing device (BCX/AS/ES). The amount of controllers and the size of the network can cause a long delay in bringing up controllers. Resolution Ensure that the RoamIO2 firmware has been updated to V1.110002 or greater. This version introduced the "Local network" and "By Network" selections in the Bacnet Service Tool. Download details of the Network Targeted Search with snapshots Download the firmware RoamIO2Appl2.000002) Download the Bacnet Service Tool and user guide(1.110003) (Download Center)

Issue A TAC Xenta programmable controller has issues, and more information is needed to analyze what is happening in the controller. Product Line EcoStruxure Building Operation Environment TAC Xenta 280 TAC Xenta 300 TAC Xenta 401 XentaErrorLogViewer Cause The TAC Xenta 280, 300 and 401 series has an internal Error Log, that in some cases could give more information about the way the device is acting, storing restart reasons etc. Resolution The XentaSystemErrorLogViewer is used to read out the internal error log file from a TAC Xenta 280, 300 or 401 device. The XentaSystemErrorLogViewer is a program that runs in your PC, and you have to connect to the TAC Xenta device by the use of a serial cable. You must have at least the same version number of the XentaErrorLogViewer as the device you want to read the information from. Please note that the XentaSystemErrorLogViewer program only works with released version of the TAC Xenta 280, 300 or 401 devices. 1. Download XentaSystemErrorLogViewer 2. Install the program 3. Connect the TAC Xenta to the PC using the TAC Xenta programming cable. Refer to the cable guide for further information. 4. In "Preferences", select the COM port to which you connected the serial cable 5. Check "Write System Error Log to file" 6. Click "Get new information" 7. The information is written to "C:\Windows\Temp\XentaSystemErrorLogg.txt"