RigiCloud and Edge Node - v1.6.0:

Added

Airbridge Planner:

Improved elevation data: A higher quality datasource (Copernicus DEM GLO-30) is now used for elevation data during planning.

Control Tower:

ADS-b integration: aircraft detected by ADS-b transponders integrated in Eiger drones or Edge Nodes are now streamed to RigiCloud and displayed in the Air Traffic map layer. Aircraft data is merged with traffic from Involi (when available), and infrastructure is set for future U-Space air traffic services.
FTS testing: The Failsafe can now be tested on the ground through a simple command, as often as required by airspace authorities (ideally once a day before flights begin), in preparation for future EASA Design Verification. The number of tests is tracked in RigiCloud for maintenance purposes.

Logistics Center:

Automatic flight log syncing: the drone will now synchronise flight logs with RigiCloud right after landing, or on bootup if synchronisation is not complete before the drone shut down. Logs become available in the Logistics Center shortly after.
Additional statistics are calculated on every Operations log for better post-flight diagnostics

General:

Server branding: RigiCloud, Test and Edge Node servers are now branded with different top-bar colours to more clearly distinguish which server the operator is connected to.
New or updated User Roles created for Observers and Simulator-only profiles
Bugfixes, reliability improvements, software refactors

Vision-based precision landing: drones equipped with a downward-facing camera will be able to land with higher precision on a Rigi-designed landing pad. This enables the use of smaller takeoff and landing areas. The detection of the landing target is displayed in the Control Tower.
Takeoff warning: the drone will now output a warning sound for several seconds (configurable) before arming for preflight checks and mission start using the Failsafe buzzer as an additional ground safety feature.
Tight-space U-turn: rather than performing a circular U-turn in Fixed-wing mode, the drone can be configured to perform a "Transition-to-Multicopter, U-turn, Transition to Fixed-wing" manoeuver when we trigger an RTO command. This may prevent the breach of a tight geocage, at the expense of higher total power consumption.
Geocage breach prediction: When a Hold or RTO command is received in FW mode, the drone will issue a warning if it predicts a (pre-)geocage breach. By default no automatic action will be taken, but the drone can be configured to automatically choose the "Transition-to-Multicopter, U-turn, Transition to Fixed-wing" manoeuver when a geocage breach is predicted upon RTO initialisation.

Better parameter handling: fixes bugs related to parameters blocking preflight checks or mission upload.
Disabled DLL failsafe action on ground to avoid triggering when the drone does not have a stable connection before takeoff.
Bandwidth optimization in the messages sent to cloud.

Update to PX4 v1.13: The autopilot firmware has been updated to RigiTech's fork of the latest stable version (v1.13) which includes numerous improvements in performance, most notably:
- State estimation robustifications
- New and improved checks on the airspeed sensor
- Better altitude tracking during FW climbs and descents
- Warning if an imbalanced propeller is detected
Improved transitions: New controllers deployed during both front transitions (FT) and back transitions (BT) to better track altitude during this critical phase of flight.
Failure detection: onboard algorithm can now detect a failure in the pusher motor and signal a warning. The drone will execute a Quadchute if it was flying in FW mode.
Remote Control (RC) update: The ability to transition between Fixed-wing and Multicopter flight has been removed. If the RC is used to take manual control of the drone during fixed-wing flight, it will automatically trigger a transition into Multicopter flight. This is part of the roadmap of removing completely the RC from operations.

RigiCloud-FS-OC Bridge: Previously, the Failsafe computer sent its own independent telemetry (GNSS position, altitude, etc) to RigiCloud through a secondary LTE datalink. Now, the Failsafe can bridge data (both telemetry and commands) between RigiCloud and the main Onboard Computer. The result is that even on main datalink loss the operator retains information on the status of the drone and can issue commands to the Onboard Computer and the Autopilot through the secondary LTE datalink, enabling full datalink redundancy.
More detailed information is logged, especially during launches.