Background image: EV charging station controller engineering (PCB, oscilloscope, laptop).

OCPP 2.0.1 embedded software for EV chargers and gateways

Delivered by dedicated teams for German/EU OEMs and integrators: interoperability-focused commissioning, backend/CSMS integration, TLS + certificate lifecycle, diagnostics/log artifacts, and requirements-to-test traceability. OCPP 2.1 is roadmap (planning & migration). OCTT-aligned where applicable.

  • Interoperability
  • Commissioning support
  • Traceability
  • Logs & artifacts
  • TLS + cert lifecycle
Talk to our eMobility team →

◈ Technical Summary

We support OCPP 2.0.1 implementation and backend integration, plus embedded development for chargers and gateways. Testing is designed to be OCTT-aligned where applicable, with reproducible diagnostics on target hardware.

  • Implementation + Integration Profile alignment, message flows, reconnect/error handling, commissioning support.
  • Embedded stack delivery HAL integration, protocol layer, application logic, source code + documentation.
  • Test readiness Automated tests, integration tests, and structured validation on target setups.
  • Diagnostics Structured logs and traceability support to speed up debugging and verification.

◈ What FlexCharge.OCPP is

Embedded OCPP software stack for EV charging stations, designed for interoperability, testability, and long-term maintainability.

Modular embedded stack AC/DC charging stations, clean module boundaries, configurable features.
OCPP 2.0.1 Core support today; OCPP 2.1 planned based on requirements and standards adoption.
For OEMs & integrators Built for charger products and engineering teams, not end users.
Source + documentation Delivered as source code with integration support and interface documentation.
Target platforms Runs on common MCU and Linux-based charger controller platforms.
Interop focus Backend/CSMS interoperability validation and reproducible diagnostics.

How This Accelerates Your Project

For pilots, we can provide a controlled evaluation scope for technical validation: architecture review, integration fit, and constraints verification. Delivery remains source code + documentation + integration support.

FlexCharge.OCPP packages reusable components and integration patterns refined across multiple charging projects so your team focuses on differentiation instead of rebuilding protocol fundamentals.

Architecture validation Start from a proven OCPP 2.0.1 baseline; confirm fit for your hardware, backend, and required profiles.
Reduced integration risk Reuse tested modules for transport/session handling, security/cert lifecycle, and diagnostics.
Faster time-to-market Skip foundational protocol work and accelerate commissioning, reconnect/error paths, and interoperability hardening.
Interoperability confidence Designed for structured test readiness (OCTT-aligned where applicable) with reproducible logs and traceability.

Delivery models

Dedicated teams Staff augmentation Project-based integration
Want a fast technical assessment? Send: backend/CSMS, target hardware/OS, required OCPP profiles.
Schedule a technical review →

◈ Testing & Conformance Pathway

We engineer for testability and certification from day one: reproducible evidence, traceable requirements, and structured validation on target hardware.

Structured validation Requirements → implementation → test traceability, with clear pass/fail artifacts.
OCTT alignment Use OCTT test suites where available for the target OCPP version; document gaps and mitigation if suites are incomplete.
QA discipline Unit tests, static analysis, regression testing, and integration validation across message flows and error paths.
Certification evidence Generate logs, reports, and documentation needed for audits and certification pathways.
Note: Conformance tooling depends on OCPP version and suite availability. We keep the test plan explicit: what is covered by automated suites (e.g., OCTT), what is validated by integration tests on your platform, and what evidence is produced.

Charging Station Software Stack

High-level view of the main modules and how they connect: protocol core, transport, security, hardware interfaces, diagnostics, and lifecycle/update integration.

Architecture

◈ Architecture Overview

The stack is split into modules with narrow interfaces. Protocol logic is separated from transport, security, and hardware control. Diagnostics and lifecycle behavior use shared APIs so modules can be instrumented and updated without tight coupling.

Diagram

◈ Module relationships

Communication layer
Transport, sessions, codecs,
dispatch in/out
OCPP Core
Routing, state machines,
profiles, device model
Security & certificates
TLS, cert lifecycle,
policy checks
Diagnostics & logging
Logs, metrics, traces,
export/adapters
Update & lifecycle hooks
Boot/shutdown hooks,
update integration
Hardware abstraction
Drivers, IO adapters,
metering/peripherals

• OCPP Core

  • Boundary: routing, state machines, profile logic, device model updates.
  • Interfaces: consumes decoded messages + connection state; emits outbound messages + internal events.
  • Extension: handler registration, feature flags, hooks for vendor-specific mapping.

• Communication layer

  • Boundary: sessions (connect/reconnect), framing, codecs, dispatch.
  • Interfaces: send/receive APIs, connection callbacks, codec registry.
  • Extension: transport selection, backoff policy, metrics/tracing hooks.

• Security & certificates

  • Boundary: TLS config, provisioning/rotation, policy checks.
  • Interfaces: TLS integration with transport; status checks for core logic.
  • Extension: trust stores, rotation hooks, secure element/keystore providers.

• Hardware abstraction

  • Boundary: metering, relays, connector lock, RFID, IO.
  • Interfaces: capability-based APIs upward; adapters hide vendor differences.
  • Extension: platform implementations, peripheral plugins, feature gating.

• Diagnostics & logging

  • Boundary: logs, metrics, traces, export workflows.
  • Interfaces: shared API across modules; export adapters for upload/local.
  • Extension: sinks, correlation IDs, sampling, per-module log levels.

• Update & lifecycle hooks

  • Boundary: startup/shutdown sequencing, lifecycle transitions, update hooks.
  • Interfaces: lifecycle callbacks; controlled restart/shutdown APIs.
  • Extension: update strategy, pre/post hooks, payload retrieval adapters.

◈ Want this architecture implemented on your hardware?

Schedule a technical review to confirm scope and constraints. We validate platform/OS, required OCPP profiles, backend behavior, security/cert lifecycle, and test approach.

Send these three inputs: backend/CSMS name, target hardware/OS, required OCPP profiles.

Schedule a technical review →

Standards and interoperability focus

The stack is engineered around predictable backend behavior, test readiness, and evidence-driven validation for EU delivery expectations.

  • OCPP 2.0.1 aligned implementation Profiles, message flows, and error paths implemented with explicit conformance targets.
  • Backend-agnostic design Clean transport and integration boundaries to support multiple CSMS backends.
  • Interoperability-driven development Validation focuses on real-world flows: reconnect behavior, timeouts, retries, and edge cases.
  • Formal test readiness OCTT-style process discipline where applicable: reproducible tests and traceable artifacts.
  • Traceability Clear links between requirements, implementation decisions, and verification evidence.
  • German/EU delivery expectations Documentation and validation structured for audits, handover, and long-term maintainability.

What you get when working with our team

Software deliverables

Technical outcomes you can ship and maintain.

  • Production-ready OCPP implementation tailored to your controller platform and constraints.
  • Interface documentation and integration guides for your firmware, backend, and tooling.
  • Test strategy + validation plan aligned with your CSMS/backend behaviors and target flows.

Engineering support

How delivery works inside your engineering workflow.

  • Dedicated engineers integrated into your repo, CI, and release process.
  • Requirements + traceability to keep scope, tests, and evidence consistent.
  • Maintenance + protocol evolution support (bug fixing, profile additions, upgrades).

Who FlexCharge.OCPP is for

For

  • Charger OEMs
  • Industrial EVSE manufacturers
  • System integrators building charger firmware

Not for

  • End consumers
  • Fleet operators looking for SaaS backends
  • White-label consumer apps

How engagement works

Typical delivery flow from first validation to rollout. Scope and artifacts are kept traceable so integration and testing remain predictable.

  • Evaluation phase (technical discussion, architecture review, integration constraints).
  • Pilot or integration phase (repo/CI setup, message flows, target-hardware validation).
  • Production rollout (stabilization, release support, handover documentation).
  • Optional long-term support (maintenance, protocol evolution, new profiles/backends).
All delivery includes German/EU timezone alignment and communication in English or German.

FAQ

Is this a SaaS platform?

No. This is embedded software for charging stations and gateways. You deploy it on your hardware; the CSMS/backend can be yours or a third-party system.

Do you provide complete charger firmware development?

Yes, depending on scope. We can deliver the software stack from the hardware abstraction layer (HAL) through the OCPP protocol layer to application logic. The split between our code and your existing components is defined per platform and project scope.

Can we run it on our own hardware?

Yes. Hardware-specific functionality is implemented behind a hardware abstraction layer (HAL), so protocol and application logic can be ported to your target platform. We adapt the HAL to your specific hardware.

Which OCPP versions are supported?

Core focus is OCPP 2.0.1. OCPP 2.1 support is planned/on the roadmap and is aligned with customer requirements and standards adoption. Supported profiles and optional features are defined per project scope.

Can it integrate with existing backends?

Yes. Integration with an existing CSMS/backend is supported as long as the OCPP version and required profiles are aligned. We validate message flows and error/reconnect behavior during integration testing.

How is QA handled?

QA combines automated tests with integration tests on target hardware using an OCTT-aligned process. Where OCTT test suites are available for the target OCPP version, we use them to validate conformance. This typically includes unit tests for protocol/core logic, integration tests for transport/TLS and message flows, and structured logs to support reproducible debugging.

Can you augment our existing engineering team?

Yes. We can provide embedded and OCPP engineers who work within your repositories, coding standards, CI, and release process. Typical support includes feature delivery, bug fixing, protocol compliance work, and hardware porting.

What's your experience with German/EU charger manufacturers?

We align with delivery expectations common in German/EU contexts: backend interoperability, clear test readiness and traceability, explicit security handling (TLS and certificate lifecycle), and integration support during commissioning and field troubleshooting.

What about standards compliance and certification?

We engineer with testability and certification in mind. Our process includes traceability from requirements to tests, structured validation, and documentation support for certification pathways, including an OCTT-aligned approach where applicable.

Need this architecture implemented on your hardware?

Schedule a technical review to confirm scope and constraints before implementation. We review the target platform, required OCPP profiles, backend behavior, security/cert handling, and test approach.

  • Target hardware/OS, HAL scope, peripherals (metering, lock, RFID, IO)
  • OCPP version/profiles and required optional features
  • CSMS/backend integration: message flows, reconnect/error handling
  • TLS + certificate lifecycle requirements
  • QA plan: automated tests, integration tests, OCTT alignment where applicable

For exact compatibility confirmation, send your backend name, target hardware/OS, and required OCPP profiles via Contact.

Schedule a technical review →