https://github.com/rubberduck203/switch-hal

Rust no_std embedded-hal driver and traits for Input/Output switches (leds, transistors, buttons, switches)
https://github.com/rubberduck203/switch-hal

Last synced: about 1 month ago
JSON representation

Rust no_std embedded-hal driver and traits for Input/Output switches (leds, transistors, buttons, switches)

• Host: GitHub
• URL: https://github.com/rubberduck203/switch-hal
• Owner: rubberduck203
• License: apache-2.0
• Created: 2020-02-03T12:58:09.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-04-17T14:27:15.000Z (2 months ago)
• Last Synced: 2024-05-09T11:42:46.181Z (about 2 months ago)
• Language: Rust
• Size: 43 KB
• Stars: 24
• Watchers: 2
• Forks: 4
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Lists

• awesome-embedded-rust - `switch-hal` -  (Component abstraction crates / Other)
• awesome-embedded-rust - `switch-hal` -  (Component abstraction crates / Other)

README

        
# switch-hal

![Rust](https://github.com/rubberduck203/switch-hal/workflows/Rust/badge.svg)

[![crates.io](https://img.shields.io/crates/d/switch-hal.svg)](https://crates.io/crates/switch-hal)

[![crates.io](https://img.shields.io/crates/v/switch-hal.svg)](https://crates.io/crates/switch-hal)

[![docs.rs](https://docs.rs/switch-hal/badge.svg)](https://docs.rs/switch-hal)

Switch-HAL is a `no_std` embedded Rust library for working with buttons, switches, LEDs, and transistors.

Basically, anything that acts like a switch, whether an input or output.

It is both a driver that uses the `embedded-hal::digital` traits and is an abstraction in it's own right.

It provides a simple, zero-cost, abstraction to clarify the _intent_ of your application code.

## Why Switch-HAL? Why not just use raw GPIO?

Did you mean to drive that line high?  

Or did you mean to _turn that LED off_?  

Wait a second... is that LED active _high_?  

Where's the schematic?  

Okay... cathode is wired to the input line... that means it's active low.

Now repeat this every place in your code where you need to turn that LED on or off.  

What happens when the hardware changes?  

Using the raw GPIO to set pins high and low will have you making changes all over your code base.

Wouldn't it be nicer if you only had to think about that once, when you initialize your application,  

and from then on out, simply called `led.on()` or `led.off()`.  

Having an abstraction at the proper level reduces cognitive load.  

Specifying whether a simple peripheral is active high or low in a single place in your application reduces the maintenance burden.

## Documentation

https://docs.rs/crate/switch-hal

or build a local copy

```sh

cargo docs

```

and open `target/doc/switch_hal/index.html` in your browser.

## License

Licensed under either of

- Apache License, Version 2.0 ([LICENSE-APACHE](./LICENSE-APACHE) or

  http://www.apache.org/licenses/LICENSE-2.0)

- MIT license ([LICENSE-MIT](./LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

## Architectural Decision Records

Major design decisions are tracked in the [adr](./adr) directory.

## Changelog

### 0.4.0

Adds `StatefulOutputSwitch` thanks to [forkbomb9](https://github.com/forkbomb9)

### 0.3.3

Update embedded-hal to 0.2.5

### 0.3.2

- Add convenience converter functions `into_active_low_switch()` and `into_active_high_switch()`

### 0.3.1

- Bug Fix: `is_active()` was returning the wrong result for `Switch`