OCPP: Zephyr RTOS as Electric Vehicle Supply Equipment(EVSE)
summary
Zephyr runs a native OCPP stack that uses websockets and JSON to act as EVSE, exposing consumer APIs for authorize, start/stop transaction and a session per connector. Implementation covers the v1.6 core profile (about 29 messages in v1.6) with built‑in socket reconnect, key‑value configuration for heartbeat/meter cadence, Modbus meter support, and modem/Wi‑Fi/ethernet interfaces; proof‑of‑concept works on existing MCU boards and one customer integration includes ISO 15118 work. Future items: TLS and optional/2.0.1 profile support.
AI-written summary · about
chapters (8)
- 0:00EVSE and OCPP intro
- 7:51Charging infrastructure limits
- 11:21Open Charge Point Protocol
- 23:32OCPP message formats
- 28:51OCPP in Zephyr RTOS
- 35:14EVSE standards handshaking
- 37:46OCPP in Zephyr future
- 38:27Q&A
related talks
05mZephyr
35mEnd-to-end IoT Development with Zephyr
16mDesigning Secure Systems for CRA Compliance leveraging Zephyr
40mZephyr Project Security Status
23mKeynote: Zephyr & IoT Security
41mTurning the Ignition on Safety: Zephyr RTOS in Automotive Compliance
31mUsing Zephyr for Embedded Controllers
39mZephyr Extensions: How to Dynamically Load an Application