bluerobotics / bluerobotics/cockpit

Joystick: allow the user to specify the "stopped" value for each axis

Open
#716 2 comments 0 reactions 0 assignees View on GitHub
enhancement joystick safety ux
Dominant language
TypeScript
Stars
198
Forks
63
Avg merge
2d 7h
Merged PRs (30d)
57

Description

We already support specifying min/max - it could also be useful to specify the stopped/neutral value for smarter messages when pilot input is not being received but the user has elected to continue sending messages (i.e. a slightly more advanced version of #713).

We could try to infer some of this from firmware versions, but allowing specifying the values manually is valuable for custom vehicles and joystick protocols, especially for future support.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the joystick handling and the existing min/max axis configuration, then review issue #713 for the related behavior. Done means users can specify a stopped or neutral value for each axis and receive smarter messages when pilot input is absent but message sending continues, including for custom vehicles and joystick protocols.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.