Pre-flight checks
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start at the code that exits safety mode and trace how it reads the ET16S slider and switches. Add checks for the left slider deadband, Switch B, and Switch H, keeping safety mode active and identifying failed checks when any condition is unsafe. Confirm the checks against the existing controller input and safety mode handling.
Written by the indexing model from the issue text.
Description
Before the robot exits safety mode, check that the ET16S is in a safe state:
- Spin off: the left slider (
L_SLIDER/get_l_slider()) is at 0, within a small deadband. - Flywheel off: Switch B is
BACKWARD. - Feeder off: Switch H is
FORWARD.
If any check fails, stay in safety mode and print which check failed.
- Dominant language
- C
- Stars
- 11
- Forks
- 2
- Avg merge
- 18d 3h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from CU-Robotics/firmware
-
good first issue not started
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
CU-Robotics/firmware#257 ·
-
Fix existing clang-tidy findingsPossibly taken @roccoagain claimed this today. Open
CU-Robotics/firmware#262 · 1 assignee ·
-
not started
Difficulty 5/5 Over a week Newbie friendliness 35/100
CU-Robotics/firmware#258 ·
-
good first issue not started
Difficulty 3/5 1-2 days Newbie friendliness 76/100
CU-Robotics/firmware#256 ·
-
in progress software-in-the-loop
Difficulty 4/5 3-5 days Newbie friendliness 42/100
CU-Robotics/firmware#250 · 1 comment ·
All issues in CU-Robotics/firmware
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schrodinger/pymol-open-source#532 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
CTSRD-CHERI/cheribsd#2769 ·
Maintainers usually reply within 2 days
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
luainkernel/lunatik#2633 ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day