4.1     System topologies

 

Each FlightZoomer system topology offers a different solution how the Cockpit-app communicates with the flight controller.

The most basic system topology makes use of a 3rd party radio telemetry solution.

Besides that, the user has the option to choose a more comprehensive system topology, which includes an onboard smartphone. This offers several benefits like unlimited range or enhanced autonomous capabilities (e.g. in case of impaired or broken ground-to-air communication).

A third category of system topologies covers several auxiliary operation modes.

 

System topologies overview:

System topology

Description

Onboard Smartphone

Time-based charges

3rd party radio

The cockpit app connects to any kind of 3rd party telemetry solution via USB COM port.

 

 

Onboard smartphone connected via Direct Link

Easy to setup and best performing communication bus via commercial real time messaging hub.

x

x

Onboard smartphone connected relay server

The user operates a stationary relay server to which all mobile devices connect. Still supported legacy topology.

x

 

Standalone simulation

Standalone operation, which is offered by the Cockpit-app to simulate fully featured autopilot operations

 

 

Auxiliary operation modes

There are several auxiliary operation modes, which allow the FlightZoomer Relay Server-desktop application to feed flight data into the Cockpit-app:

1.       Flights can be replayed

2.       Simulation of 3D flight vectors

3.       Joystick input to simulate 3D flight vector

 

 

 

 

4.1.1   Operation with 3rd party radio

4.1.2   Onboard smartphone connected via Direct Link

4.1.3   Onboard smartphone connected via relay server

4.1.4   Standalone simulation

4.1.5   Auxiliary operation modes

4.1.5.1   Replay flights

4.1.5.2   Simulation of 3D flight vectors

4.1.5.3   Joystick input to simulate 3D flight vector

4.1.6   MAVLink requirements