oxidecomputer / oxidecomputer/hubris
Improvements to transceiver temperature handling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
quoth @kc8apf
- reading max case temperature to set limit
- checking
Data_Not_Readyand reporting no temp available if set- interpreting free side temperate of 0C as no temperate and hoping that no one operates a module at precisely that temperature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the transceiver temperature handling in the repository and trace how temperature availability and limits are currently determined. Compare that behavior with the three requirements in the issue; the work is done when maximum case temperature, Data_Not_Ready, and a free-side temperature of 0C are handled as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100