Alfen OCPP testing validates how your CSMS handles Alfen chargers across BootNotification, Authorize, StartTransaction, MeterValues, StatusNotification, and remote commands. Alfen units such as the Eve Single Pro-line and Eve Double Pro-line commonly speak OCPP 1.6J and rely on Active Load Balancing and smart-charging configuration that your backend must read and set correctly. Teams use this testing to catch compatibility gaps before a backend release or a fleet rollout reaches production.
Last reviewed
A practical Alfen 1.6J regression test covers BootNotification with the Alfen vendor identity, authorization, an active session with meter values, a smart-charging limit, and a remote stop before the session ends.
Charge point -> CSMS: BootNotification(chargePointVendor "Alfen BV", chargePointModel "Eve Single Pro-line")
CSMS -> Charge point: Accepted
Charge point -> CSMS: Authorize(idTag)
CSMS -> Charge point: Accepted
Charge point -> CSMS: StartTransaction
CSMS -> Charge point: Accepted
Charge point -> CSMS: MeterValues (Energy.Active.Import.Register)
CSMS -> Charge point: Accepted
CSMS -> Charge point: SetChargingProfile (Active Load Balancing limit)
Charge point -> CSMS: Accepted
CSMS -> Charge point: RemoteStopTransaction
Charge point -> CSMS: StopTransactionAlfen testing reduces regression risk across the charger lifecycle, from BootNotification identity through smart-charging limits, before a backend release or a site rollout.
Registration and identity
Session execution
Smart charging and commands
| Area | Coverage | Typical validation |
|---|---|---|
| Registration and identity | BootNotification and early-session setup | Confirm your CSMS accepts the Alfen BV vendor identity and applies the right configuration keys to Eve Pro-line and NG9xx units. |
| Session execution | Authorize, MeterValues, and StopTransaction | Validate the Authorize, MeterValues, and StopTransaction path that drives billing and support cases. |
| Smart charging and commands | SetChargingProfile, Reset, and reconnect handling | Exercise SetChargingProfile limits, Reset, and reconnects where Alfen Active Load Balancing assumptions often break. |
Check Alfen charger behavior before shipping backend changes to sessions, statuses, or smart-charging limits across your Eve Pro-line fleet.
Run Alfen 1.6J flows next to other vendors so your CSMS handles Active Load Balancing and configuration differences cleanly.
Replay reported Alfen session or load-balancing issues in a controlled setup instead of waiting on hardware-lab access.
Run repeatable virtual tests for Eve Pro-line and NG9xx onboarding, sessions, smart-charging limits, and reconnect behavior before they reach production.