Robin Mueller
fe970ad881
Add satrs::fdir::FaultCounter, an FSFW-style error threshold counter: counts faults, decrements over time when faults stop, and reports when a threshold is exceeded. Two variants for now, mirroring the hk.rs helper pattern: - FaultCounterStd, backed by std::time::Instant - FaultCounterEmbassy, backed by embassy_time::Instant (embassy-time feature), with an optional defmt::Format impl gated on the defmt feature Add satrs::health::HealthTableMapSync::default() for easy construction of a shared, global health table. Wire both into the example app's MGM device handler as the first real FDIR use case: - the minisim MGM model gains SpiFaultMode (None/AllZeros/AllOnes) and a SetSpiFault request, so a stuck SPI bus can be injected for testing, independent of switch state - MgmHandlerLis3Mdl::poll_sensor checks the SPI transfer result: a comm timeout or an all-1s stuck-bus reply (the same pattern the sim already uses for "device off") counts as a fault. Above threshold, the component is marked Faulty in a HealthTableMapSync shared from main.rs. This logic lives in the device handler, not the SPI comm layer, since deciding what a failed transfer means for FDIR is a handler concern. - an all-0s reply is deliberately not treated as a fault, since it collides with a legitimate zero-field reading
23 lines
511 B
TOML
23 lines
511 B
TOML
[package]
|
|
name = "client"
|
|
version = "0.1.0"
|
|
edition = "2024"
|
|
|
|
[dependencies]
|
|
clap = { version = "4", features = ["derive"] }
|
|
log = "0.4"
|
|
fern = "0.7"
|
|
humantime = "2"
|
|
serde = { version = "1" }
|
|
serde_json = "1"
|
|
satrs = { path = "../../satrs" }
|
|
satrs-example = { path = ".." }
|
|
satrs-minisim = { path = "../minisim" }
|
|
types = { path = "../types" }
|
|
spacepackets = { version = "0.18", default-features = false }
|
|
bitbybit = "2"
|
|
arbitrary-int = "2"
|
|
ctrlc = { version = "3.5" }
|
|
postcard = { version = "1" }
|
|
anyhow = "1"
|