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

Allow resuming of transactions for OCPP1.6 #704

Merged
merged 3 commits into from
Jul 31, 2024

Conversation

Pietfried
Copy link
Contributor

@Pietfried Pietfried commented Jul 22, 2024

Describe your changes

Allow resuming of transactions for OCPP1.6:

  • charge_point.start() function can now receives a set of active transactions
  • If an internal transaction in libocpp can be identified from the internal database and the session_id is also listed in the set of active transactions, libocpp will resume the transaction
  • If an internal transaction in libocpp can be identified from the internal database and the session_id is not listed in the set of active transactions, libocpp will initiate a StopTransaction.req

Issue ticket number and link

Companion PR in everest-core: EVerest/everest-core#789

Checklist before requesting a review

* charge_point.start() function can now receives a set of active transactions
* If an internal transaction in libocpp can be identified from the internal database and the session_id is also listed in the set of active transactions, libocpp will resume the transaction
* If an internal transaction in libocpp can be identified from the internal database and the session_id is not listed in the set of active transactions, libocpp will initiate a StopTransaction.req

Signed-off-by: pietfried <[email protected]>
Signed-off-by: pietfried <[email protected]>
@Pietfried Pietfried force-pushed the feature/resume-transactions-ocpp16 branch from 67aa756 to c70334a Compare July 26, 2024 10:43
@Pietfried Pietfried merged commit aab1d57 into main Jul 31, 2024
4 checks passed
@Pietfried Pietfried deleted the feature/resume-transactions-ocpp16 branch July 31, 2024 10:44
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.

2 participants