Skip to content
Start testing
Features

Product features for OCPP and OCPI operations

The signed-in workspace for chargers, virtual chargers, OCPP proxy, roaming, health checks, and the operator assistant. Protocol coverage is OCPP 1.6 / 2.0.1 / 2.1 and OCPI 2.1.1 / 2.2.1 / 2.3.0.
Start your testingBook technical demo
Product still: the OCPPLab workspace sidebar lists six areas, Charging, Virtual charger, OCPP proxy, Roaming, Observability and Operator assistant, with Virtual charger selected and its fleet of virtual charge points open beside it.

Charging

Operate charge points from the charger list, OCPP map, and station detail. Status comes from the live OCPP messages your chargers send.

Animated product preview: the charger list shows CP-1042, CP-1043 Available and CP-1044 Faulted. CP-1042 is selected; a StatusNotification arrives and its status changes from Available to Charging, and its station detail shows connector 1 with a RemoteStopTransaction action.

Virtual charger

Run hardware-free OCPP simulation from fleet, sites, logs, workflows, and playgrounds, including load-testing scenarios.

Animated product preview: a grid of identical virtual chargers, one in focus running OCPP 2.0.1. Its message log fills with StatusNotification Occupied, TransactionEvent Started and, last, TransactionEvent Updated.

OCPP proxy

Route charger traffic through backends, tokens, and routes. Inspect the message log when an integration fails.

Product still: the OCPP proxy message log with CALL BootNotification, CALLRESULT Accepted and CALL Heartbeat. The first row is expanded to its raw OCPP-J frame, [2,"19223201","BootNotification",{"chargePointVendor":…,"chargePointModel":…}].

Roaming

Work OCPI partners, catalog, sync, commands, and charging profiles in one place. Coverage is OCPI 2.1.1 / 2.2.1 / 2.3.0.

Product still: the OCPI roaming partner NL*OCP with the CPO and eMSP roles and its handshake steps versions, credentials and locations, each checked.

Observability

Watch protocol health across your paths. Metrics with no data show as unknown, never as zero.

Product still: a protocol health list where a path with no data reads Unknown, not zero.

Operator assistant

Ask the operator assistant on the home screen about your charging data once you sign in.

Product still: the operator assistant answers a question with a proposed RemoteStartTransaction for CP-1043 connector 1, waiting for the operator to approve or deny it.

Protocol coverage by version

What each version adds, checked against the specs. A dash is a real gap in that version, not a plan limit.

  • OCPP 1.6

    Transactions
    Supported
    Smart charging
    Supported
    Device model
    Not in this version
    Bidirectional (V2X)
    Not in this version
    Local tariffs
    Not in this version

  • OCPP 2.0.1

    Transactions
    Supported
    Smart charging
    Supported
    Device model
    Supported
    Bidirectional (V2X)
    Not in this version
    Local tariffs
    Not in this version

  • OCPP 2.1

    Transactions
    Supported
    Smart charging
    Supported
    Device model
    Supported
    Bidirectional (V2X)
    Supported
    Local tariffs
    Supported

  • OCPI 2.1.1

    Credentials
    Supported
    Tariffs
    Supported
    ChargingProfiles
    Not in this version
    HubClientInfo
    Not in this version
    Bookings
    Not in this version

  • OCPI 2.2.1

    Credentials
    Supported
    Tariffs
    Supported
    ChargingProfiles
    Supported
    HubClientInfo
    Supported
    Bookings
    Not in this version

  • OCPI 2.3.0

    Credentials
    Supported
    Tariffs
    Supported
    ChargingProfiles
    Supported
    HubClientInfo
    Supported
    Bookings
    OCPPLab extension, not an OCPI module
Vendor profilesABBEVBoxWallboxAlfen
Roaming hubGIREVE
Representative scenarios

Two evaluations buyers run before they sign

Each one ends on the run artifact and lists what to verify in the trial. They are example paths, not customer case studies.

CSMS release team

Mixed-fleet OCPP regression before production rollout

Your backend team needs proof that a CSMS release will not break charger onboarding, transactions, or smart charging on the legacy fleet or the new one.

  • Run OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 chargers side by side. ABB, EVBox, Wallbox, and Alfen-style profiles in the same workspace.
  • Replay BootNotification, Authorize, MeterValues, TransactionEvent, reconnect, and remote-command flows. Inspect raw protocol logs as they happen.
  • Send a SetChargingProfile with an invalid schedule from your CSMS and confirm the virtual charger answers Rejected.
Animated test-run result for OCPP 1.6, OCPP 2.0.1 and OCPP 2.1 chargers running the same checks. Checks resolve top to bottom: BootNotification Accepted, Authorize Accepted, then StartTransaction Accepted on OCPP 1.6 where the 2.x chargers send TransactionEvent and get Accepted, MeterValues answered with an empty CALLRESULT, and last the CSMS sends SetChargingProfile with an invalid schedule and each charger answers Rejected, as the check expects. Every check passes. Example run, not a captured result.
OCPP 1.6 testingOCPP 2.0.1 testingOCPP 2.1 testingCSMS testing workflow

Roaming interoperability team

OCPI partner onboarding before hub or bilateral go-live

Your roaming team validates credentials, tariffs, sessions, and CDR exchanges before a new OCPI connection touches a real partner or a certification path.

  • Exercise credentials, locations, tokens, sessions, CDRs, and tariff sync. OCPI 2.1.1 / 2.2.1 / 2.3.0 in one workspace.
  • Connect to OCPI hubs such as GIREVE as a CPO or eMSP party, or test bilaterally. ChargingProfiles and HubClientInfo included.
  • Push a CDR over OCPI 2.2.1 and confirm its total_cost carries both excl_vat and incl_vat.
Animated OCPI 2.2.1 onboarding timeline: GET /versions, GET /versions/2.2.1, POST /credentials, where token B is sent and token C returned, PUT /locations/{country_code}/{party_id}/{location_id}, GET /tokens and POST /cdrs, whose CDR total_cost carries excl_vat and incl_vat. Each step is checked in order. Example run, not a captured one.
OCPI 2.1.1 testingOCPI 2.2.1 testingOCPI 2.3.0 testingOCPI roaming workflow

Ready to open the app?

Open the operator workspace for chargers, virtual chargers, proxy, roaming, and health checks. Sign-in required.

Start your testingBook technical demo

Last updated: