Skip to content
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

Jump to bottom

Unklare Differenzierung zwischen ChargingStationStatus und ChargingPointStatus (Prio: Medium) #2

Open
meppingvector opened this issue Sep 30, 2021 · 9 comments · Fixed by #4 or #28
Open

Unklare Differenzierung zwischen ChargingStationStatus und ChargingPointStatus (Prio: Medium) #2

meppingvector opened this issue Sep 30, 2021 · 9 comments · Fixed by #4 or #28
Assignees
@maikwoehl-psi
Labels
breaking change inkompatible Schemaänderung discussion required to be discussed in VDV463 WG specification Improvements or additions to specification
Milestone
Version 2.0.0

Comments

@meppingvector
Copy link

Unklare Differenzierung zwischen ChargingStationStatus [Available, Unavailable, Faulted] und ChargingPointStatus [Available, Occupied, Reserved, Unavailable, Faulted].
Haben die ChargingPointStatus Parameter einen Einfluss auf den ChargingStationStatus, z.B. durch eine Aggregation? Es ist eine detailliertere Definition notwendig.

Änderungsvorschlag:
Folgende Interpretation von ChargingStationStatus wird als Beschreibungstext im Dokument hinzugefügt.
ChargingStationStatus:
Available: Untergeordnete Ladepunkte haben den Status Available, Occupied oder Reserved.
Unavailable: Einer der untergeordneten Ladepunkte hat den Status Unavailable.
Faulted: Einer der untergeordneten Ladepunkte hat den Status Faulted.
@maikwoehl-psi
Copy link
Collaborator

Da sowohl OCPP 1.6 als auch OCPP 2.0.1 keine genauere Angabe zur Ladestation, sondern nur zum Ladepunkt machen, erscheint mir das als eine sinnvolle Ergänzung.

@maikwoehl-psi maikwoehl-psi added the specification Improvements or additions to specification label Feb 21, 2022
@maikwoehl-psi
Copy link
Collaborator

Das muss ich revidieren. ConnectorID=0 beschreibt den Hauptcontroller der Ladestation. Das kann dann für ChargingStationStatus verwendet werden.

A status can be reported for the Charge Point main controller
(connectorId = 0) or for a specific connector. Status for the Charge Point main controller is a subset of
the enumeration: Available, Unavailable or Faulted.
States considered Operative are: Available, Preparing, Charging, SuspendedEVSE, SuspendedEV,
Finishing, Reserved. States considered Inoperative are: Unavailable, Faulted.

Außerdem wurde Occupied ja aufgeteilt:

The Occupied state as defined in previous OCPP versions is no longer relevant.
The Occupied state is split into five new statuses: Preparing, Charging,
SuspendedEV, SuspendedEVSE and Finishing.

@maikwoehl-psi
Copy link
Collaborator

maikwoehl-psi commented Mar 3, 2022 •
edited
Loading

So wie es aussieht, hat sich das in OCPP 2.0.1 geändert. Dort steht:

When a Connector (or the EVSE or the entire Charging Station it belongs to) has reported an error and is not
available for energy delivery. (Inoperative).

Also kann man das bei OCPP 2.0.1 nicht mehr konkret am Stecker festmachen, ob das ein Fehler des Steckers ist, oder von der Hauptplatine, wie mir scheint.

@maikwoehl-psi
Copy link
Collaborator

Gibt es in OCPP 2.0.1 noch die Möglichkeit den MainController anzusprechen (per StatusNotification)?

@maikwoehl-psi maikwoehl-psi self-assigned this Mar 22, 2022
@maikwoehl-psi
Copy link
Collaborator

Das Attribut chargingStationStatus wird ersatzlos gestrichen.

@maikwoehl-psi
Copy link
Collaborator

Erwarte Pull-Request zu diesem Issue

@maikwoehl-psi maikwoehl-psi reopened this Mar 22, 2022
BenjaminKowatschVector added a commit to BenjaminKowatschVector/VDV463 that referenced this issue Mar 23, 2022
@BenjaminKowatschVector
Add v1.1 JSON schemas fixing issues VDVde#2 and VDVde#3
4157033
@maikwoehl-psi maikwoehl-psi linked a pull request Oct 27, 2022 that will close this issue
Add v1.1 JSON schemas fixing issues #2 and #3 #4
Merged
maikwoehl-psi added a commit to maikwoehl-psi/VDV463 that referenced this issue Jan 30, 2023
@maikwoehl-psi
Merge remote-tracking branch 'remotes/upstream/v1.1-dev' into Fix-iss…
4e663db 
…ues-VDVde#2-VDVde#3
@maikwoehl-psi maikwoehl-psi added this to the Version 1.1 milestone Jul 4, 2023
@amotech-mdo amotech-mdo linked a pull request Jul 4, 2023 that will close this issue
removing "uri" format constraint from all string identifiers #15
Closed
BenjaminKowatschVector added a commit to BenjaminKowatschVector/VDV463 that referenced this issue Oct 24, 2023
@BenjaminKowatschVector
Merge branch 'v1.1-dev' into Fix-issues-VDVde#2-VDVde#3
6d15dbe
@maikwoehl-psi
Copy link
Collaborator

maikwoehl-psi commented Oct 25, 2023 •
edited
Loading

  • Schemaänderung
  • Spezifikationsdokument noch ändern?

@maikwoehl-psi maikwoehl-psi added ready Ready to Merge and removed ready Ready to Merge labels Oct 25, 2023
@maikwoehl-psi
Copy link
Collaborator

maikwoehl-psi commented Jan 17, 2024 •
edited
Loading

Grafiken: #4 (comment)

maikwoehl-psi added a commit that referenced this issue Jan 17, 2024
@maikwoehl-psi
Merge pull request #4 from BenjaminKowatschVector/Fix-issues-#2-#3
bb9272b 
Add v1.1 JSON schemas fixing issues #2 and #3
@maikwoehl-psi
Copy link
Collaborator

grafik

@maikwoehl-psi maikwoehl-psi added the ready Ready to Merge label Jan 18, 2024
@DohmenClaus DohmenClaus added the breaking change inkompatible Schemaänderung label Feb 26, 2024
@DohmenClaus DohmenClaus modified the milestones: Version 1.1, Version 2.0 Feb 26, 2024
@DohmenClaus DohmenClaus added discussion required to be discussed in VDV463 WG and removed ready Ready to Merge accepted labels Feb 26, 2024
DohmenClaus added a commit that referenced this issue Feb 26, 2024
@DohmenClaus
Revert "Add v1.1 JSON schemas fixing issues #2 and #3"
3f9b706
DohmenClaus added a commit that referenced this issue Jul 8, 2024
@DohmenClaus
Merge pull request #28 from VDVde/revert-4-Fix-issues-#2-#3
dec81bb 
Revert "Add v1.1 JSON schemas fixing issues #2 and #3"
@maikwoehl-psi maikwoehl-psi linked a pull request Jul 8, 2024 that will close this issue
Revert "Add v1.1 JSON schemas fixing issues #2 and #3" #28
Merged
maikwoehl-psi added a commit that referenced this issue Dec 2, 2024
@maikwoehl-psi @BenjaminKowatschVector
@amotech-mdo @DohmenClaus @Basler182
Merge v1.1.0 to main (#38)
4cdb5df 
* Add v1.1 JSON schemas fixing issues #2 and #3

* Fixes #5

* removing "uri" format constraint from all string identifiers

as agreed in the VDV 463 meeting

* removing "uri" format constraint from all string identifiers

* removing "uri" format constraint from all string identifiers

* Remove obsolete whitespace changes

* #20: Allow empty arrays

* #22: Allow empty ChargingPredictionData

* #22: Add structure ChargingPredictionDataDepartureTime to ChargingPredictionData

* #22: Fix descriptions

* Update v1.1/ProvideChargingInformationRequest.json

Co-authored-by: Maik Wöhl <[email protected]>

* Update v1.1/ProvideChargingInformationRequest.json

Co-authored-by: Maik Wöhl <[email protected]>

* Add critical condition for tractionBattery, add hydrogentankinfo (#16)

* Add critical condition for tractionBattery, add hydrogentankinfo

* Move vehicleInfo into it's own list

* Add VehicleId to ChargingPointInfo to reference it

* Switch criticalCondition to integer to reflect SNA values

* Revert "Add VehicleId to ChargingPointInfo to reference it"

This reverts commit d14814e.

Revert "Move vehicleInfo into it's own list"

This reverts commit 0aa89ce.

* Rename criticalCondition to status

* Revert "Add v1.1 JSON schemas fixing issues #2 and #3"

* Add evccId to VehicleInfo structure

Closes #30

* Revert "Add critical condition for tractionBattery, add hydrogentankinfo (#16)"

This reverts commit c82bf61.

* Add Validations to JSON Schema Properties (#36)

* Move changes of v1.1 to v1.0

Signed-off-by: Maik Wöhl <[email protected]>

* Rename v1.0 to schema

Signed-off-by: Maik Wöhl <[email protected]>

---------

Signed-off-by: Maik Wöhl <[email protected]>
Co-authored-by: Kowatsch, Benjamin <[email protected]>
Co-authored-by: Dominique Müller <[email protected]>
Co-authored-by: Benjamin Kowatsch <[email protected]>
Co-authored-by: DohmenClaus <[email protected]>
Co-authored-by: Kilian Schneider <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maikwoehl-psi maikwoehl-psi

Labels
breaking change inkompatible Schemaänderung discussion required to be discussed in VDV463 WG specification Improvements or additions to specification
Projects
None yet
Milestone
Version 2.0.0
3 participants
@maikwoehl-psi @meppingvector @DohmenClaus