NOTE: For the TLS 1.2, it is recommended to plan to swap to an EAPro-Gateway device by August 2025
Verify your current settings.
To check the current firmware and bootloader on your device.
- Main menu > About EA800
Under the large EA800 Logo, there will be a long S- Number. The end of the number will give you your current firmware. In the image below, the current version is C.15g.
Note: Winland recommends staying on C.15F until August 2025, when it's time to replace the unit if INSIGHT connection is still required.
2. To check the bootloader, you must reboot the device. While it's rebooting, you will see the Winland logo, which will also have the bootloader version in an IP=X.X or IP-X.X format. The image below shows the bootloader as version A.6
Please ensure you backup all data and configurations prior to updating the firmware.
To upload the firmware, you will need:
A USB (Smaller than 32GB. The EA800-ip will not read any USB that is beyond 32GB).
Upload the 3 follows files to the USB
- IP800.BIN
- IP800_A6.UPB
- IP800_1.2TLS_C15f.UPD
Once you have the 3 files above on the USB, connect the USB to the EA800-IP
To navigate to Update Firmware;
Unlock Device > Hit Main Menu > Go to system > then Update Firmware > Select:
IP800_1.2TLS_C15f.UPD
If done correctly the device will validate update, then you will see the confirmation screen (see below).
Hit OK to apply update.
Note on your device you may see C.15g and not C.15f. That is not issue, continue with the update.
Memory clearing must be done after a firmware update
Constant Bootload Errors
If you find you are having the device reboot on its own. There might be a bootloader or a firmware issue. You will need to load each file separately to the USB and leave the USB in the unit while it reboots. This will cause the device to load only the selected file. Start with the bootloader (A6.UPB) and follow the prompts. If the device still reboots, then remove A6.UPB from the USB and only load the firmware (C15F), following the prompts once more.
If you are still running into issues, please reach out to tech support.
0 Comments