# Firmware Lifecycle
It is recommended to update the device in the IDLE mode without receiving and executing any commands from Modbus, Enapter Cloud, Enapter Mobile App, EL 2.1 Web GUI or others.
Make sure you have physical access to the device before starting the update process.
Do not power off the device during the firmware update.
Remove Dryer Control Network before updating the firmware.
If Site has Enapter Gateway it needs to be updated to version 1.8.9 or higher.
# Change Log
# New Features
UCM firmware version 1.7.0 release.
UCM and Mainboard Firmware Update over Web GUI.
The age of the electrolyte is displayed in the Web GUI.
Keep cooling loop valve open in maintenance mode for Liquid Cooled versions of Electrolyser.
New fatal state FX_11 introduced in case control board MCU reach temperature 75C.
# Compatibility Matrix
Please carefully check the compatibility matrix for the 1.7.0 firmware version with the previous version.
- C - fully compatible;
- NC - not compatible;
- PC - party compatible, check additional notes.
|Modbus Communication Backward Compatibility||C|
# Functional Depreciation Statements
- Warning WS_20 is deprecated. Instead of using it for checking that Electrolyser reached Max Pressure it is recommended to use input register #1200 (4 = Stand-By (Max Pressure)).
# Modbus Compatibility
Holding register #6018 is used for Start and Stop the Dryer starting from firmware 1.6.0.
Input registers #14 (Cabinet (Chassis) Serial Number) and #1000 (Stack Serial Number) are deprecated. Instead use holding registers #4026 (Enapter Chassis Serial Number) and #4376 (Enapter Stack Serial Number).
# Known Bugs List
The list below contains the most important problems in the firmware and their solutions.
There is an issue (opens new window) using WiFi and Windows to access the
Solution: Use a local ethernet connection to the electrolyser or IP address as a hostname.
If the WiFi router power cut happens for a very short period it is possible that one of the devices connected to the Dryer Control Network won't be able to connect to the cloud and will have the offline status.
Solution: To resolve the issue you will need to manually reboot the device. This issue will be fixed in future FW releases.