The firmware updater can be found in the software under Tools -> Firmware Updater. This feature is used when a controller is not behaving as expected or is needing to be updated in its base programming. Before you begin, ensure that you are only selecting a single door, along with the correct firmware version.

There are three active firmware versions in the most recent release of BlueView. Version 3.0+ is used in legacy boards of the previous hardware iteration, while newer versions accept 5.0+ and 7.0+. When just trying to clear corrupted data or programming, simply pushing the same version that is on the board is sufficient to refresh the firmware.

Though the tool allows you to select by area, site, or company, DO NOT apply firmware updates in bulk! This can be unstable, and due to the nature of the tool, interruptions and breaks can cause damage to the functionality of the board!

Therefore, ensure that Door is selected in the first checkbox.

Next thing to confirm is network, be sure that you ping the board before attempting an update, and it is recommended to run command prompt with an active ping running alongside the updater tool.

Once all is confirmed, click Start Firmware update to begin.

Once started, the system will wipe all data on the board and begin to write lines to build the firmware. This is usually around 3000 lines and takes a few minutes. While updating, the LED on the board will turn off. Once complete, the controller will initialize, causing the LED to light up yellow for around seventy seconds as the controller reboots and initializes. 

After the initialization process finishes, the system will report a successful update. The door will automatically be scheduled with a full programming update and will upload the configuration settings along with credentials. Test the door to confirm functionality has returned.

If the process fails at the start command for any reason, you can do the following:

Check off the box for “Disable current firmware check”. The tool checks the compatibility of the firmware you are pushing as well as checking the current firmware of the board. This will bypass the check, which can often fail due to the missing or corrupted data.

You can also power cycle the board and system, along with a network reset, in order to possibly bring the door back to a state in which it can be updated. It is always recommended to directly connect a laptop to the controller’s network port to ensure the most stable connection and rule out any outside factors.