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

Intro    Architecture    Simulator    CI/CD    Support    Contact

Optimized for microcontrollers

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

MIT license

No licensing fees · No usage limits

Private & public charging

Same API for private & public charging · Eichrecht-compliant

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

Compatible with the market-leading OCPP backends. For example:

      The list of public references is growing

Open, extensible architecture

MicroOCPP is a full implementation of the OCPP standard, but leaves the hardware-specific parts up to the charger firmware. This allows for portability to virtually any platform, regardless of the charging outlets, sensors or network stack.

The MicroOCPP API is a compact set of functions for the integration of OCPP into the charger. The main firmware uses the API to notify the OCPP server about the hardware status and reads back the OCPP commands from the server. A modular software architecture allows to alter existing features or to add completely new use cases.

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 Linux application which runs MicroOCPP on a desktop PC. The Simulator directly connects to an OCPP server from Linux. 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 used for integration testing within the target charging network. You can share the Simulator  with potential commercial customers too. They can try the OCPP interface on the PC immediately without waiting 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, there are also example integrations for microcontrollers on GitHub. Example Charge Point implementations for Espressif boards without external HW are ready to be tested instantly.

For backend developers build CI/CD pipelines with MicroOCPP

As an OCPP reference client, the Simulator is also useful for testing OCPP servers. The dashboard allows for manual tests for development and the IPC-interface of the Simulator then allows for automated tests from the CI/CD pipeline of an OCPP backend. Since the dashboard uses the same API, the transition from manual to automated tests is easy, and fast.

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


Email: matthias (A⊤) micro-ocpp (⊤) com 

Don't hesitate to reach out for any questions.