Firmware updates
Functionality support and firmware roadmap for Plus products
The Eve Single Plus, Eve Double Plus, Twin 5 Plus and Twin 4XL V2G are built on the Alfen Hardware Platform (AHP), a new hardware and firmware architecture designed to support the next generation of EV charging functionality.
AHP has been developed to provide a reliable, flexible, and future-ready foundation that enables continuous improvement through firmware updates. This allows new features, integrations and performance enhancements to be introduced over time, ensuring chargers remain compatible with evolving technologies, energy systems and industry standards throughout their operational lifetime.
Platform transition and functionality availability
The introduction of AHP represents a transition from the previous NG9 platform, which is used on the Eve Single S-line, Eve Single Pro-line, Eve Double Pro-line and Twin 4XL.
Because AHP uses a completely redesigned architecture, certain functionalities available on NG9 require redevelopment and validation before becoming available on the new platform. These functionalities are introduced gradually through firmware releases, following extensive testing and validation.
This structured approach ensures that each new feature meets Alfen’s standards for reliability, stability and safe operation.
Why AHP firmware is larger than NG9
Compared to the NG9 platform, the AHP firmware image is larger by design. This reflects the broader functional scope, more advanced architecture and multi-generation design of the platform.
Key contributors include ISO 15118 preparation—even when Plug & Charge is not yet fully active—and enhanced security mechanisms required for evolving cybersecurity, grid and automotive standards.
While firmware size may vary slightly with future updates, the update process remains efficient and reliable. For more detail, refer to the Alfen Knowledge Base.
Firmware releases and functionality introduction
Functionality on AHP is delivered through firmware releases. Firmware version 2.5, scheduled for release in May, introduces a new set of capabilities focused on security, network control and energy management.
This release includes:
- EU RED Cyber Security compliance
- Tamper Detection (Strict Mode)
- Fixed IP support
- Advanced Active Load Balancing
Subsequent firmware releases will continue to expand platform capabilities further, including integration with Energy Management Systems, advanced energy features such as Solar Charging, Eve Connect, Vehicle-to-Everything (V2X) and Plug & Charge.
Continuous improvement through firmware updates
Firmware updates are a core component of the Alfen Hardware Platform lifecycle. They enable chargers to gain new functionality, improve performance and maintain compatibility with evolving energy and charging ecosystems.
Chargers are delivered with the latest available firmware version at the time of production. Additional features and improvements become available through subsequent firmware updates.
We recommend regularly checking the firmware version installed on your charger and reviewing the latest available updates. For detailed release notes and specifications per firmware version, please refer to the Alfen Knowledge Base.
Compatibility in mixed SCN environments
In installations where NG9-based chargers and AHP-based chargers are combined in a mixed Smart Charging Network (SCN), not all firmware versions are fully compatible. As a result, certain functionalities may be limited or unavailable depending on the firmware combination used.
For a complete and up-to-date overview of compatible NG9 and AHP firmware versions in mixed SCN environments, please refer to the Alfen Knowledge Base.
Release process and disclaimer
Firmware releases follow a structured validation process, including internal testing and customer validation cycles. Each release candidate cycle requires a minimum of three weeks of validation before production release.
All mentioned timelines and functionalities are indicative and subject to change without notice. No rights or commitments can be derived from published information.