Issue Create a report of all expired cards Product Line EcoStruxure Security Expert Environment Security Expert Controller 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 A custom report and its configuration are needed to find all expired cards at the site Resolution This video demonstrates how to create and configure a report to find all expired cards in a system   Create a User Report: 1. In Security Expert Client, go to Reports|Setup|User and Add a new (or use an existing) report. 2. Configure the desired Report Type and Sorting 3. Go to the Columns tab, click the Add button and select Columns.  Make sure to have: -Expiration date of badge AND/OR Expiry date 4. Save your report   Please note: The "Expiration date of badge" column pulls the date from Users|Users|Extended Tab|Expiration date of badge. The "Expiry date" column pulls the date from Users|Users|General Tab|User expiry date/time section's End date.   Customize the User Report's layout: 1. Go to Reports|Setup|User| General Tab| Default user report filter and click the "Edit in report view" button 2. Right-click "Expiration date of badge" (or "Expiry date") column and select the Filter Editor 3. Change the "And" condition (in red) to "Or" 4. Change Equals to DateTime Operators: Is Yesterday 5. Click "+" sign in green circle to a line and repeat changes 5 more times for the following: - Is Earlier This Week - Is Last Week - Is Earlier this Month - Is Earlier This Year - Is Prior This Year 6. Click Save Report Layout

Issue How to properly configure Time Zone and UTC Offset settings in Cyberstations and controllers. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Controllers Cause There are a number of locations for time configuration settings, creating uncertainty as to what needs to be set, and where, to maintain the correct time in all devices. Resolution How to sync controller time with WS time with Server time. Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and regional settings are correct. [This has no effect on time synchronization but does have an effect on what time alarms and events are written to the database as well as when alarms will be delivered to Cyberstations] Confirm the SQL Server PC time zone (GMT settings) and regional settings are correct. [same as 1 above] In Continuum, the Workstations Device object's Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes.) In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note1: To synchronize controller time to Workstations time a program needs to be created in one WS that sets the Date object of the Netcontroller (IP level controller) with the lowest ACCnet ID. This controller will then push any time changes out to all other IP level controllers and down to its subnet controllers (i2’s or b3’s). See Time sync controllers to workstations for details on this. Note2: At 38 minutes past the hour the Netcontroller will push its time down to its subnet (aka Field Bus) controllers. Note3: When time is set in the Netcontroller with a reload of the controller, the UTC settings of the WS doing the reload, and the Network folder the controller is in, are accounted for and the controllers time is set with these UTC settings taken into account. When time is set with a PE program using the WS Date object, this does not take into account the UTC settings of the various locations and just sets the controller Date object to the exact value of the WS Date object. If the controller is in a different time zone than the WS setting its time, then it will now have the wrong time in it. To compensate for this, it is suggested that time offsets must be added to the Time Sync program to accommodate those networks in a different time zone than the WS. Other UTC setting locations and what these settings effect IP level BACnet Device UTC Offset The UTC offset value on the Time tab of the BACnet Device object is only used when the BACnet time synchronization method is being used to set time. This setting then follows the BACnet specification where it needs to be the negative value of the GMT setting. For example, if the BACnet device is in the GMT+10 time zone, then set this offset to -(10*60) = -600. Note4: If using the PE program method, the UTC offset value on the Time tab of the BACnet Device object does not change how time is set in the controllers. However, if the UTC offset value on the Time tab of the BACnet Device object is changed, it will change the current time of the controller to coincide with the new time zone until the time is set again in the controller, or the UTC offset value is removed. UTC offset in controller configuration Time Settings webpage This doesn’t change how the time of the controller is set. It is used to set the time of sent email messages when using the SMTP option on this controller.

Issue Time Zone and DST when syncing time to an NTP server Time differs from NTP server with x hours. DST is not following NTP server time. Environment TAC Xenta 701, TAC Xenta 711, TAC Xenta 731,TAC Xenta721, TAC Xenta 511, TAC Xenta 527 NTP server Cause NTP provides UTC, no information about time zones or daylight savings ( DST)  is sent. So if you don't set the correct time Zone and DT settings the time will be set to UTC time in the device. Resolution Log in to Xenta server Go to  Configuration- Time- Regional Settings Set correct information

Issue Pins 4 through 7 across the top of the Automation Server are labeled as "Operator Panel" although there is not an Operator Panel part available. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Cause There is no explanation of what the AS Operator Panel contacts are for? On front of AS:  Operator Panel Terminals Term 4 RET Internally connected to ground Term 5 10V 10 VDC max. 120 mA Term 6 Tx/Rx+ RS-485 communication Term 7 Tx/Rx- RS-485 communication Resolution At one time there were plans to create an Operator Panel so terminals were reserved on the Automation Server for local OP connection, however, these plans were not implemented. The next generation Automation Server Premium (AS-P) does not have the Operator Panel label, and today most operators use Webstation or Workstation.

Issue The Insight Sensor and Multi Sensor Ambient Light Sensor require calibration before they can be effectively used. Product Line EcoStruxure Building Operation. Environment Insight Sensor. Multi Sensor Cause When setting up a new Insight Sensor or Multi Sensor device, the default settings for Gain and offset may result in inaccurate readings. Calibration is necessary to ensure accurate data collection based on the specific installation area. Resolution To perform the calibration, the following two tasks need to be carried out manually: Calibrate the Light Sensor: Conduct the calibration process in an environment without any daylight for optimal results. Set the light to 100%. Measure the lux level at the reference point using a lux meter. Adjust the gain settings on the sensor to match the measured lux level. Linearize the Feedback Signal: In some cases, lights may not provide a linear feedback (lux level) as the output increases. To compensate for this non-linearity, the signal from the controller is linearized before being sent to the output. During the optimization phase, the controller incrementally increases the output in 10% steps, measuring the adjacent lux levels for each step. The maximum lux supplement is calculated by subtracting the lux level at 100% output from the lux level at 0% output. After the optimization phase, breakpoints are determined and verified by re-running the test. If the results fall within the maximum difference limit compared to a linear signal, the calibration test is considered valid. Remember, performing the calibration process without any daylight present will yield the best results.  

Issue SPP920 Datasheet, Technical Information and Installation Instructions Product Line Field Device Environment SPP920 Differential Pressure Switch Cause No information available for the SPP920. The Sensor catalogue says it is supported by Huba. Resolution Either click link www.hubacontrol.com and search for 630. or the Technical information can be downloaded here. Installation Instructions can be downloaded here. Mechanical connections are: P1 = High Pressure (discharge/flow), P2 = Low Pressure (suction/vacuum) All of the various pressure range options come with the following options: - EPDM diaphram material - Brass Case - Spec Cover PG9 - IP65 Rating - Bracket Type A

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue In BAS and Sigma, what batteries and PSU cards can be used in a x96 controller.? Product Line Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue What features are included in Building Operation evaluation (demo) licenses? Product Line EcoStruxure Building Operation Environment Building Operation evaluation license Cause The features included in evaluation licenses are not shown in the documentation. Resolution License Administrator (Software Evaluation License) After adding the evaluation license in License Administrator,   Click on the "Diagnostics" Tab. Click on "Refresh the list". Local licenses list generates. Example of generated list: Local licenses: -------------------------------------------------------------------- Trust Flags: FULLY TRUSTED Fulfillment Type: TRIAL Status: ENABLED Fulfillment ID: LOCAL_TRIAL_FID_498 Activation ID: SC_57LRIHRFBOXC28SGYTPKCH98WIRKMWE Product ID: NAME=EcoStruxure Building Operation Demo License;VERSION=5.0 Suite ID: NONE Expiration date: 01-Feb-2024 Concurrent: 0 Concurrent overdraft: 0 Hybrid: 0 Hybrid overdraft: 0 Activatable: 1 Activatable overdraft: 0 Repairs: 0 Feature line(s): server.mssql (Version 5.0) client.zoning (Version 5.0) client.dashboard (Version 5.0) server.ec.auth.saml (Version 5.0) server.ws.generic.consume (Version 5.0) server.dig.signed.docs (Version 5.0) server.alarms.snmp (Version 5.0) server.ec.es (Version 5.0) server.device.es (Version 5.0) server.ws.ews.history (Version 5.0) Sigma.Server (Version 4) server.mqtt.rw (Version 5.0) graphdb.base (Version 1.0) server.esignature (Version 5.0) server.enterprise.base (Version 5.0) server.ws.ews.consume (Version 5.0) client.cad.import.tool (Version 5.0) smartdriver.license (Version 5.0) server.timescale (Version 5.0) client.script (Version 5.0) server.es.as (Version 5.0) client.graphiceditor (Version 5.0) server.device.as (Version 5.0) server.ws.ews.serve (Version 5.0) server.es.auth.saml (Version 5.0) server.enterprise.central (Version 5.0) client.functionblock.view (Version 5.0) client.station (Version 5.0)   Refer to the Webhelp EcoStruxure Building Operation Software Feature License String Description topic for an explanation of the license feature strings. Device Administrator (Embedded Evaluation License) After adding the evaluation license to the Device Administrator (see the article How to activate a demo license on an Automation Server at EBO 2022) follow the steps to view the available features: Click on the Entitlements. Click on Product Licenses. - The individual features are then shown as column headings The best way to see all the features available is to right-click on the license name under Product Name and choose Add/Remove columns.   A Select columns popup is then shown, and the available features are much easier to read.  

Issue Unable to find the latest firmware for ADv3 in EcoXpert Extranet Product Line EcoStruxure Building Operation Environment Advanced Display v3 (ADv3) Cause The firmware is not publicly posted since the process to load the firmware should not be attempted without guidance from Product Support. Resolution All customers must to open a support case to receive fixes or enhancements.

Issue A new Automation Server won't load in Device Administrator versions earlier than EBO 2022. A "Failed to process USB connection event for DevicePath:\\?" error is shown when adding the device.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server AS-P with Secure Boot Building Operation Automation Server AS-B Scalable Cause Secure Boot/Scalable Automation Server hardware is not supported in EBO versions prior to EBO 2022. Resolution It is not possible to install EBO versions prior to EBO 2022 in Secure Boot/Scalable Automation Server hardware. Verify the Automation Server part number to ensure it is a non-scalable/non-secure boot version. Refer to the Part Number and Hardware and Software Matrix for a list of parts numbers and their associated EBO version compatibility.

Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue Can the EasyLogic range of controllers & RP-IO Modules work under Building Operation 3.2 as BACnet MS/TP third-party devices  Product Line EcoStruxure Building Operation Environment EasyLogic Controllers, EasyLogic RP-V, EasyLogic RP-C, EasyLogic MP-C EasyLogic RP-IO SpaceLogic Advanced, Pro, and Pro Plus Controllers that support native BACnet MS/TP (via a SpaceLogic RS-485 Adapters.   Standalone BACnet field controller Cause The documentation states that EasyLogic Controllers can be used as a Native BACnet MS/TP device. These devices must be configured using their respective supported Building Operation versions, such as Building Operation 2022 and above. However, there are no guidelines on whether they can be used as a third-party BACnet device, particularly in earlier versions such as Building Operation 3.2.    Resolution EasyLogic controllers can be used as BACnet MS/TP third-party devices in Building Operation 3.2 since the EasyLogic range of RP and MP controllers, and RP-IO I/O modules, natively communicate using the BACnet MS/TP protocol.  This same concept applies when using the devices as true 3rd-party devices (e.g., with Continuum and I/A systems) when older controllers fail, and these EasyLogic controllers are used as temporary replacements before a complete transition.   What MUST be understood before taking this approach is that there is no automatic conversion when migrating the site (and devices) to later Building Operation versions that support these devices natively. After the upgrade, the controller must be deleted from the database and hosted as a native EBO controller.   During this process, some programming may be lost. This risk may be mitigated by creating Custom Types for the application once engineered in Building Operation 2022 (or higher) to future-proof the site for upgrades.  Using the latest firmware for the EasyLogic range of devices is also recommended.     Furthermore, the SpaceLogic Controller Range that supports native BACnet MS/TP (via an RS-485 Adapters) can be configured in the same fashion as described for the EasyLogic range.   Refer to Hardware Overview for further details on each product line. 

Issue DHCP server is required to assign addressing to IP devices Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Jace 8000 I/A Series ScheniderMPx Modules Building Operation Multi-purpose VAV  Building Operation Multi-purpose Controller Building Operation Room Controller (RPC) 24 V Building Operation IP-IO Cause When working with the SchneiderMPx modules for engineering Spacelogic devices, the Jace can be used as a DHCP server for the field devices. Resolution This video discusses how to; - Configure the second IP network port for DHCP server use - Add an additional IP Port to the Jace station  

Issue After setting up a REST gateway in SmartConnector, how can it be tested to see that it is working using the built in test client called Swagger? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central SmartConnector   Cause Swagger is a built in test REST client which can be used to read and set values in EBO. So it can be used instead of a "real" REST client to test the REST gateway in the SmartConnector and test that the connection between SmartConnector and EBO is working. Resolution The objective in this video is to set up a REST gateway in SC and show how we can test that the gateway is working using the built in test REST client called Swagger. Please see video.

  Issue Cannot communicate to an ADV3 connected to the USB port of an AS-P or AS-B. The error message “Website not available” is displayed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display v3 (AD v3) Cause The AS-P or AS-B’s USB port uses a IP network connection to the ADV3 that defaults to 192.168.42.116. If the AS-P’s primary port is in the same range, for example the main LAN network range is 192.168.42.* there is a conflict with the USB IP network. Resolution Change the sites main LAN, which the AS-P or AS-B primary port connects too, to another network range.

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue Valve Flange Tables Product Line Field Devices Environment Valves Flanged Gaskets Bolt holes PN rating PCD Cause What flanged tables are used with what valves? Resolution The PN of the valve and the valve size will indicate the diameter, PCD (Pitch Circle Diameter), number of bolt hole/size and bolt size and therefore size of flange and gasket. Download the flange tables for BS EN 1092 (metric), ANSI  (ASA) and BS10 or here for an alternative flange table document.

Issue Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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. Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)