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

connector inoperative overridden #690

Closed
wants to merge 3 commits into from

Conversation

james-ctc
Copy link
Contributor

@james-ctc james-ctc commented May 16, 2024

Describe your changes

When OCPP ChangeConfiguration to Inoperative is set this is overridden on EVerest restart.
In addition some actions on the CP line were causing the state to leave DISABLED.

This work is based upon:
#505

This changed is linked with
EVerest/libocpp#623

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

@james-ctc james-ctc force-pushed the fix/connector-inoperative-overridden branch from a6e48bc to 3a0f1b6 Compare May 16, 2024 13:57
@james-ctc james-ctc marked this pull request as ready for review May 16, 2024 14:10
types/evse_manager.yaml Outdated Show resolved Hide resolved
types/evse_manager.yaml Outdated Show resolved Hide resolved
corneliusclaussen and others added 3 commits May 17, 2024 09:41
It replaces the old enable/disable commands and adds a source and
priority. See README of the API module for more details.

Compile time breaking change on the evse_manager interface.
All enable/disable calls need to be switched over to the new
enable_disable call, for everest-core this is done in this PR.

In some uses cases it is useful if e.g. a LocalAPI source disables
a connector that only the same local source can enable again.
Think of a service technician who has an app to disable the connector
locally. Then it should be prevented that it is re-enabled by the CSMS
until the service technician enables it again via the same app.
Using priorities this is quite flexible and a lot of use-cases can
be implemented without a change in EVerest code.

The API module also has a new enable_disable command. It also has
compatibility implementations for the old enable/disable commands.

Signed-off-by: Cornelius Claussen <[email protected]>

fix: merge issues
fix: updated README

Signed-off-by: James Chapman <[email protected]>
@james-ctc james-ctc force-pushed the fix/connector-inoperative-overridden branch from 91f4e73 to 451ee5d Compare May 17, 2024 08:42
@james-ctc james-ctc changed the base branch from main to feature/enable_disable_source May 17, 2024 08:43
@Pietfried Pietfried force-pushed the feature/enable_disable_source branch 2 times, most recently from b0b0f7b to dbc8527 Compare May 30, 2024 07:58
Base automatically changed from feature/enable_disable_source to main June 3, 2024 11:27
@Pietfried
Copy link
Contributor

This issue has been adressed by: #714

@Pietfried Pietfried closed this Jun 11, 2024
@james-ctc james-ctc deleted the fix/connector-inoperative-overridden branch September 17, 2024 12:45
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

Successfully merging this pull request may close these issues.

4 participants