Missing baudrates in Comm Links

[riosnav]

Have you checked the latest release for fixes?

• Yes, I’ve tested on the latest release

Description

Expected Behavior
I am configuring QGroundControl on a new laptop with the latest version from the website (5.0.2) and want to add a Comm Link with Baud Rate 500 000 as I have in my older device running 4.4.4.

Current Behavior
When adding a new Comm Link, it is not possible to select baudrates higher that 256000 in the dropdown menu.

Steps To Reproduce

1. Application Settings
2. Comm Links
3. Add New Link
4. Baud Rate dropdown menu

Additional Details
Maybe I am missing something. In case this is indeed a new limitation, can I circumvent the menu to input the value editing some config file?

System Information

v5.0.2 64 bit
Windows 11

Log Files and Screenshots

Screenshot new menu
Screenshot old menu

[riosnav]

I have tried manually editing QGroundControl.ini to change the baudrate, but upon restart of QGroundControl it defaults to the lowest baudrate 110, at least graphically.

[HTRamsey]

The baud rate options for windows comes from Qt's qserialport_win.cpp which is apparently obtained from WinBase.h. We used to have them hard coded in the SerialLink file. Would a custom/manual entry work for you?

[riosnav]

The baud rate options for windows comes from Qt's qserialport_win.cpp which is apparently obtained from WinBase.h. We used to have them hard coded in the SerialLink file. Would a custom/manual entry work for you?

I think it would work fine, yes.

[DonLakeFlyer]

We should go back to the old code which added the baud rates ourselves. That was specifically put in there to support cases like this. Is there a problem with doing it like we did before?

[HTRamsey]

We can, but personally I think it's better to obtain the baud rates that the platform libraries actually support, then allow a user to force a custom baud if they want to try that. Even the different Android drivers support different baud rates so it's difficult to hard code an accurate mapping