DHB - PowerSwitcherIF - first changes #88
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#88
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
I am changing DHB again to test distributed pools too and the issue from #20 came up again when I disabled most device handlers for testing: I need to implement a PowerSwitcherIF (so ,an empty PCDU handler basically), or the DH initialization will fail.
I might implement some suggestions of #20 .
Better error value for missing powerConfirmationId objectto Better error value for missing PowerSwitcherIFThis is related to #20 .
I might implement parts of the suggestions to make the switch optional as I am changing parts of the DHB for the new distributed datapools anyway (I disabled all but one device handler for easy of testing and the initialization failed, of course)
Point 1 and Point 2 would be a good beginning.
In fact, for every single device handler implemented so far I implemented the getSwitches function() just to return NO_SWITCHES and write a comment above to replace this as soon the PCDU is implemented..
Better error value for missing PowerSwitcherIFto DHB - PowerSwitcherIF - first changesI check powerSwitcher for nullptr now at various places in the state machine and related functions which use the powerSwitcher pointer (hopefully didnt forget anyhting..) and tested a dummy device handler with an uninitialized powerSwitcher. (basic DH command, Action command and of course mode command tests) maybe there is a better solution but it propaply involves packaging the powerSwitcher functionality into a helper or the state machine into a separate class.
Actually, initialization still fails because of the missing ConfirmsFailuresIF..