-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/channel management #29
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ticked the wrong box on the first review above.
Needs some changes. Most are minor.
src/rf_channel.rs
Outdated
|
||
/// Disable the channel and power it off. | ||
pub fn disable(&mut self) -> Result<(), Error> { | ||
self.pins.power_down_channel(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does matter and let's not risk it. The PA datasheet, the schematic, and the current code all insist on this sequence (rf off, then pinching off before removing the drain voltage).
disable()
is just the reverse of enable()
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more things.
This PR implements the top-level API needed for adding the RF channel management task to RTIC.
It also adds support for configuring alarms on channels, measuring channel characteristics, and disabling channels. The only unimplemented feature is enabling a channel, which is intentionally omitted for safety reasons until we can verify the functionality of the interlock thresholds in #3.
This addresses most of #5