Skip to content

Conversation

@Pietfried
Copy link
Contributor

  • in case of an active transaction we were responding with Scheduled instead of Accepted to a ChangeAvailability.req(status=Operative) - this has been fixed and is required by G03.FR.03 and G04.FR.04
  • now overrding or removing scheduled availability changes if needed

Signed-off-by: pietfried <pietgoempel@gmail.com>
@Pietfried Pietfried marked this pull request as ready for review October 12, 2023 19:47
Comment on lines 902 to 906
if (this->evses.at(evse.value().id)->has_active_transaction()) {
return true;
} else {
return false;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if (this->evses.at(evse.value().id)->has_active_transaction()) {
return true;
} else {
return false;
}
return this->evses.at(evse.value().id)->has_active_transaction();

return (operational_status == OperationalStatusEnum::Inoperative and
connector_status == ConnectorStatusEnum::Unavailable) or
(operational_status == OperationalStatusEnum::Operative and
(connector_status != ConnectorStatusEnum::Unavailable or connector_status != ConnectorStatusEnum::Faulted));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This last statement is always true since it can't be Unavailable and Faulted at the same time.

Also, maybe easier to read using a switch for one of the enums?

Signed-off-by: pietfried <pietgoempel@gmail.com>
@Pietfried Pietfried requested a review from marcemmers October 13, 2023 17:08
@Pietfried Pietfried merged commit f07b61d into main Oct 16, 2023
@Pietfried Pietfried deleted the pg-v201-change-availability branch October 16, 2023 08:02
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