# 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.
1.5.0 Update Note
In case firmware is updated from 1.5.0 directly to 1.9.0, produced H2 metric will be lost and FP_02 will be raised. It is recommended to follow the upgrade path: 1.5.0 -> 1.6.0 -> 1.7.X -> 1.8.X -> 1.9.X.
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
Preheatcommand for electrolyte preheating available in ModBus (#1014), EL 2.1 Web GUI and Enapter Cloud
- Elevation can be set over ModBus or WebGUI to compensate zero pressure of stack and outlet pressures
- Support for liquid cooled version 3 configuration of EL 2.1
- Electrolyser settings backup and restore feature available in the Enapter Cloud
- Dryer Firmware Update now available over Electrolyser Web GUI when IDCN is used. Dryer needs to be updated to version 3.5.0 over OTA.
- Improved PID regulation of electrolyte cooling fan to avoid overcooling and prevention to reach 55C
- A long press of the button in Stand-by enables system restart even outlet pressure is over the restart pressure setpoint
- FR_50 event renamed to CONFLICT BETWEEN WATER LEVEL SENSORS (LOW AND MEDIUM LEVEL)
- FR_51 event renamed to CONFLICT BETWEEN WATER LEVEL SENSORS (MEDIUM AND HIGH LEVEL)
- FR_52 event renamed to CONFLICT BETWEEN WATER LEVEL SENSORS (HIGH AND VERY HIGH LEVEL)
- FR_10 event renamed to ELECTROLYTE LEVEL IS TOO HIGH
- FR_20 event renamed to ELECTROLYTE LEVEL TOO MUCH LOW
- New warning event introduced - WL_10: Insufficient pressure drop
- New warning event introduced - WR_22: Refilling failure
- Improvements for the descriptions of Events in Web GUI, Mobile App, Cloud and Handbook
- Self Service Troubleshooting Flowcharts were added to Enapter Handbook
- Blowdown request now available in Web GUI
- The maintenance mode is activated automatically when there is no electrolyte in the tank
- Added new stack state -
# Bug Fixes
- Ethernet static discharge protection improved
- DCN/IDCN improvements
- Web GUI visual improvements
- Improved Stack Membrane check for 8 bar system
- Refilling routine improvements for better compatibility with external water systems
- Purge routine and V101 solenoid check improved
- Fixed Fatal Error FR_20 after updating from firmware 1.7.X
# Compatibility Matrix
Please carefully check the compatibility matrix for the 1.9.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)).
In case firmware is updated from 1.5.0 directly to 1.9.0 produced H2 will be lost and FP_02 will be raised.
# 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.
DCN may assign an IP address to devices (computers, mobiles) connected to Wi-Fi AP associated with DCN enabled Enapter devices.
- Delete the DCN from the Enapter Mobile App and create it one more time.
- If it is possible try to separate the DCN from your main network environment by connecting the DCN to another WiFi AP. There is no need to separate one DCN from another.