OCPP: Zephyr RTOS as Electric Vehicle Supply Equipment(EVSE)
summary
Zephyr ships a native OCPP stack that implements OCPP 1.6 core (about 29 messages) as a consumer API on top of Zephyr’s WebSocket JSON transport, with session open/close, reconnection logic, and key/value configuration for heartbeat and meter intervals. The build integrates Modbus energy meter integration and RFID/NFC hooks, exposes authorize/start/stop transaction calls and meter callbacks, and is under review for merge so it exists as working code pending upstream inclusion.
AI-written summary · about
chapters (13)
- 0:00OCPP and EVSE with Zephyr
- 1:23EV charging challenges
- 3:32Zephyr RTOS for EVSE
- 8:13Open Charge Point Protocol
- 12:23OCPP 1.6 core messages
- 20:24OCPP message format
- 23:31Charging session workflow
- 28:46OCPP in Zephyr RTOS
- 35:30EVSE handshaking standards
- 37:57Zephyr OCPP support
- 38:20Q&A on OCPP transactions
- 40:04Q&A on ISO 15118
- 41:53Q&A on meter values
related talks
37mZephyr: A Game Changer for the Automotive Industry
49mThe Zephyr™ Project – An Updated Overview
45mLeveraging Zephyr RTOS for modern embedded systems: a perspective from education and research
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
20mZephyr Network Subsystem Status and Overview
05mZephyr
44mThe Meetup of Zephyr and OpenEuler