ABB OCPP Testing
Validate how your CPMS handles ABB chargers, from the Terra AC wallbox to Terra DC and Terra 360 fast chargers, with repeatable virtual OCPP testing before rollout, fleet migration, or backend changes.
What is ABB OCPP testing?
ABB OCPP testing checks how your CPMS behaves when it talks to ABB chargers such as the Terra AC wallbox, Terra DC, Terra 360, and the older Terra 54. These run OCPP 1.6J, and some DC models add OCPP 2.0.1 on newer firmware. You can test onboarding, authorization, transactions, remote commands, and reconnect behavior across a mixed 1.6 and 2.0.1 fleet without booking a hardware lab.
Why this matters
- ABB's lineup spans low-power AC wallboxes and high-power DC chargers, so one CPMS change can pass on a Terra AC and still break a Terra 360.
- Most ABB chargers speak OCPP 1.6J today while newer DC firmware adds OCPP 2.0.1, so your backend must handle both versions side by side.
- Virtual Terra chargers reproduce onboarding and session flows on demand, so you regression-test every backend or firmware change without waiting on lab hardware.
What to validate
- BootNotification, heartbeat, authorization, transaction, and status lifecycle coverage.
- Remote commands such as remote start, stop, reset, and configuration-related behaviors.
- MeterValues cadence, session closure, and reconnect scenarios under realistic CPMS conditions.
- Side-by-side OCPP 1.6 and OCPP 2.0.1 validation where mixed-fleet support matters.
Example ABB OCPP validation flow
A practical ABB regression test starts when a Terra charger sends BootNotification, then runs through authorization, an active transaction, MeterValues, and a backend stop command before the session ends.
Charge point -> CPMS: BootNotification(chargePointVendor "ABB", chargePointModel "Terra AC")
CPMS -> Charge point: Accepted + heartbeat interval
Charge point -> CPMS: StatusNotification(Available -> Preparing)
Charge point -> CPMS: Authorize(idTag)
CPMS -> Charge point: Accepted
Charge point -> CPMS: StartTransaction or TransactionEvent(Started)
CPMS -> Charge point: Accepted
Charge point -> CPMS: MeterValues or TransactionEvent(Updated)
CPMS -> Charge point: Accepted
CPMS -> Charge point: RemoteStopTransaction or RequestStopTransaction
Charge point -> CPMS: StopTransaction or TransactionEvent(Ended)ABB compatibility proof points
Validate these areas against ABB chargers, from AC wallboxes to high-power DC, before you trust the fleet in production.
| Area | Coverage | Typical validation |
|---|---|---|
| AC and DC onboarding | BootNotification with chargePointVendor ABB, heartbeat, and StatusNotification | Confirm your CPMS registers Terra AC, Terra DC, and Terra 360 chargers cleanly. |
| Session lifecycle | Authorize, StartTransaction or TransactionEvent, MeterValues, and stop | Check that billing and meter data stay consistent across AC and high-power DC sessions. |
| Backend control paths | RemoteStopTransaction, Reset, and ChangeConfiguration | Verify remote commands land reliably during fast-charging sessions. |
Common scenarios
Pre-release CPMS regression
Replay ABB Terra flows before deploying backend changes that touch registration, transactions, or remote commands.
Mixed 1.6 and 2.0.1 fleet
Test OCPP 1.6J Terra AC chargers next to OCPP 2.0.1 DC models so your CPMS handles both protocol versions in one fleet.
High-power DC under load
Run many concurrent Terra DC and Terra 360 sessions to check meter cadence, timing, and command reliability under real traffic.
Related resources
Test ABB Terra chargers against your CPMS
Validate onboarding, transactions, and remote commands for ABB AC and DC chargers in a controlled environment instead of debugging against scarce hardware.