Pre-flight checks

Open Beginner friendly
#222 0 comments 0 reactions 0 assignees View on GitHub

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

in progress

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

  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 CU-Robotics/firmware

All issues in CU-Robotics/firmware

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.