Add MSP request for UBLOX SatInfo and disable SatInfo on ARMING.

[haslinghuis]

As configurator some times fails to get satellite info as it missed the opportunity we rather like to add a MSP request from client.

• Send a MSP request from configurator to firmware to enable SatInfo.
• Added support for configurator Add MSP2_UBLOX_REQUEST_SV_INFO betaflight-configurator#3689
• Does not have to wait 3 seconds for GPS data to arrive in OSD.
• Disables sat info on arming.

[github-actions]

Do you want to test this code? You can flash it directly from Betaflight Configurator:

• Simply put #13240 (this pull request number) in the Select commit field of the Configurator firmware flasher tab (you need to Enable expert mode, Show release candidates and Development).

WARNING: It may be unstable. Use only for testing!

[blckmn]

AUTOMERGE: (FAIL)

• github identifies PR as mergeable -> FAIL
• assigned to a milestone -> PASS
• cooling off period lapsed -> PASS
• commit count less or equal to three -> FAIL
• Don't merge label NOT found -> PASS
• at least one RN: label found -> PASS
• Tested label found -> PASS
• assigned to an approver -> PASS
• approver count at least three -> FAIL

[ctzsnooze]

Tested - works GREAT! Much faster than before.

The only thing I haven't confirmed is that the sat info is not being sent when not connected to configurator. That requires parallel monitoring the output of the GPS module in pyGps or uCenter, and powering it up with Configurator not connected.

Two questions:

• could there be some other MSP connection, other than Configurator, which could be active and initiate SatInfo messages when we don't want them - eg an MSP connected GPS itself, or an MSP connected HD goggles? Is this mechanism only initing SatInfo for Configurator alone?
• if a user powers up with Lipo, and connects to Configurator to check sats, that will enable SatInfo. If they disconnect from Configurator, but keep the Lipo connected, will SatInfo continue to be sent, or will it stop when MSP is disconnected?

It is very important that SatInfo is not requested in flight, it results in a very big serial data load.

[Pancronos]

Tested - works GREAT! Much faster than before.

The only thing I haven't confirmed is that the sat info is not being sent when not connected to configurator. That requires parallel monitoring the output of the GPS module in pyGps or uCenter, and powering it up with Configurator not connected.

Two questions:

• could there be some other MSP connection, other than Configurator, which could be active and initiate SatInfo messages when we don't want them - eg an MSP connected GPS itself, or an MSP connected HD goggles? Is this mechanism only initing SatInfo for Configurator alone?
• if a user powers up with Lipo, and connects to Configurator to check sats, that will enable SatInfo. If they disconnect from Configurator, but keep the Lipo connected, will SatInfo continue to be sent, or will it stop when MSP is disconnected?

It is very important that SatInfo is not requested in flight, it results in a very big serial data load.

For your second question i think (for the little i understand code) is also checking the armed flag. So, in anycase, if you take off satinfo is disabled.

[haslinghuis]

@ctzsnooze

Two questions:

could there be some other MSP connection, other than Configurator, which could be active and initiate SatInfo messages when we don't want them - eg an MSP connected GPS itself, or an MSP connected HD goggles? Is this mechanism only initing SatInfo for Configurator alone?

SatInfo will only be requested (enabled) when sending the MSP message on the gps tab in configurator.

if a user powers up with Lipo, and connects to Configurator to check sats, that will enable SatInfo. If they disconnect from Configurator, but keep the Lipo connected, will SatInfo continue to be sent, or will it stop when MSP is disconnected?

It is very important that SatInfo is not requested in flight, it results in a very big serial data load.

ARMING the quad disables SatInfo.