Error Reporting via OCPP201 #824
Merged
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
…w the EventDataType is derived from the EVerest Error Type Signed-off-by: pietfried <[email protected]>
Pietfried
force-pushed
the
feature/ocpp201-error-handling
branch
2 times, most recently
from
0b39a5d
to
8256c5f
Compare
…ceived within EVerest. Added documentation about the current limitations, which includes that currently no proper mapping to Components and Variables is implemented Signed-off-by: pietfried <[email protected]>
Pietfried
force-pushed
the
feature/ocpp201-error-handling
branch
from
8256c5f
to
52e9fc7
Compare
hikinggrass
approved these changes
Oct 14, 2024
hikinggrass
added
the
include-in-release
hikinggrass
pushed a commit
that referenced
this pull request
Oct 25, 2024
* Implemented on_event in OCPP201 and add documentation for how the EventDataType is derived from the EVerest Error Type * Added implementation to trigger NotifyEvent.req in case errors are received within EVerest. Added documentation about the current limitations, which includes that currently no proper mapping to Components and Variables is implemented --------- Signed-off-by: pietfried <[email protected]>
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
This PR adds support for reporting errors that are raised within EVerest over OCPP2.0.1. Errors that are reported will initiate a NotifyEvent.req using the information provided via the Error object.
Adds documentation for the Error Handling via OCPP2.0.1.
Current Limitations
In OCPP2.0.1 errors can be reported using the
NotifyEventRequestmessage. The
eventDataproperty carries the relevant information.This format of reporting errors deviates from the mechanism used within
EVerest. This data structure forces to map an error to a
component-variable combination. This requires a mapping
mechanism between EVerest errors and component-variable
combination.
Currently this module maps the Error to one of these three Components:
The Variable used as part of the NotifyEventRequest is constantly defined to
Problemfor now.The goal is to have a more advanced mapping of reported errors to the respective component-variable combinations in the future.
Issue ticket number and link
Checklist before requesting a review