OCPP 1.6 client for microcontrollers. Portable C/C++. Compatible with Espressif, Arduino, NXP, STM, Linux and more.
Formerly ArduinoOcpp (migration guide): the initial version of this library used the Arduino API but this dependency was dropped some time ago and the old name has become outdated. Despite the new name, nothing changes for existing users and the Arduino integration will continue to be fully functional.
✔️ Eligible for public chargers (Eichrecht-compliant)
✔️ Supports all OCPP 1.6 feature profiles
Tester / Demo App
Main repository: MicroOcppSimulator
(Beta) The Simulator is a demo & development tool for MicroOcpp which allows to quickly assess the compatibility with different OCPP backends. It simulates a full charging station, adds a GUI and a mocked hardware binding to MicroOcpp and runs in the browser (using WebAssembly): Try it
OCPP server setup: Navigate to "Control Center". In the WebSocket options, add the OCPP backend URL, charge box ID and authorization key if existent. Press "Update WebSocket" to save. The Simulator should connect to the OCPP server. To check the connection status, it could be helpful to open the developer tools of the browser.
If you don't have an OCPP server at hand, leave the charge box ID blank and enter the following backend address:
wss://echo.websocket.events/ (this server is sponsored by Lob.com)
RFID authentication: Go to "Control Center" > "Connectors" > "Transaction" and update the idTag with the desired value.
Full report: MicroOcpp benchmark (esp-idf)
The following measurements were taken on the ESP32 @ 160MHz and represent the optimistic best case scenario for a charger with two physical connectors (i.e. compiled with
-Os, disabled debug output and logs).
|Flash size (minimal)||121,170 B|
|Heap occupation (idle)||12,308 B|
|Heap occupation (peak)||21,916 B|
|Large message sent||5 ms|
In practical setups, the execution time is largely determined by IO delays and the heap occupation is significantly influenced by the configuration with reservation, local authorization and charging profile lists.
PlatformIO package: MicroOcpp
MicroOcpp is an implementation of the OCPP communication behavior. It automatically initiates the corresponding OCPP operations once the hardware status changes or the RFID input is updated with a new value. Conversely it processes new data from the server, stores it locally and updates the hardware controls when applicable.
examples/ESP/main.cpp as the starting point for the first project. It is a minimal example which shows how to establish an OCPP connection and how to start and stop charging sessions. The API documentation can be found in
MicroOcpp.h. Also check out the Docs.
If compiled with the Arduino integration:
- Links2004/arduinoWebSockets (version
In case you use PlatformIO, you can copy all dependencies from
platformio.ini into your own configuration file. Alternatively, you can install the full library with dependencies by adding
matth-x/MicroOcpp@1.0.0 in the PIO library manager.
OCPP 2.0.1 and ISO 15118
The call for funding for the OCPP 2.0.1 upgrade is open. The version 1.6 support has successfully been funded by private companies who share an interest in using this technology. OCPP is most often seen as a non-differentiating feature of chargers and is therefore perfectly suited for Open Source collaboration. If your company needs OCPP 2.0.1, please use the contact details at the end of this page to receive the more details about the funding plan and why it is beneficial to engage in the upgrade (for hardware manufacturers and CPOs).
MicroOcpp is a good foundation for starting the OCPP 2.0.1 development:
🎉 Tested by hundreds, including backend operators. The Simulator encourages quick compatibility tests
🔨 Comes with development tools and a CI/CD specialized for OCPP
👨🏫 Academic background: roots in a research project
🔐 Unit tests with valgrind, AddressSanitizer and UndefinedBehaviorSanitizer
❤️ Contributions are highly welcome. Open to building a team
A note on ISO 15118: this library facilitates the integration of ISO 15118 by handling its OCPP-side communication. A public demonstration will follow with the first collaboration on an open OCPP 2.0.1 + ISO 15118 integration.
I hope the given documentation and guidance can help you to successfully integrate an OCPP controller into your EVSE. I will be happy if you reach out!
✉️ : matthias [A⊤] arduino-ocpp [DО⊤] com