OCPP and OCPI protocol testing
OCPP 1.6 Testing
Validate charger onboarding, authorization, transactions, status notifications, meter values, and remote commands for widely deployed OCPP 1.6 fleets.
- Legacy AC charger compatibility
- CSMS transaction handling
- BootNotification and heartbeat validation
Explore OCPP 1.6 testing →
OCPP 2.0.1 Testing
Test modern OCPP 2.0.1 workflows including smart charging, device management, security profiles, ISO 15118-adjacent flows, and TransactionEvent handling.
- Smart charging and charging profiles
- Security profile validation
- Device model and TransactionEvent workflows
Explore OCPP 2.0.1 testing →
OCPP 2.1 Testing
Cover OCPP 2.1 in the workspace: V2G/V2X setpoints, DER control, local tariffs, BatterySwap, and AFRR message sequences.
- Bidirectional power and V2G workflows
- Local tariffs with SetDefaultTariff and ChangeTransactionTariff
- DER integration and battery swapping
Explore OCPP 2.1 testing →
OCPI 2.1.1 Testing
Cover core roaming interoperability for credentials, locations, sessions, CDRs, tariffs, tokens, and commands between CPOs and eMSPs.
- Core roaming interoperability
- CPO and eMSP endpoint simulation
- Credentials, sessions, and CDR validation
Explore OCPI 2.1.1 testing →
OCPI 2.2.1 Testing
Validate newer roaming and hub workflows including ChargingProfiles, HubClientInfo, richer tariff structures, and broader hub interoperability requirements.
- Hub-oriented roaming workflows
- ChargingProfiles and HubClientInfo coverage
- Advanced tariffs and smart charging flows
Explore OCPI 2.2.1 testing →
OCPI 2.3.0 Testing
Cover OCPI 2.3.0 in the workspace: hub_party_id credentials, the PTP role, HubClientInfo routing, and the OCPPLab Bookings extension.
- Bookings extension and EVSE reservation flows
- Hub party ID and credential handshakes
- Advanced tariff structures and HubClientInfo
Explore OCPI 2.3.0 testing →
Protocols & standards
The core EV charging and energy protocols OCPPLab speaks, from charger-to-backend communication through roaming between networks.
OCPP
The Open Charge Point Protocol is an application protocol for communication between electric vehicle charging stations and a central management system.
OCPI
The Open Charge Point Interface is a protocol that connects charge point operators and e-mobility service providers, enabling EV roaming, location and tariff data, and the exchange of charging sessions and billing records between networks.
Adjacent standards (not supported)
EEBUS and Modbus often sit next to chargers in energy and site setups. OCPPLab does not implement them.
EEBUS
EEBUS is a protocol suite for the Internet of Things that aims to standardize the interface between electrical consumers, producers, storages and (logical) managing entities.
Modbus
Modbus is a data communications protocol. It is a de facto standard communication protocol and widely used to connect industrial electronic devices.
Comparison guides
Use these guides when you need to choose between versions or evaluate emulator options before committing to an implementation path.
Need coverage across multiple protocol versions?
OCPPLab lets you test mixed fleets and roaming stacks from one cloud platform.