Protocols
OCPP and OCPI protocol testing
OCPP is the protocol between a charger and its CPMS. OCPI is the roaming API between CPOs and eMSPs. Dedicated pages for protocol versions EV charging teams test: OCPP 1.6, 2.0.1, 2.1, and OCPI 2.1.1, 2.2.1, 2.3.0. Each covers version-specific workflows and testing scope.
Interactive Protocol Frame Inspector
Inspect live schemas, JSON-RPC envelopes, and REST payloads across all six supported protocols.
Protocol Version1.6-J
Action / MethodBootNotification
Flow DirectionCharger → CSMS
Spec CapabilityActive Fleet Standard
[
2,
"msg-16-boot-8841",
"BootNotification",
{
"chargePointVendor": "OCPPLab Virtual",
"chargePointModel": "HyperCharge-Pro",
"chargePointSerialNumber": "OCPP-SIM-9021",
"chargeBoxSerialNumber": "BOX-77319",
"firmwareVersion": "2.4.12-rel",
"meterType": "Integrated 3-Phase kWh"
}
]Standard charger power-on handshake with firmware, vendor model, and charge point serial.WebSocket JSON-RPC 2.0
OCPP 1.6
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
- CPMS transaction handling
- BootNotification and heartbeat validation
Explore OCPP 1.6 testing →
OCPP 2.0.1
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
OCPP 2.1 Testing
Explore OCPP 2.1 enhancements including bidirectional charging (V2G/V2X), DER control, dynamic tariffs, BatterySwap, and AFRR signal integration.
- Bidirectional power and V2G workflows
- Dynamic tariffs and cost calculation
- DER integration and battery swapping
Explore OCPP 2.1 testing →
OCPI 2.1.1
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
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
OCPI 2.3.0 Testing
Validate modern OCPI 2.3.0 roaming workflows featuring the Bookings module for EVSE reservations, hub party ID credentials, and HubClientInfo.
- Bookings module 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, smart energy, and industrial device control.
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.
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.