-
Notifications
You must be signed in to change notification settings - Fork 9
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
Adding basic dynamic mode #42
Conversation
…rialization ScheduleExchange messages tests Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
…arge_dynamic_mode to feedback Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
…mobilityneeds (1 and 2) modes in the EvseSetupConfig struct Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
…needs_mode support to schedule_exchange & dc_charge_loop, adding dc_charge_loop states test Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
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.
I really like the consistent use of test cases. I would still ask to refactor the code a bit to avoid code duplication and make it more readable.
static constexpr auto SCHEDULED_POWER_DURATION_S = 86400; | ||
|
||
Header header; | ||
ResponseCode response_code; | ||
|
||
ScheduleExchangeResponse() : | ||
processing(Processing::Finished), control_mode(std::in_place_type<Dynamic_SEResControlMode>){}; | ||
processing(Processing::Finished), control_mode(std::in_place_type<Dynamic_SEResControlMode>) {}; |
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.
We should use default values for the member variables right away, not defining custom constructors
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.
I have no preference. So I can change this in a separate PR for all message definitions.
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
…amicModeParameters struct instead of the 3 individual variables Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Signed-off-by: Sebastian Lukas <[email protected]>
Describe your changes
This PR adds basic support for dynamic mode. Tested on the Testival in France and there was no problems.
Issue ticket number and link
Support for dynamic mode was missing
Checklist before requesting a review