-
Notifications
You must be signed in to change notification settings - Fork 7.4k
OCPP 1.6 native stack #68739
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
base: main
Are you sure you want to change the base?
OCPP 1.6 native stack #68739
Conversation
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 added project Note: This message is automatically posted and updated by the Manifest GitHub Action. |
f83d4ff
to
9bcf891
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial comments, will continue later.
lib/ocpp/src/core.c
Outdated
fn = ctx->cfn[UnlockConnector]; | ||
fn(buf, sizeof(buf), resp, uid); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using a fn variable seems pointless just for this one call, why not just do ctx->cfn[UnlockConnector](buf, ....);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made for better code readability
If this PR is still a draft (as indicated by the title), you can mark it as a draft in github. Search "Still in progress?" and there is a link at top right hand side of the page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial thoughts. I think such a library should get a separate entry in CODEOWNERS/Maintainers file - IMO it's way too specialized to fall under general "networking" umbrella.
9bcf891
to
85b37ad
Compare
aa9e763
to
e1b137b
Compare
depends on #66763 |
Describe OCPP Charge Point (CP) support and illustrate how to implement CP sample. Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
Add test suit for OCPP lib with one complete charging session with a random meter values. Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
A test sample for ocpp charge point with 2 connectors, central system steve server is used with test setup (public available) Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
add code owner for OCPP native stack Signed-off-by: Saravanan Sekar <saravanan@linumiz.com>
add json-c as external module and define CMake ane Kconfig compialtion control from zephyr tree. Commit also includes generated header files which are essential for compilation. config.h typically controls the available support in the toolchain and the current choice with zephyr is done using picolibc. Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com>
This commit adds the new external json-c modules to the MAINTAINERS.yml file. Signed-off-by: Parthiban Nallathambi <parthiban@linumiz.com>
my comments re: documentation have been addressed - thanks!
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
@ssekar15 are you planning to work on this PR? |
@jukkar yes for sure... looking for json dependency PR or alternative |
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
@ssekar15 I would suggest putting this PR In draft mode if it's not ready yet. This makes it clearer that it doesn't require attention from reviewers. Thanks! |
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Add a support for Open Charge Point Protocol(OCPP v1.6) native stack
Basic support for open charge point protocol v1.6 as native stack with
below functionality