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.

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

K01.FR.48 - Is this even reachable? #723

Open
Giavotto opened this issue Jul 31, 2024 · 1 comment
Open

K01.FR.48 - Is this even reachable? #723

Giavotto opened this issue Jul 31, 2024 · 1 comment

Comments

@Giavotto
Copy link
Contributor

Description

K01.FR.48 - Precondition -

When a SetChargingProfileRequest with a value for phaseToUse is received AND the EVSE is NOT capable of switching the phase connected to the EV, which is indicated by ACPhaseSwitchingSupported not being implemented or defined as false AND the EVSE is NOT going to use the received phaseToUse.

Within the description of phaseToUse in the ChargingSchedulePeriodType it says:

Optional. Values: 1..3, Used if numberPhases=1 and if the
EVSE is capable of switching the phase connected to the
EV, i.e. ACPhaseSwitchingSupported is defined and true.
It’s not allowed unless both conditions above are true. If
both conditions are true, and phaseToUse is omitted, the
Charging Station / EVSE will make the selection on its
own.

Functional Requirements K01.FR.19 and K01.FR.20 cover the above description.

In order to check the if the final condition in the precondition of K01.FR.48 has been satisfied, the JOET team was planning on using the PhaseRotation variable within the Connector component of the Device Model.

PhaseRotation is defined as a 3 character string consisting of the letters: R, S, T and x depending on what phases the EVSE is using.

Action Items

Is K01.FR.48 even a reachable condition?

If so, what is this covering that is not covered by K01.FR.19 and K01.FR.20?

@Giavotto
Copy link
Contributor Author

@Pietfried @marcemmers @RobertDeLeeuw ticket created according to the discussion today on the Cloud Communication Working Group.

@couryrr-afs couryrr-afs mentioned this issue Sep 17, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant