Building Automation Knowledge Base

Issue Scheduled event reports exported to PDF are using the US date time format not the local systems date time format. Report settings   In the below example the Windows system, and Security Expert, were both setup for Australia regional settings with a date format of dd/mm/yyyy. The automatic scheduled reports exported to PDF were showing the US date format mm/dd/yyyy. Report export before   Product Line EcoStruxure Security Expert Environment Security Expert event reports Cause The local Windows system date settings for Welcome screen and New user accounts are incorrect. Resolution In Windows navigate to Control Panel\Region Click on Change date, time, or number formats. A new window (Region) will pop up. Click the Administrative tab Click Copy settings... Enable the following options if not enabled already. Under Copy your current settings to tick Welcome screen and system accounts and New user accounts as shown in the image below. This will copy the Current users format over to the Welcome screen and New user accounts sections. Date format settings After making the above changes the PDF reports generated now show the correct date format of dd/mm/yyyy. Report export after

Issue The following is a typical entry in a controller error log: 184 I 01/07/2012 16:02:16.19 0x00010000 0x0021a600 0x00177b9a 0x00000000 0x00000136 Product Line Andover Continuum Environment Network controllers Infinet controllers b3 controllers Cause The above entry is an indication of a clock change in the controller. Resolution 184 I 01/07/2012 16:02:16.19 0x00010000 0x0021a600 0x00177b9a 0x00000000 0x00000136 The above entry is just an informational log entry - not an error. This can be seen by the "I" after the line number 184. The three types of entries in the controller error logs are: 'I' (Informational) 'W' (Warning) 'E' (Error) It is not unusual to see the Clock Change entry a few times a day as many sites are set up with a time sync program that runs in one workstation every hour and synchronizes the WS time to the lowest ID network level controller in each network object. In this case there were dozens of entries per hour as there was a looping time sync program updating the clock whenever the time difference was >1 sec. For a program to sync time, see Time sync controllers to workstations.

Issue Having difficulties binding (pairing) room controller with MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) SE7000 Room Controller Cause Unable to make sense of LED blinks status Resolution The room controller cover needs to be removed to expose the LED located on the ZigBee communication module.   Here is a description of the LED status for Sigma Room Controllers (SE7000 Series): Blinks once: ZigBee Communication module is powered but might be defective or incompatible with the room controller base board. Blinks twice: ZigBee Communication module is compatible with room controller base board but cannot see any ZigBee network in its range that matches its own channel and PAN ID. Blinks 3 times: Room controller has joined the network successfully but it is not bound to MPM. Blinks continuously: Room Controller has joined the network and is placed in identify mode by MPM during the binding process. Blinks 4 short and 1 long: Thermostat is bound to the MPM and is communicating.

Issue Some sensors such as the SCR110-H CO2 produce a noisy signal even when wired according to the documented instructions. The following is a trend chart of the unfiltered raw signal from the sensor. Environment Automation Server Continuum controllers TAC Xenta Cause Noisy signal is typically caused by common ground wiring of AC power. Resolution SOLUTION #1 Signal noise can usually be eliminated by using an isolated transformer to power the sensor separately as opposed to using a common transformer that powers up several pieces of equipment. SOLUTION #2 For sensors that support  AC and DC input voltage, signal noise can usually be eliminated by using DC instead of AC power source to power the sensor. SOLUTION #3 Implement a Slew Rate to filter out the noise. As of version 1.7.1, StruxureWare Building Operation does not have a built-in slew rate functionality. Nevertheless, a custom slew rate can be implemented using Script programming. See HowToDebounceANoisySensorSignal.pdf SOLUTION #4 Add a filter (FILT) in a Function Block program after the signal input Description: The function block is a discrete time first order software filter. The filter time constant is specified in seconds with the Time Const parameter. The initial block output value is zero. The filter algorithm is y(k) = y(k-1) + 1 / 1+T/h (u(k)-y(k-1)) where y(k) and u(k) are the filtered and unfiltered values at time k, respectively,h is the sampling interval (i.e. the application program cycle time), and T is the filter time constant. If the time constant is less than or equal to zero, no filtering is done. To obtain a good filter function, the time constant should be set significantly greater than the application program cycle time. This filter algorithm is based on a straightforward backward difference approximation of the continuous time derivative operator. SOLUTION #5 Ensure you are not using older versions of the IO Firmware. As detailed in TPA-SBO-17-0006.00 the firmware should be at least V2.015 in the modules and is available on the Download Center.

Issue What card readers and technology can be used with Continuum Access Control Systems Product Line Andover Continuum Environment Continuum Cause Need to know what card readers will work with Continuum Access Control Systems Resolution The card reader and card technology is not relevant to the Continuum Controller, as this is used between the card (tag, fob or other) and the reader. This allows the use of the standard technologies available today, including fingerprint and other biometric based access as well as cards, fobs and tags. The signal that comes from the reader must be serial data input type Wiegand or ABA (or Clock & Data) USB, Ethernet, RS485, RS232 inputs are not accepted. NOTES The exact input type and maximum data bits can only be determined by checking the hardware, firmware and Continuum version combination being used. Retina, fingerprint, facial recognition and other biometric based systems that are connected to Continuum Access Controllers will store the biometric information and still be connected via the serial data Wiegand or ABA to the Continuum Controller. The current Continuum access controllers also accept an 8 bit burst for PIN numbers from keypads See Where can I find datasheets, install guides and other information on HID Electronic Access Control products? ABA (or Clock & Data) this was often used with Magnetic Swipe technology which has mostly been phased out Standard Wiegand Formats within Continuum Infinity 37-Bit AC 4+4 32-Bit Wiegand 26-Bit CK 34-Bit G 32-Bit HIDCorp1000 35-Bit - Some restrictions Custom

Issue Will a TAC Xenta 28x, 30x, 401 controllers do time synchronization in the Lon network? Product Line TAC Vista Environment Xenta 401 Xenta 281/282 Xenta 301/302 Cause The TAC Vista server will synchronize the time of all of the TAC Xenta controllers in the Vista database every 10 minutes by default but the time can be changed by a value greater than the Delta time setup in the Vista database and an update forced. Resolution The TAC Xenta group master will send out the time to all TAC Xenta devices in the group once a day and this time interval cannot be changed. If the time in the TAC Xenta Master is changed for example by the OP-panel it will send out the time to all TAC Xenta devices in its network.

Issue After upgrading a TAC Vista system on a site with high IT security you can end up with a wrong schema version in the SQL database causing issues such as failure to insert trend log data. Environment TAC Vista SQL Cause In some versions of TAC Vista, the SQL database upgrade carried out during the installation of TAC Vista doesn't upgrade the SQL database to the newest version. The first time you start TAC Vista Server, the server (TACOS) carries out the remaining upgrade steps. On a site with very high security standards, TAC Vista Server is however not able to apply the last SQL database upgrade scripts as those can only be carried out by the IT department directly on the SQL server, and as a result the SQL database is not fully upgraded. Resolution   1.      Note exactly what schema version the SQL database currently has This can be checked through SQL management studio with this query USE taclogdata; SELECT dbo.DSS_SchemaVersion() AS Db_SchemaVersion 2.      Note exactly what version of TAC Vista you have upgraded to 3.      Contact PSS to get a SQL upgrade script specific for the site and run that on the SQL database

Issue BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8 Product Line EcoStruxure Building Operation Environment BACnet Broadcast Device Table BBDT BDT Management BBMD Cause When a BDT is manually built (or BBMD first created), BDTE00001 is always set to the Server IP address. In the example this is 192.168.1.15 When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address. Thus the Servers BBMD BDT can be corrupted with the Server IP address appearing twice in the BDT Resolution The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade. Option 1: Change the BDT before the upgrade The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001. Option 2: Correct the BDT after the upgrade For the first Server being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries, Then manually reenter in all the BDT entries. For all remaining servers being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries From the First Server BBMD do a teach Verify the BDT table is in the Server Below would be the first upgraded Server as option 2 or a corrected as option 1   NOTES Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed. A hotfix will be available in V1.7 Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.

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 If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue Enterprise Server and the B-OWS capability Environment SmartStruxure site Cause Enterprise Server and the B-OWS capability for viewing BACnet Operator Workstation Resolution The Enterprise Server is a native BACnet/IP protocol operator workstation and controller with a built-in web server. The Enterprise Server also serves as a BACnet/IP Broadcast Management Device (BBMD). The Protocol Implementation Conformance Statement (PICS) document details the BACnet Interoperability Building Blocks that are supported in StruxureWare Building Operation. The PICS are available from the BACnet International labs for BACnet Operator Workstation (B-OWS) Continuum 1.9x The below screenshot is of a StruxureWare Building Operation 1.3 Release and the desired connection using B-OWS to a Continuum 1.94 Release. Workaround is on the BACnet Interface of the ES, highlight the IP Network then Add New BACnet Device. 1. Suggested name would be the Cyberstation Name 2. Upload from BACnet device 3. Instance ID is the Device Node ID (Right-click/Edit on the Cyberstation) 4. Create Then perform an Upload from the newly created Cyberstation. Resulting View from the Enterprise Server: (Note that Cyberstation owned objects are not available in the Enterprise Server) There is an “official” document on Continuum and StruxureWare Building Operation BACnet communication that was produced specifically for this issue. It is a TVDA produced by the Buildings StruxureLab and it is Andover Continuum BACnet with StruxureWare TVDA 1.02

Issue How to completely uninstall and remove TAC Vista 5.X.X Product Line TAC Vista Environment TAC Vista 5.1 and later versions Windows OS (Windows XP, Windows 7 tested) Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using the full SQL version not administered by TAC Vista: Backup SQL database named “taclogdata”. Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL folder Server and TAC root directory (usually C:\Program Files\Schneider Electric (note: TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead) and C:\Program Files\Microsoft SQL Server). Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove all TAC Vista hotfixes using the uninstall program in Control panel Add/Remove programs. Remove TAC Vista Server 5.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC toolpack, TAC Xbuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL Server 2005) using the uninstall program in Control panel Add/Remove programs. Delete remaining uninstalled TAC folders (usually C:\Program Files\Schneider Electric, TAC Vista 5.1.3 and prior will have path C:\Program Files\TAC instead). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server). Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. Find the registry key folder HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDll Remove all keys containing “TAC Shared”, e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \Microsoft SQL server. Reboot. If SQL Server (TACVISTA) still listed under Services, please follow steps in SQL server service cannot be started during Vista 5.X.X installation to solve the issue. See How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 for steps to completely remove TAC Vista IV.

Issue Attempt to download license and see the below error. Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B)   Failed to request license Error: Failed to store licence file Exception HRESULT:0x8007051B) (0x0000051B) Product Line EcoStruxure Security Expert Environment Security Expert Cause This error could be caused by a folder permissions issue. Usually occurring when Security Expert was installed without proper permissions to edit the folder or parent folder of where the license is stored. Alternatively it can be caused by a domain user account and local user account having identical names since Security Expert doesn’t know which user to check the permissions of when trying to save the license file. Resolution The possible solutions are shown in the order that they should be attempted: Right click the Security Expert license folder, (usually "C:\ProgramData\SchneiderElectric\SecurityExpert\License")and ensure that the Windows user has permissions to modify and view the contents of the folder. Ensure that the there is no local windows user with the exact same name as a domain windows user (e.g. LOCALHOST\admin, as well as ACME\admin). If this is the case change the name of one of the windows users so it doesn’t exactly match the other.  Perform a manual registration. Generate the .req file, go on the Licensing page, fill the form and download the license file. Then use the Browse button to import you license in Security Expert.

Issue When the Sigma client attempts to connect to the Sigma server it fails and reports an error "No Seats Available".  What is the maximum number of clients that can be connected to a server? Product Line Satchwell Sigma Environment Sigma version 4.08 Client connections Cause Sigma server is not licensed for the attempted client connection Resolution For a customers system check: 1.  The Sigma dongle is licensed for the number of clients to be connected.  From a working client see Help - About and the number of clients supported is shown in the brackets ().  The maximum allowed depends on the operating system where the OS itself limits the number of consecutive connections; Windows 2003/Windows 2008 server:  Maximum client connections is 10 Windows XP/ Windows 7:  Maximum client connections is 5 2. Run the file C:\Sigma\bin\Setupsvr.exe and check that if a local client (on the same PC as the Sigma server) that "My Computer" is ticked or for a remote client (not the same as the server PC) that the "My Computer" is un-ticked and the correct Sigma server IP Address is entered. 3. Also in the Setupsvr.exe for a remote client check that the HTTP Server Port is set the same as the Sigma server (default = 8080) 4. Close down another client to free up a seat 5. Purchase more licensed clients (seats) using ZSO_CLIENT-x (where x is the number of additional clients - max 5 for Windows XP/7 server and max 10 for Windows 2003/2008 server).  Must add the Dongle number to order.    For an engineers laptop (Local connection) running SigmaX check: 1. SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. SigmaX 7.09 no longer unlocks Sigma (or BAS2800+). To unlock Sigma you will need to install the SBO (Verision 1.5, 1.6, 1.7, 1.8 or 1.9) or EBO license administrator (Version 2.0 or later) and unlock Sigma using the current EcoStruxure Building Operation Evaluation License. The evaluation license is available to download form the Schnieder Echange Extranet web site. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. 2. If the Ethernet connections have been enabled or disabled (i.e. laptop has been with IT or wireless switched off/on) then a new SigmaX code will most likely be required. 3. Run the file C:\Sigma\bin\Setupsvr.exe and check that "My Computer" is ticked.

Issue Need requirements for email notifications Environment Continuum Cyberstation Email Eventnotification Outlook 2007 (32bit Only) Outlook 2010 (32bit Only) Cause Requirements for sending email notifications with Continuum Resolution Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have a MAPI-compliant email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book. How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook(32bit). Other mail applications may have different menu names and choices but the general procedure is the same. Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. Select New Entry from the Address Book File menu. Select the entry type Personal Distribution List and put this entry in the Personal Address Book. In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages. ** Ensure that there are not 2 PCs using the same email account for Outlook.

Issue System was running fine with EBO version 3.2.3 and Active Directory (AD) integration. But after upgrading to EBO version 2022 no AD user could login to the ES. The Workstation Error when trying to login is: User_Not_Associated_With_A_Group And the error message seen in the ES trace log is: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28).  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved in version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution If turning on the below property in the properties the old way used in EBO version 3.2.3 of matching groups during logon will be used: In the "ES.properties" file usually placed in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config add and save: NspServer.Windows.Group.MatchByName = true   To utilize the AD performance improvement in EBO 2022 re-connect the AD group to their respective EBO group. This is done by changing the "Windows group name" property in the EBO group to anything else or an empty string and then change it back to its proper value, i.e. the AD group name. Doing so should correctly populate the hidden "External SID" property for the EBO groups that is missing as the upgrade was done with no connection to the AD server.  

Issue Getting DCOM errors when trying to access WebClient and need to determine which of the various permissions have not been set properly. Product Line Andover Continuum Environment WebClient IIS Cause DCOM permissions have not been set properly. Resolution Open EventViewer, go to System Events, and note the DistributedCOM error. Open the error and find the CLSID that it is referring to. In the DCOM Config, look through all of the DCOM objects and find the one with the matching CLSID. Make sure that it has the correct permissions according the WebClient installation document. If this does not resolve the problem, you can also consult WebClient most common installation problems for further troubleshooting steps.

Issue Replacing Satchwell Sensors with Schneider Electric part numbers Product Line Field Devices Environment Sensors Cause Cross referencing older 'T' type sensors to the current version. Resolution Outside Sensor DOT2301 , DOT0001, DOT0002 is now STO600 Immersion Pipe Sensor DWT1701 (125mm), DWT1702 (200mm), DWT0001 is now STP660 (note, if replacing sensor only then DWA0001 required). Strap On/Pipe Contact Sensor DST1601 , DST0001 is now STC600 Duct Sensor (mainly FCUs) DDU1803 , DDU0001 is now STD670 Duct Sensor DDT1701 (300mm) , DDT1702 (460mm) , DDT0001 is now STD660 Room Sensor DRT3453 (sensor only, no setpoint adjust) is now STR600 For other DR and DRT sensors see Replacements for Satchwell sensors Drayton Room Sensor A701 is now STR600D Drayton Outside Sensor A702 is now STO600D Drayton Immersion Sensor A703 is now STP600D Drayton Strap On / Contact Sensor A704 is now STC600D

Issue VSB valves have been substituted by the Schneider Electric V211T valve VSB..F valves have been substituted by the Schneider Electric V211 valve VMB valves have been substituted by the Schneider Electric V311T valve VMB..F valves have been substituted by the Schneider Electric V311 valve Product Line Field Device Environment VMB VSB Cause The existing actuator is not compatible with the replacement valve as it is a different type. Resolution Schneider Electric  are no longer supplying VSB and VMB valves. They are replaced by a Schneider Electric Venta valve. Note: VSB and VMB valves are still manufactured by Controlli. VSB 2 ports are replaced by the V211T, VSB..F is replaced by the V211. VMB 3 ports are replaced by the V311T, VMB..F is replaced by the V311. The existing actuator will no longer fit on the new valve and needs to be replaced as well. If the actuator was a Controlli MVB22, MVB26 or MVB28, then replace with MV15B-230 actuator. If the actuator was a Controlli MVB46, then replace with MV15B-24 actuator. If the actuator was a Controlli MVB36, MVB52 or MVB56 then replace with M800 actuator. For compatibility: V211, V211T, V311 and V311T Venta valves are directly compatible with the Forta range of actuators e.g. M310, M400, M800, M1500, M3000, M700, MG900 and the MV15B-24/230 and no linkage kits are required.

Issue MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." Environment Continuum loaded on a Microsoft Operating System computer Cause MSMQ has become corrupt on this PC. Resolution Continuum cannot be installed on XP HOME(XP Professional only) Verify that the msmq service is started Go to Add/Remove programs > Add/Remove Windows Components does not give the option of installing Message Queuing. Go to a DOS Prompt and change your directory to C:\Program Files\Continuum\Install (cd \Program Files\Continuum\Install) Run the batch file Runafterreboot.bat (This will reinstall the Continuum version of MSMQ. NOTE: Most recent versions of CyberStation RunAfterReboot.bat has been renamed InstallMSMQ.bat Run the batch file and re-boot the machine then run Continuum ** In some cases Windows Add/Remove programs may not completely remove MSMQ and a utility like Revo Uninstaller may be helpful in getting a clean uninstall, so that a reinstall is successful.

Issue BACnet b3 or Infinet i2 controller shows version 0.000000 Product Line Andover Continuum Environment BACnet b3 Controller Infinet i2 Controller Cause The Controller is likely to be in bootloader mode, this can be confirmed by looking at the CPU flash speed. If you can count the flashes it is likely to be in bootloader mode see CPU LED flashing rate  Resolution Reflash the controller OS with the firmware compatible with the Continuum installation on site, using "Update b3 OS" or ""Update Infinet2 OS" NOTE - An ACX57 with Comm1 set to Infinet is unlikely to be able to communicate with an i2 device in bootloader mode, in this case an NC2 or other NetController may be required