Enapter Handbook

# Firmware Lifecycle

# Requirements

Note

Before OTA make sure to go through the list below.

  • Make sure you have physical access to the device before starting the update process.
  • Do not power off the device during the firmware update.
  • If Site has Enapter Gateway it needs to be updated to version 1.8.9 or higher.
  • Remove the Dryer Control Network (DCN) before updating the firmware (no need since 3.3.0).
  • Electrolysers connected to DCN/IDCN should be version 1.10.0 or higher, otherwise monitoring and control from Electrolyser Web GUI or Modbus TCP interface won't work.

# Change Log

# New Features

  • Added new event Warning WP_05: Drying interrupted during operation.
  • Added possibility of adjusting automatic start/stop pressure variables using Enapter Cloud.
  • Added possibility to save Average Operational Period using Enapter Cloud.

# Compatibility Matrix

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

Legend:

  • C - fully compatible;
  • NC - not compatible;
  • PC - party compatible, check additional notes.
3.9.1
OTA Upgradable C
Rollback C

# Functional Depreciation Statements

# Modbus Compatibility

  • Begin with firmware version 3.6.0 Dryer input registers are deprecated, holding registers should be used instead.

# Known Bugs List

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

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

  • False EPS00 and EPS01 errors may occur during frequent transitions of input pressure through In_pressure_threshold_drying (short Drying periods and longer Waiting for Pressure periods alternating).

    Solution: Update the firmware to version 3.10.1 or above.

Was this page useful?