The OCPP Add-On for Chargers. Lean integration. Open Source.

MicroOcpp is an OCPP client for Charge Points. Customizable software architecture. Continuously tested with the market-leading OCPP backends.

Optimized for microcontrollers

Embedded C/C++ · Low memory footprint · Suitable for RTOSes

MIT license

Cost-efficient OCPP compatibility · No licensing fees

Private & public charging

Same API for private & public charging · Eichrecht-compliant

Compatible technologies: NXP ·  Espressif · STM32 · Texas Instruments · FreeRTOS · ESP-IDF · Arduino · Embedded Linux · WebAssembly · PlatformIO · Mongoose · libwebsockets · mbedTLS · OpenSSL

Compatible backends

      The list of compatible backends is growing

Open, extensible architecture

MicroOcpp is hardware-agnostic. The API allows to integrate it within the host system, to provide access to the hardware features and to implement custom use cases of OCPP. And a modular software architecture allows to introduce new features and to make something completely new.

Choose the best design for your Charge Point and MicroOcpp will work with it. Whether running it on the main controller or a separate OCPP core, or an external controller, the library will make the setup OCPP compatible.

As the world around the Charge Point changes, so do the protocols — and MicroOcpp. New releases will keep the Charge Point up-to-date with all new protocol revisions.

The Simulator – discover and test MicroOcpp

The Simulator is a PC application which contains a ported version of MicroOcpp. The Simulator directly connects to an OCPP server from the PC. A dashboard allows to trigger charger actions and to see the results.

Since the OCPP code in the Simulator and on the charger are the same, it greatly simplifies testing. The Simulator can be white‑labeled too and potential commercial customers of the charger can try it out on their PCs without the need for real hardware.

As an open source project, OCPP backend operators use the Simulator as a reference for building their own software or include it into their test base. A charger equipped with MicroOcpp comes with a broad test coverage already out-of-the-box.

To get started with MicroOcpp it's even better to dive directly into the sources on GitHub. Example Charge Point implementations for Espressif boards without HW are ready to be tested instantly.

Upgrade your product development with Commercial Support

#1 Integration and Maintenance

Get support for the integration and ongoing maintenance of OCPP. This accelerates the project time and helps to get software updates quickly.

#2 Testing and Code Reviews

Automated software tests and code reviews decrease the likelihood of charger downtimes in the field. New product updates are deployed easier with strong test suites.

#3 Compliance and Certification

Legal requirements on Chargers pose the risk of product development delays. First-hand technical experience on EV charging accelerates achieving the legally required certifications.

Cooperation partners & References


E-mail: matthias [A⊤] arduino-ocpp [DО⊤] com 

Don't hesitate to reach out for any questions.