Implementation of scheduler in pus and tmtc handler #29
No reviewers
Labels
No Label
api
b-api
bug
concepts
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: rust/sat-rs#29
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "pus_schedule_implementation"
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?
Implementation of scheduler in pus and tmtc handlerto WIP: Implementation of scheduler in pus and tmtc handler@ -12,0 +19,4 @@
pub enum ScheduleError {
PusError(PusError),
TimeMarginTooShort(UnixTimestamp, UnixTimestamp),
NestedScheduledTC,
TC -> Tc for consistency
Passt
@ -50,6 +134,7 @@ impl PusScheduler {
}
/// Like [Self::new], but sets the `init_current_time` parameter to the current system time.
I think this newline is problematic
@ -121,0 +221,4 @@
) -> Result<StoreAddr, ScheduleError> {
let check_tc = PusTc::from_bytes(tc)?;
if PusPacket::service(&check_tc.0) == 11 && PusPacket::subservice(&check_tc.0) == 4 {
// TODO: should not be able to schedule a scheduled tc
TODO can be removed probably
@ -1,3 +1,5 @@
extern crate core;
What does this do?
Not entirely sure, I think it was an IDE auto import, commented it out and everything seems to work fine so I think it can be deleted
Still TODO: pyclient scheduler implementation
WIP: Implementation of scheduler in pus and tmtc handlerto Implementation of scheduler in pus and tmtc handlerlog folder in satrs-core should be removed
@ -8,1 +10,4 @@
use spacepackets::time::cds::DaysLen24Bits;
use spacepackets::time::{CcsdsTimeProvider, TimeReader, TimestampError, UnixTimestamp};
use std::collections::BTreeMap;
use std::dbg;
should be removed (or put behind std feature and `#[allow(unused_imports)]
@ -276,0 +381,4 @@
.completion_success(start_token, Some(&self.time_stamp))
.expect("Error sending completion success");
//let addr = self.tc_source.tc_store.add_pus_tc().unwrap();
maybe this can be deleted as well?
@ -178,0 +202,4 @@
&mut udp_tmtc_server,
&mut tc_args,
&mut tc_buf,
//&mut tc_source,
old code can be deleted
@ -183,2 +215,4 @@
udp_tmtc_server: &mut UdpTmtcServer,
tc_args: &mut TcArgs,
tc_buf: &mut [u8],
//tc_source: &mut PusTcSource,
unused code can be deleted
@ -187,0 +244,4 @@
}
Err(_) => {}
}
//.expect("error releasing tc");
can be deleted