KameCore

ISO 15118-2/-20 and OCPP 2.0.1/2.1 Software Stacks

Technical implementation details for V2G communication, CSMS integration, and deployment on KameCore modules or third-party hardware.

Software Architecture

  • - Split runtime between real-time EVSE control (IEC 61851 state machine) and Linux user-space protocol services.
  • - ISO 15118 communication over GreenPHY PLC: SLAC, IPv6, TCP/TLS, SDP, EXI codec, and session lifecycle orchestration.
  • - PKI services for Plug & Charge certificate installation, chain validation, and revocation checks.
  • - Device-model bridge that maps meter values, connector states, and diagnostics into OCPP data structures.
  • - Persistent event store for transaction events, signed metering records, and offline replay after reconnect.
  • - Northbound adapters for REST/OCPI/MQTT integrations with billing and enterprise EMS backends.

ISO 15118-2/-20 and V2G

Our SECC stack is built for production interoperability, not only lab demos, with strict timeout handling and state rollback logic.

ISO 15118-2 scope

  • - Full session flow: SupportedAppProtocol, SessionSetup, ServiceDiscovery, Authorization, ChargeParameterDiscovery, PowerDelivery, SessionStop.
  • - DIN 70121 fallback for legacy EV interoperability.
  • - TLS profile hardening and configurable retry windows for unstable PLC environments.
  • - Contract certificate handling for Plug & Charge with EIM fallback.

ISO 15118-20 scope

  • - Bidirectional Power Transfer (BPT) support for AC/DC use cases.
  • - Schedule exchange with target profile negotiation under EVSE power limits.
  • - Session renegotiation paths without tearing down the communication channel.
  • - Extensible message handlers for optional services without rewriting the core stack.

V2G control loop

  • - Real-time mapping from EV requests to converter setpoints with safety interlocks.
  • - Power shaping based on site load limits, thermal derating, and tariff windows.
  • - Deterministic trace logs for compliance evidence and dispute resolution.

OCPP 2.0.1 and 2.1

A versioned protocol layer lets the same charger firmware interoperate with OCPP 1.6J, 2.0.1, or 2.1 backends.

  • - Full device-model mapping for components, variables, monitoring, and remote configuration.
  • - TransactionEvent pipeline with deterministic ordering and signed meter-value handling.
  • - Smart charging profile merge with local load manager constraints and ISO 15118 schedules.
  • - Security event reporting and certificate management for secured deployments.
  • - Offline buffer and idempotent replay strategy to preserve transaction integrity.
  • - Remote diagnostics with structured logs and triggerable data collection.
  • - Interoperability validation against major CSMS implementations before release.

Deployment and Porting

The stack is delivered for KameCore modules and can be ported to third-party hardware through a HAL adaptation layer.

  • - KameCore STM32MP151/STM32MP157 modules with Yocto-based secure images.
  • - Third-party ARM/x86 platforms with custom metering, contactor, and CP/PP interfaces.
  • - Hybrid deployments with local edge gateways and centralized cloud CSMS.

Integration deliverables

  • - BSP integration guide and deterministic startup sequencing.
  • - Protocol conformance results and interoperability matrix.
  • - CI test suites with EV/EVSE/CSMS simulators.
  • - Commissioning scripts for certificate provisioning and backend onboarding.
ISO 15118-2/-20 and OCPP 2.0.1/2.1 Stacks | KameCore