OpenStickCommunity / OpenStickCommunity/GP2040-CE

Enabling Turbo Dial cause instability problems

Open
#846 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
2.5k
Forks
666
Avg merge
1d 19h
Merged PRs (30d)
7

Description

Prerequisites

Please check the following before posting an issue / bug report.

  • I am running the latest version of the firmware found HERE
  • I have checked the documentation HERE and found no answer
  • I checked to make sure that this issue has not already been filed HERE
  • I am reporting the issue to the correct repository
Context

Please provide all relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

  • Firmware Version: v0.7.7
  • Name of device: RP2040-Zero
  • Link to where you purchased the device:
  • Is this a custom build?: yes
  • Operating System: Win11
  • Browser: Chrome
Expected Behavior

10K potentiometer connected to analog I/O pin26 to dial the turbo speed

Current Behavior

So i tested the use of a Turbo button, a Turbo LED and a Turbo Dial function back in September 2023 on firmware version V.0.7.1 with a simple bread board.
Everything was fine and working as expected so i made a custom PCB.
Now i just assembled the PCB and flashed the new WaveshareZero firmware v0.7.7.
The Turbo functions are still working as expected but Windows very often fail to properly recognize the device, giving the "unknown device" error.
This problem goes away as soon i disable the Turbo Dial on pin26 in the web-config.
On top of that, if i plug the USB while the potentiometer is set to full turbo speed the configuration made in the web interface are wiped to the default settings.
If i load the old v.0.7.1 firmware on my PCB the problem disappear.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

  1. Just enabling the Turbo Dial on an analog I/O pin make the device pretty unstable, Win11 and Win10 often fail to recognize the device
Screenshots & Files

(https://drive.google.com/file/d/1HMMg-TPW2Efj3OVIwXRW9o_sqa61D9Uq/view)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the issue on an RP2040-Zero with firmware v0.7.7, a 10K potentiometer on analog pin26, and Turbo Dial enabled. Compare behavior with v0.7.1, focusing on Windows device recognition and whether web configuration resets when the potentiometer is at full speed. Done means Turbo Dial no longer causes USB instability or configuration loss.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.