Should we have sensor readings traits in embedded-hal or another "sensor" crate?

Open
#32 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
embedded-iot

Research direction

Start by reviewing the embedded-hal scope and the proposed sensor categories in this issue. Compare whether common reading traits and unit conversion belong in embedded-hal or a separate sensor crate. Done means reaching and documenting a clear project-level decision.

Written by the indexing model from the issue text.

Description

discussion

Since concrete driver implementations are on the way it would be great if there was a common set of Traits that could be implemented to retrieve values from sensors, potentially including unit conversion.

Some Traits that immediately come to my mind would be:

  • Temperature
  • Electricity
  • Location
  • Kinetics
  • Orientation
  • Vision
  • Concentrations
  • ...

My question would be: Is this something we would want to add to embedded-hal or should this better live in a to-be-created new crate?

Dominant language
Rust
Stars
2.7k
Forks
282
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-embedded/embedded-hal

All issues in rust-embedded/embedded-hal

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.