Power Switcher Component #596
No Assignees
Notifications
Due Date
No due date set.
Depends on
#590 refactor power module
fsfw/fsfw
Reference: fsfw/fsfw#596
Reference in New Issue
Block a user
Delete Branch "eive/fsfw:mueller/power-switcher-component-upstream"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Extends #590 , adding a
PowerSwitchComponentAllows to create an power switch object with its own mode and health
This basic component allows to create an object which is solely responsible for managing a switch. It also has a mode and a health by implementing the respective interface components which allows integrating this component into a system mode tree.
See comments.
@@ -0,0 +23,4 @@}ReturnValue_t DummyPowerSwitcher::sendFuseOnCommand(uint8_t fuseNr) {if (fuseNr < fuseList.capacity()) {Why do you use capacity() and not size()?
@@ -0,0 +30,4 @@}ReturnValue_t DummyPowerSwitcher::getSwitchState(power::Switch_t switchNr) const {if (switchNr < switcherList.capacity()) {Why do you use capacity() and not size()?
@@ -0,0 +37,4 @@}ReturnValue_t DummyPowerSwitcher::getFuseState(uint8_t fuseNr) const {if (fuseNr < fuseList.capacity()) {Why do you use capacity() and not size()?
@@ -17,2 +17,3 @@limits.voltageMin, limits.voltageMax, events.voltageLow, events.voltageHigh) {commandQueue = QueueFactory::instance()->createMessageQueue();commandQueue =QueueFactory::instance()->createMessageQueue(3, MessageQueueMessage::MAX_MESSAGE_SIZE);Is the 3 here a specific requiremenet and the MessageQueueSize?
LGTM