bluerobotics / bluerobotics/cockpit

joystick: Jabra headset treated as controller, interupting active control

Open
#2,993 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
198
Forks
63
Avg merge
2d 7h
Merged PRs (30d)
57

Description

### Bug description

While trying to control the robot via cockpit, and having both controller: Logitech Cordless RumblePad 2 + Headset: Jabra Evolve2 65 Flex, we were not able to have control.

Disconnecting the headset gives us back actions with the controller.

### Steps to reproduce

1. Have both a Jabra wireless headset and controller active
2. Open cockpit
3. Try to gain control with controller
4. Fail to gain control

### Primary pain point(s)

It is disruptive, and a bit scary when you lose control unexpectedly, and it also prevents us from using our wireless headsets while operating robots (which we do all the time).

### Additional context

Joystick info: name: 'Jabra Evolve2 65 Flex (Vendor: 0b0e Product: 2519)
Joystick info: name: 'Jabra Link 380 (Vendor: 0b0e Product: 24c8)
Joystick info: name: 'Logitech Cordless RumblePad 2 (STANDARD GAMEPAD Vendor: 046d Product: c219)

The Jabra devices do NOT have axes:
`axes: buttons: 0, 0...`
Where as the normal controllers do, of course.

This could be used to discriminate devices, or perhaps simply blacklist the vendor (or maintain a product list)

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named in the issue. Start by locating cockpit's joystick handling and checking how devices with no axes are classified; reproduce with the Jabra headset and Logitech controller. Done means the headset no longer interrupts control and the controller retains control while both devices are connected.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.