Description
Describe the bug
I assumed all newer configurator versions should be able to connect to older betaflight firmware drones.
I have a working drone connected to usb at com7 (windows auto-detects the com-port),
and its autodetected on betaflight configurator, but the connect fails.
com7 is using the cp210 universal windows drivers.
do I have to use some specific older version of the configurator to work with 4.0.6 firmware drones?
I'm not sure its exactly 4.0.6 firmware but its the latest firmware that is supported on spracingf3, because of the firmware changes.
I'm currently on win11 not using the browser version but the pre-compiled windows installable version.
I think I previously connected using the browser version, and that worked. now desktop version does not work.
nothing on the drone has changed on the firmware from last successful connect some time/months ago.
(I did add a radio receiver on the sbus/ppm port, between the last success and now, if it matters.)
To Reproduce
- connect working drone to usb
- press connect button
Expected behavior
previous connection on some old configurator version worked directly and gyros/accelerometers worked fine.
Configurator version
10.10.0 (c97deaf) win_x64
Flight controller configuration
Add any other context about the problem that you think might be relevant here
2025-06-07 @15:54:11 -- OS: Windows
2025-06-07 @15:54:11 -- Configurator: 10.10.0 (c97deaf)
2025-06-07 @15:54:18 -- Serial port successfully opened with ID: 1
2025-06-07 @15:54:28 -- No configuration received within 10 seconds, communication failed
2025-06-07 @15:54:28 -- Serial port successfully closed