Ocpp-809 Driver [hot] May 2026

It looks like you're asking for a feature overview (or technical briefing) on an “OCPP-809 driver.”

However, there is no official standard called “OCPP-809” in the Open Charge Point Protocol (OCPP) ecosystem (OCPP 1.6, 2.0.1, and 2.1 are the main versions). ocpp-809 driver

Most likely, you mean one of these:

  1. OCPP 1.6 (or 2.0.1) – 80x series driver – e.g., for an 800 kW split charger or a specific power module controller (like in Delta, Infy, or Huawei chargers).
  2. A vendor-specific implementation – “809” might be a firmware version, hardware platform, or internal product code for a charger model (e.g., “ABB 809” or “EO 809”).
  3. A typo – You meant OCPP-1.6-J (JSON) driver.
  4. A serial-to-OCPP gateway driver – using an 809-series RS485/CAN to OCPP converter.

Future of OCPP-809 Drivers: Moving to OCPP 2.0.1

The EV industry is shifting to OCPP 2.0.1 (which introduces ISO 15118 Plug & Charge and Device Model). Legacy 809 drivers built for 1.6 will soon be obsolete. It looks like you're asking for a feature

Look for next-gen drivers that support:

  • OCPP 2.0.1 Device Model: Representing the 809 board as a set of "Variables" and "Components."
  • Security: TLS 1.3 and Basic Auth passwords (not just insecure WebSockets).
  • Flexible Tariff Mapping: Converting Modbus energy pulses to OCPP Tariff objects.

⚙️ Hardware‑specific “809 driver” features (if it’s a power stage controller)

  • Load balancing – dynamic phase rotation, current limit per connector
  • Thermal management – derating if >80°C (809 series modules)
  • AC/DC fault handling – ground fault, relay weld detection
  • LCD / UI control – show session info, QR code for auth
  • RFID whitelist sync from CSMS

Use Case 2: DIY Open Source Chargers

Hobbyists using the "QC809" control board to build a 22kW AC charger need a software bridge. The open-source community (EVerest, OpenEVSE) uses 809 drivers to allow the DIY charger to appear as legitimate OCPP hardware on networks like Shell Recharge. OCPP 1