Wallbox OCPP Testing
What is Wallbox OCPP testing?
Wallbox OCPP testing checks how your CSMS handles Wallbox chargers across the OCPP 1.6J lifecycle. AC units like the Pulsar Plus, Commander 2, and Copper SB, plus the Supernova DC fast charger, send BootNotification, Authorize, StartTransaction, MeterValues, and StatusNotification. Teams verify these flows before backend changes reach production. Many Wallbox sites add the Power Boost or Power Sharing accessory for load management, so confirm your backend reads the meter values those setups report.
Last reviewed
Why this matters
- Wallbox regressions show up in session timing and RemoteStopTransaction handling, not in simple schema checks.
- You can test a Pulsar Plus or Supernova session without booking a physical charger or a field site.
- Power Boost and Power Sharing change the MeterValues your CSMS receives, so repeatable tests catch billing and load-management bugs early.
What to validate
- BootNotification, Heartbeat, StatusNotification, Authorize, MeterValues, and transaction handling.
- Remote commands such as remote start, stop, reset, and operational control flows.
- State transitions across available, preparing, charging, suspended, finishing, and faulted conditions.
- Regression testing across reconnects, timeouts, and backend release changes.
Example Wallbox OCPP validation flow
A practical Wallbox test follows a Pulsar Plus from BootNotification through Preparing, an Authorize check, an active StartTransaction session with MeterValues, and a backend-sent RemoteStopTransaction. These are OCPP 1.6J messages, the version Wallbox chargers commonly use.
Pulsar Plus -> CSMS: BootNotification {chargePointVendor: "Wallbox", chargePointModel: "Pulsar Plus"}
CSMS -> Pulsar Plus: Accepted, heartbeatInterval 300
Pulsar Plus -> CSMS: StatusNotification {connectorId: 1, status: "Preparing"}
CSMS -> Pulsar Plus: (ack)
Pulsar Plus -> CSMS: Authorize {idTag}
CSMS -> Pulsar Plus: idTagInfo {status: "Accepted"}
Pulsar Plus -> CSMS: StartTransaction {connectorId: 1, idTag, meterStart}
CSMS -> Pulsar Plus: transactionId, idTagInfo {status: "Accepted"}
Pulsar Plus -> CSMS: MeterValues {transactionId, Energy.Active.Import.Register}
CSMS -> Pulsar Plus: RemoteStopTransaction {transactionId}
Pulsar Plus -> CSMS: StopTransaction {transactionId, meterStop, reason: "Remote"}Wallbox compatibility proof points
Wallbox QA needs confidence across the full charger lifecycle, not just one happy-path session. AC units like the Pulsar Plus and the Supernova DC fast charger both matter.
Onboarding and status
- BootNotification (chargePointVendor Wallbox), then Available and Preparing StatusNotification
- Check the first messages a Pulsar Plus or Commander 2 sends after power-up or reconnect.
Authorization and charging
- Authorize, StartTransaction, MeterValues, and StopTransaction
- Confirm the billing path, including the meter readings a Power Boost or Power Sharing setup reports.
Operational commands
- RemoteStopTransaction, Reset, and ChangeAvailability
- Make sure backend commands reach the charger reliably during a live session.
| Area | Coverage | Typical validation |
|---|---|---|
| Onboarding and status | BootNotification (chargePointVendor Wallbox), then Available and Preparing StatusNotification | Check the first messages a Pulsar Plus or Commander 2 sends after power-up or reconnect. |
| Authorization and charging | Authorize, StartTransaction, MeterValues, and StopTransaction | Confirm the billing path, including the meter readings a Power Boost or Power Sharing setup reports. |
| Operational commands | RemoteStopTransaction, Reset, and ChangeAvailability | Make sure backend commands reach the charger reliably during a live session. |
Common scenarios
Release regression testing
Replay Pulsar Plus and Supernova sessions before shipping CSMS updates that touch StartTransaction, StatusNotification, or RemoteStopTransaction handling.
Support issue reproduction
Recreate a reported Commander 2 or Copper SB fault in a controlled test instead of waiting on field access and partial logs.
Vendor-compatibility QA
Run Wallbox sessions next to other vendor profiles so mixed-fleet backend behavior stays stable, including sites that use Power Sharing.
Frequently asked questions
- Which Wallbox chargers are supported for OCPP CSMS testing?
- OCPPLab models Wallbox Pulsar Plus, Pulsar Max, Commander 2, Copper SB, and Supernova DC fast chargers over OCPP 1.6J WebSockets.
- Can I test Wallbox Power Sharing profiles and remote lock/unlock?
- Yes. You can simulate dynamic charging profiles, ChangeConfiguration parameters, and remote commands to ensure your CSMS correctly controls Wallbox units.
Validate Wallbox OCPP 1.6J behavior before rollout
Test Pulsar Plus, Commander 2, and Supernova sessions, status transitions, and RemoteStopTransaction in a repeatable virtual environment instead of waiting on a hardware lab.