# Firmware Lifecycle

# Requirements


Before OTA make sure to go through the list below:

  • It is recommended to update the device in the IDLE mode without receiving and executing any commands from Modbus, Enapter Cloud, Enapter Mobile App, 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.
  • Dryer connected to DCN/IDCN should be version 3.6.0 or higher, otherwise it won't be possible to connect Electrolysers to IDCN, monitor and control Dryer from Electrolyser Web GUI or Modbus TCP interface.

# Change Log

# New Features

  • Added support for new hardware product codes ELE400535A2ASV04, ELE400508A2ASV04, ELE400535A2LSV04, ELE400508A2LSV04, ELE400535A2ASV05, ELE400508A2ASV05, ELE400535A2LSV05, ELE400508A2LSV05.
  • Pre-heating of electrolyte can be canceled by command.
  • Warning WS_22 was renamed to Refilling not happening.
  • Added Warning WU_11: Electrolyte level insufficient for start-up.
  • Safety Proof-Tests can be run in Maintenance mode.
  • Handbook documentation was updated with minor bug fixes.
  • Safety errors descriptions improvement (FY_51, FY_52, FY_53, FY_54, FY_55, FY_56 and FY_25).
  • First refilling by customer skips flushing.
  • Added Warning WR_23: Draining timeout when draining is slow.
  • Ramp-Up Routine extended with advanced Stack diagnostics.
  • Added Warning WU_20: Ramp-Up leak check failed.
  • De-pressurisation slope stored in Enapter Cloud (stack aging analysis).
  • Refilling Routine was improved for better operation with EL 4.0 process water tank.
  • De-pressurisation Routine improved for increased safety.
  • Antifrost Routine activated on low water level instead of medium.
  • Added Recombiner Antifreeze Routine. Added Fatal Error FB_30: Recombiner frozen. Added Fatal Error FB_31: Recombiner heater malfunction.
  • Added new Recombiner states.
  • Recombiner Fatal Error FB_11: Over temperature can happen in Idle state.
  • Minor fixes and improvements for UCM.
  • Added support for Dryer Control Network API version 2.0.
  • Improvements for Dryer Control Network communication.
  • Added Stack new states.
  • Refilling happens to medium level.
  • Minor improvements in configuration.
  • FAT can disable first flushing for user's maintenance.
  • H2 sensor logic improved to reduce false positives.
  • After periodic purge Stack self-diagnostics check introduced for 35 bar systems.
  • Added Fatal Error FS_11: Stack internal leakage.
  • Error EU_10: Not enough warmup water was changed to Warning WU_11: Electrolyte level insufficient for start-up.
  • Syslog compatibility is improved.
  • Added Warning WT_21: Slow electrolyte heating in case when electrolyte temperature is not growing fast enough.

# Bug Fixes

  • Avoid system reboot in case of big number of commands from Enapter Cloud / App or Gateway.
  • Fixed pump speed after running pre-heat command.
  • Fixed Web GUI freeze if Syslog Severity Level is out of range.
  • Fixed WX_50 triggering in Service mode.

# Compatibility Matrix

Please carefully check the compatibility matrix for the 3.3.0 firmware version with the previous version.


  • C - fully compatible;
  • NC - not compatible;
  • PC - party compatible, check additional notes.
OTA Upgradable C
Modbus Communication Backward Compatibility C
Configuration C
Rollback C

# Functional Depreciation Statements


# Known Bugs List

The list below contains the most important problems in the firmware and their solutions.

  • It is an issue (opens new window) using WiFi and Windows to access the .local hostname.

    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. It is no need to separate one DCN from another.