Add In Depth Smart Charging Documentation #905
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Daniel Moore <[email protected]>
Signed-off-by: Daniel Moore <[email protected]>
…plainations apart from smart charging Signed-off-by: Piet Gömpel <[email protected]>
Pietfried
requested review from
hikinggrass,
marcemmers and
maaikez
as code owners
maaikez
reviewed
Dec 10, 2024
| 2. External Charging Limit-based Smart Charging (K11–K14) | ||
| 3. ISO 15118-based Smart Charging (K15–K17) | ||
|
|
||
| Support for General and External Charging Limit-based Smart Charging is largely complete, with ISO 15118-based Smart Charging under active development. For an up-to-date overview of exactly which features are currently supported as well as design decisions that have been made to address optional or ambiguous functional requirements, please refer to the [OCPP 2.0.1 Status document](ocpp_201_status.md). |
There was a problem hiding this comment.
How do you remember to change this line as soon as it is totally complete?
maaikez
approved these changes
Dec 10, 2024
| ChargePoint->>+DeviceModel : SmartChargingCtrlrAvailable? | ||
| DeviceModel-->>-ChargePoint : Component | ||
|
|
||
| rect rgb(128,202,255) |
There was a problem hiding this comment.
White on light blue is very hard to read.
| | `TxProfileEvseIdNotGreaterThanZero` | `TxProfile` needs to have an `evseId` greater than 0. [K01.FR.16] | | ||
| | `TxProfileMissingTransactionId` | A `transactionId` is required for`SetChargingProfileRequest`s with a `TxProfile` in order to match the profile to a specific transation. [K01.FR.03] | | ||
| | `TxProfileTransactionNotOnEvse` | Happens when the provided `transactionId` is not known. [K01.FR.33] | | ||
| | `TxProfileConflictingStackLevel` | Happens when a TxProfile has a stackLevel and transactionId combination already exists in a TxProfile with a different id in order to ensure that no two charging profiles with same stack level and purpose can be valid at the same time. [K01.FR.39] | |
There was a problem hiding this comment.
On other places, TxProfile and transactionId has backtics (TxProfile and transactionId)
| | `ChargingProfileNoChargingSchedulePeriods` | Happens when the `ChargingProfile` doesn't have any Charging Schedule Periods. | | ||
| | `ChargingScheduleChargingRateUnitUnsupported` | Happens when a chargingRateUnit is passed in that is not configured in the `ChargingScheduleChargingRateUnit`. [K01.FR.26] | | ||
| | `ChargingSchedulePeriodInvalidPhaseToUse` | Happens when an invalid `phaseToUse` is passed in. [K01.FR.19] [K01.FR.48] | | ||
| | `ChargingSchedulePeriodPhaseToUseACPhaseSwitchingUnsupported` | Happens when phaseToUse is passed in and the EVSE does not have `ACPhaseSwitchingSupported` defined and set to true. [K01.FR.20] [K01.FR.48] | |
There was a problem hiding this comment.
phaseToUse backtics? (phaseToUse)
Like in other places.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
New PR taking parts of #836 for documentation of in depth smart charging use cases.
Issue ticket number and link
Checklist before requesting a review