Skip to content

Conversation

@zhenbin-lin
Copy link

Hi @matth-x

I've created a new service called DataTransferService designed to route various types of DataTransfer Message based on vendorId and messageId.

For the upcoming development work, could you please create a new branch named feature/california-pricing-requirements? Alternatively, would it be better if I push my code directly to the existing develop/remodel-api branch?

Also, could you please check if there are any existing issues or discussions related to this RP that I should be aware of?

Thanks for your help!

1. Separate the message processing of OCPP1.6 and OCPP2.0.1
2. Reserve complete DataTransfer packets for extended DataTransfer operations
1. Finish base request for cost and idle fee.
2. Add new unit tests for operations of FinalCost, RunningCost and UserPrice.
3. Add a new funcation triggerMeterValues in MeteringService in order
   making external Services to trigger MeterValue.
4. Modify CMakeLists.txt add California Service.
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.

3 participants