Skip to content

Split ISO/DIN capabilities #31468

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
premultiply wants to merge 3 commits into from
Closed

Split ISO/DIN capabilities #31468

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b3ef8c0
split iso caps
premultiply Jul 4, 2026
a9f43e7
Merge master into feat/iso-din-caps
Copilot Jul 9, 2026
6e81aa6
Templates: rename WARP ISO capability key
Copilot Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion templates/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,17 @@ Note: The official website of the manufacturer or service provider is the refere

**Possible values**:

- `iso151182`: The device supports communicating via ISO 15118-2.
- `iso15118-2`: The device supports communicating via ISO 15118-2.
- `iso15118-20`: The device supports communicating via ISO 15118-20.
- `din70121`: The device supports communicating via DIN 70121.

@naltatis naltatis Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@premultiply can you phrase this from a user/feature perspective (identify, soc, ...).

@andig andig Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wofür brauchen wir das denn überhaupt also was würde ein Anwender mit der Information machen? Für evcc relevant ist das m.E. nur, wenn wir daraus evcc Fähigkeiten ableiten. Welche wären das jeweils (also z.B. SoC auslesen)?

@premultiply premultiply Jul 10, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ausgangspunkt: "iso151182" als einziges Capability-Tag ist sehr ungenau bzw. unzureichend.

Zu diskutieren ist natürlich ob man dies wie hier vorgeschlagen (weiter) anhand der gewählten aber nicht weniger für den gemeinen Anwender nicht so geläufigen Spec-Namen oder anderer Tags macht.

Ich habe Claude mal gezielt recherchieren lassen und die PR-Beschreibung aktualisiert.
Durchaus lesenswert als die gewünschte technische Hintergrundinformation über die jeweiligen Fähigkeiten der Protokolle/Spezifikationen.

@naltatis naltatis Jul 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important AC/DC nuance: ISO 15118-2 transmits SoC only for DC charging — the standard defines no SoC
field for AC sessions. Therefore a plain AC wallbox speaking ISO 15118-2 gets no SoC. Some AC wallboxes
(e.g. openWB Pro, using Bender CC613 / chargebyte / Hardy Barth controllers) work around this with a DC
handshake trick: at plug-in they briefly signal a DIN 70121 DC connection, read the SoC (and whatever battery
fields the car exposes) over that channel, tear it down, and then charge normally via IEC 61851-1 AC PWM. This
yields a one-time SoC at plug-in, not a continuously updated value.

Interesting. Hier passiert ja auch ein Mix an Standards. Spricht für mich auf jeden Fall dafür, dass wir hier auf die Feature-Ebene bei den Capabilities gehen sollten. Also sowas wie initialSoc, continuousSoc ...
Mit welchem Verfahren die Wallbox das dann mit dem Fahrzeug rausbekommt ist aus Nutzersicht (vmtl. sogar aus evcc-Sicht) ja Nebensache.

@andig andig Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ausgangspunkt: "iso151182" als einziges Capability-Tag ist sehr ungenau bzw. unzureichend.

Aber unzureichend wofür? Warum sollte uns das interessieren? Wir spezifizieren hier ja kein WB Datasheet? ich würde gerne nur Dinge dokumentieren, die wirklich für uns relevant sind.

- `mA`: The device supports granular (milliamp) current control.
- `rfid`: The device supports RFID.
- `1p3p`: The device supports 1P/3P phase switching.
- `battery-control`: The device supports battery control.
- `meter`: The device has a built-in energy meter.
- `dim`: The device supports EnWG §14a dimming.
- `curtail`: The device supports EEG §9 curtailment.
- `smahems`: The device can be used as an SMA HEMS device.

`capabilities` can be set at two levels:

Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/alpitronic.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ products:
- brand: Alpitronic
description:
generic: Hypercharger
capabilities: ["iso151182", "mA", "rfid", "meter", "dim"]
capabilities: ["din70121", "mA", "rfid", "meter", "dim"]
requirements:
evcc: ["sponsorship"]
params:
Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/elli-2.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ products:
- brand: Cupra
description:
generic: Charger Pro Eichrecht 2
capabilities: ["iso151182", "mA", "rfid", "1p3p", "meter", "dim"]
capabilities: ["iso15118-2", "mA", "rfid", "1p3p", "meter", "dim"]
requirements:
description:
de: |
Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/ghost.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ products:
- brand: Kontron Solar
description:
generic: Charger
capabilities: ["iso151182", "mA", "rfid", "1p3p", "meter", "dim"]
capabilities: ["iso15118-2", "mA", "rfid", "1p3p", "meter", "dim"]
requirements:
description:
de: |
Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/openwb-pro.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ products:
- brand: openWB
description:
generic: Pro
capabilities: ["iso151182", "mA", "1p3p", "meter", "dim"]
capabilities: ["iso15118-2", "din70121", "mA", "1p3p", "meter", "dim"]
params:
- name: host
render: |
Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/porsche-pmcc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ products:
- brand: Porsche
description:
generic: Mobile Charger Connect
capabilities: ["iso151182", "mA", "meter", "dim"]
capabilities: ["iso15118-2", "mA", "meter", "dim"]
params:
- preset: eebus
render: |
Expand Down
2 changes: 1 addition & 1 deletion templates/definition/charger/porsche-wallbox.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ products:
- brand: Porsche
description:
generic: Wallbox
capabilities: ["iso151182", "mA", "rfid", "1p3p", "meter", "dim"]
capabilities: ["iso15118-2", "mA", "rfid", "1p3p", "meter", "dim"]
requirements:
description:
de: |
Expand Down
4 changes: 2 additions & 2 deletions templates/definition/charger/tinkerforge-warp-ws.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,10 @@ template: tinkerforge-warp-ws
products:
- brand: TinkerForge
description: { generic: WARP4 Smart }
capabilities: ["iso151182", "rfid", "1p3p"]
capabilities: ["iso15118-2", "rfid", "1p3p"]
- brand: TinkerForge
description: { generic: WARP4 Pro }
capabilities: ["iso151182", "rfid", "1p3p", "meter"]
capabilities: ["iso15118-2", "rfid", "1p3p", "meter"]
- brand: TinkerForge
description: { generic: WARP3 Smart }
capabilities: ["rfid", "1p3p"]
Expand Down
4 changes: 3 additions & 1 deletion templates/definition/devices-schema.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,9 @@
"enum": [
"1p3p",
"battery-control",
"iso151182",
"iso15118-2",
"iso15118-20",
"din70121",
"rfid",
"smahems",
"mA"
Expand Down
11 changes: 6 additions & 5 deletions templates/definition/vehicle/iso15118.yaml → templates/definition/vehicle/iso15118-2.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,20 @@
template: iso15118
template: iso15118-2
covers: ["iso15118"]
products:
- description:
generic: ISO15118
capabilities: ["iso151182"]
generic: ISO 15118-2
capabilities: ["iso15118-2"]
group: generic
requirements:
description:
de: |
Nur unterstützt wenn das Fahrzeug den Ladestand (Soc) an die verbundene Wallbox übermitteln kann.
Bei Verwendung von ISO15118 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration
Bei Verwendung von ISO 15118-2 mit bestimmten VW Konzernfahrzeugen, z.B. Porsche Taycan, ist zusätzliche Konfiguration
im Fahrzeug erforderlich. Dafür muss ein aktives Ortsbezogenes Ladeprofil mit der niedrigsten Minimalladung (25%)
angelegt sein und Direktladen deaktiviert. Anderenfalls kann das Fahrzeug nicht in den Schalfmodus übergeben.
en: |
Only supported if the vehicle can provide the state of charge (Soc) to the connected charger.
Using ISO15118 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle.
Using ISO 15118-2 with some VW group vehicles, e.g. Porsche Taycan, requires additional configuration in the vehicle.
This requires an active location-based charging profile with the lowest minimum charge (25%) and direct charging disabled.
Otherwise the vehicle cannot be put into sleep mode.
params:
Expand Down
6 changes: 5 additions & 1 deletion util/templates/capability.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,11 @@ type Capability int
const (
_ Capability = iota
// ISO 15118-2 support
CapabilityISO151182 // iso151182
CapabilityISO151182 // iso15118-2
// ISO 15118-20 support
CapabilityISO1511820 // iso15118-20
// DIN 70121 support
CapabilityDIN70121 // din70121
// granular current control support
CapabilityMilliAmps // mA
// RFID support
Expand Down
78 changes: 43 additions & 35 deletions util/templates/capability_enumer.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading