A facility that provides control of automatic connection for drone and remote control devices.
The goal of auto-connection is to ensure that exactly one remote control and exactly one drone are connected whenever it is possible to do so, based on rules as described below.
GroundSdk may be configured so that auto-connection is started automatically at GroundSdk startup. This behaviour is enabled by setting
AutoConnectionAtStartupconfiguration flag to
YESin the dictionary entry
GroundSdkdeclared in the
info.plist. It can be disabled (this is the default) by either removing the
AutoConnectionAtStartupentry or setting it to
NO. Auto-connection may also be started and stopped manually though this Facility API.
Remote control auto-connection:
When started, auto-connection will try to always maintain one, and only one remote control connected. It will pick one remote control amongst all currently visible devices and ensure it is connecting or connected, and will connect it otherwise. All other connected remote control devices are forcefully disconnected.
To chose which device will get connected, visible remote control devices are sorted by connector technology: Usb is considered better than Wifi, which is considered better than Bluetooth Low-Energy. The best available remote control is picked up according to this criteria and will be auto-connected.
Also, if the best available remote control is currently connected (or connecting) and an even better connector becomes available for it, then it will be auto-reconnected (that is, disconnected, then connected again) using this better connector.
When started, auto-connection will try to always maintain at least one, and only one drone connected.
Two different cases must be distinguished:
When no remote control is currently connected, then drone auto-connection behaves like remote control auto-connection: drones are sorted by connector technology and the drone with best technology is elected for auto-connection. Auto-reconnection using an even better connector may also happen, as for control devices.
When a remote control is connected (or connecting), then auto-connection will ensure that no drones are connected through any other connector (including local ones: WIFI or BLE) than this remote control. Any drone that is currently connected or connecting though one of these connectors will get forcefully disconnected. If, by the time the remote control gets auto-connected, some drone is already connected through a local connector, then auto-connection will try to connect it through the remote control if the latter also knows and sees that drone; otherwise auto-connection lets the remote control decide which drone to connect.
@objc(GSAutoConnection) public protocol AutoConnection : Facility
Facility that provides global management of firmware updates.
FirmwareManager allows to:
- Query up-to-date firmware information from remote update server; note that the application is only allowed to query update once every hour.
- list firmware updates for all supported device models, both remotely available (that need to be downloaded from remote update server) and locally available, that are present on the device’s internal storage and are ready to be used for device update.
- Download remote firmware update file from remote update server and archive them on device’s internal storage for later use.
- Delete locally downloaded firmware update files.
This facility can be obtained using:
@objc(GSFirmwareManager) public protocol FirmwareManager : Facility
Facility that allows the application to register some user account identifier.
When such an identifier has been registered by the application, then flight blackboxes and full crash reports (which may contain user-related information) may be uploaded to the configured remote server. Upload HTTP requests for those data will contain this identifier.
When no identifier is registered, then:
- Flight blackboxes are neither recorded nor uploaded to the configured remote server.
- Only ‘light’ crash reports, which do not contain any user-related information, may be uploaded to the configured remote server. Furthermore, in the absence of an authenticated user, this utility allows to define the authorization to use anonymous data or not
@objc(GSUserAccount) public protocol UserAccount : Facility