Firmware Lifecycle

• Requirements
• Change Log
• Compatibility Matrix
• Functional Depreciation Statements
• Known Bugs List

Requirements

Note

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

• Link to the Terms of Use were added to Web GUI log in form.
• Added Cloud over Ethernet in Web GUI.
• Added Modbus TCP configuration in Web GUI.
• New event Warning WY_50: SIF-test has been started was introduced.

Bud Fixes

• Fixed Warning WU_11: Electrolyte Level Insufficient for Start-up.
• Fixed Build_id field skipped in released firmware.

Compatibility Matrix

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

Legend:

• C - fully compatible;
• NC - not compatible;
• PC - party compatible, check additional notes.

	3.5.0
OTA Upgradable	C
Modbus Communication Backward Compatibility	C
Configuration	C
Rollback	C

Functional Depreciation Statements

None

Known Bugs List

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

• This version of firmware can cause false positive triggering of FS_12 (Insufficient stack current) event when production rate set to 60%.

  Solution: Use 65% production rate as a minimum production rate until the patch version of firmware will be released.

• 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.

  Solution:

  • 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.