Not just a “performance EPROM”.
In a Fenix 1B ECU, the EPROM contains both the code executed by the ECU and its engine calibrations. Fenix 1B EvoPROM works on both. The Renault ECU remains physically original; its software architecture evolves.
From the original 13×9 format up to 30×21
Original Fenix 1B programs use 13×9 maps for ignition advance and base injection-time tables, giving 117 cells per table.
EvoPROM expands this architecture up to 30×21, or 630 cells per table. Engine-speed and pressure axes remain fully configurable.
Prepared from your configuration
By default, EvoPROM is built from the contents of the EPROM currently installed in the customer’s ECU. The original tables are linearly interpolated into the new resolution.
Axis steps are defined with the customer according to the engine configuration and intended use, and remain fully configurable afterwards.
Added functions inside the Fenix
An EvoPROM paired to your ECU
For copy-protection reasons, each EvoPROM is physically paired to one specific Fenix 1B ECU. The ECU must be sent to FENIX LAB for pairing. This cannot be performed remotely.
Pairing is invisible to other EPROMs, so returning to an original or previous EPROM remains possible.
BIN and XDF supplied
EvoPROM is supplied with its corresponding .bin file and an .xdf file for access to the exposed parameters in TunerPro.
Fenix 1B only
Fenix 1B EvoPROM is exclusively intended for compatible Fenix 1B ECUs.
A Fenix 3 version is under study. Interested owners are invited to contact FENIX LAB by email with their vehicle and ECU reference; demand will help prioritize development.
Public-road use and compliance
Fenix 1B EvoPROM can alter engine parameters and strategies compared with the vehicle’s original approved configuration. Depending on the changes used, this may affect compliance for public-road use. The owner remains responsible for compliance with applicable regulations.
