Technical articles
Deep dives on OCPP 2.0.1 (messages, transport and the bench).
Why testing a charge point needs a different CSMS than operating one
A CPO can prepare for the charge points it integrates. A manufacturer cannot prepare for the CSMS it will be connected to. This asymmetry decides what a test CSMS needs to support.
- ocpp
- testing
- csms
Your wallbox, your backend? Why migrating a charge point to a new CSMS fails at the security profile
The EU Data Act gives owners the right to send their charging data to a service of their choice. OCPP security profiles 1, 2 and 3 decide whether that is a five minute job or technically impossible without help from the new operator.
- ocpp
- security
- certificates
- data-act
The certificate dilemma: how we (have to) backport ISO 15118-20 support to OCPP 1.6 and 2.0.1
AFIR mandates ISO 15118-20 from 2027, but OCPP 1.6 and 2.0.1 have no standard way to manage its separate certificate chains. Three ways to backport it, and why the OCA needs to act.
- afir
- ocpp
- iso-15118
- certificates
The OCPP 2.0.1 BootNotification
The very first message a charging station sends after it connects: the boot reason, the hardware it reveals, and the clock sync hiding in the response.
- ocpp
- boot
- websocket
How a charging station opens its OCPP-J WebSocket connection
The connection URL, the HTTP upgrade and subprotocol negotiation, HTTP Basic Auth and TLS across the three security profiles, and how the connection is kept alive and re-established.
- ocpp
- websocket
- transport
The stack under OCPP: TCP, TLS, WebSocket and OCPP-J
OCPP messages do not travel over the wire by themselves. They ride a stack of well-known layers. A walk from TCP up to the application layer, and where the security profiles and TLS fit in.
- ocpp
- transport
- security
What is OCPP, and where do you get it?
A short introduction to the Open Charge Point Protocol: what it does, who maintains it, how to obtain the open specification, and what each of its seven parts contains.
- ocpp
- introduction