chonky #670
No reviewers
Labels
No Label
OPS TODO
api change
breaking api change
bug
documentation
duplicate
feature
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: eive/eive-obsw#670
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "v3.0.0-dev"
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?
TMTC PR: eive/eive-tmtc#197
@ -492,2 +572,4 @@
return;
}
uint16_t decRateReadBack = (rawReply[10] << 8) | rawReply[11];
sif::debug << "AcsPollingTask: DEC rate configuration. Read " << decRateReadBack
who did this?
@ -194,0 +237,4 @@
return;
} else if (powerState == PowerState::SHUTDOWN) {
// Wait till power state is OFF.
return;
How do we ever get to PowerState::OFF, if we return here? Is that not needed for this configuration?
This is done by the supervisor, so when the action reply arrive, the power state will go to OFF. Some sort of timeout is missing though..
@ -29,3 +29,3 @@
* packet otherwise the MPSoC will reply with an acknowledgment failure report.
*
* @author J. Meier
* NOTE: This is not an example for a good device handler, DO NOT USE THIS AS A REFERENCE HANDLER.
lol
@ -597,3 +597,2 @@
}
auxHk.vcc.value = as<int16_t>(packet + 0x24);
auxHk.vbat.value = as<int16_t>(packet + 0x26);
coreHk.vcc.value = as<int16_t>(packet + 0x24);
is the MIB prepared for this?
v2.0.0-dev is being prepared for this