open-ocpp icon indicating copy to clipboard operation
open-ocpp copied to clipboard
verified publisher icon c-jimenez

Is it compatible with version ocpp 2?

Open Drus566 opened this issue 1 year ago • 3 comments

Hello, is the client compatible for use with OCPP 2.0 ? Any support planned? Maybe I can somehow help with implementation.

Thank you in advance!

Drus566 avatar Jul 15 '24 11:07 Drus566

Hi, It is not yet compatible, I am currently preparing the development branch to support OCPP2.0 => For now, I have moved OCPP1.6 specific code in dedicated namespaces/directories. I am currently implementing OCPP2.0 messages serialization/deserialization (shall be done before end of July). Then client charge point implementation can begin. If you can help with this last step it will be a pleasure.

c-jimenez avatar Jul 15 '24 18:07 c-jimenez

Thanks for the answer! I'll try to help with the transfer to version 2, just don't judge too harshly, I don't have much experience) Can you provide a source of information from which you learned C++?

Drus566 avatar Jul 16 '24 05:07 Drus566

Sorry for the late response.

The following branch contains all the necessary base classes to start working with OCPP 2.0.1 => https://github.com/c-jimenez/open-ocpp/tree/dev/ocpp20

A first ChargePoint20 class has been written to allow "low-level" usage of the stack and custom behaviors implementations.

The next step is to write a ChargePoint class similar to the one provided for OCPP1.6 with all the behavior which can be implemented by following the standard and which is not product specific.

Concerning the C++ part, I learned at school and by reading the C++ bible => https://stroustrup.com/4th.html.

c-jimenez avatar Oct 22 '24 19:10 c-jimenez

Hi @c-jimenez,

Are you planning to rebase a branch on 2.0? I'd like to help you move forward on this if possible. Is your branch functional for testing?

Thank you in advance!

jorisoffouga avatar May 28 '25 08:05 jorisoffouga

Hi @jorisoffouga, I won't have much time in the next few months to work on OCPP2.0.1. What I have planned in the next weeks:

  • Generate a 1.6.0 release based on the current status of the develop branch
  • Start a new develop16 branch on this tag for any bug fix needed for OCPP 1.6 only users
  • Merge the dev/ocpp20 branch into develop so that new developments will be focused on ocpp 2.X
  • Generate a 2.0.0 release with the low-level OCPP2.0.1 features

I will be more than happy if you can contribute to OCPP2.X development. The current status for the dev/ocpp20 branch is that it is stable enough for functional testing except for BasicChargePoint20 class which will still be under development. So you can start working using this branch and soon the develop branch.

c-jimenez avatar May 28 '25 10:05 c-jimenez

Hi @c-jimenez Thank you for integrating my pull requests. It's a pleasure to contribute to your project. Is it possible to rebase dev/ocpp20?

I'm starting development on version 2.0 next week. I won't hesitate to submit PRs if I see anything that needs improvement.

jorisoffouga avatar Jun 17 '25 19:06 jorisoffouga

@jorisoffouga : The develop branch is now the reference for OCPP2.X developments.

Thanks for your collaboration.

c-jimenez avatar Jun 19 '25 06:06 c-jimenez