RigiTech Software Update - October 28, 2024

RigiCloud and Edge Node - v1.13.0:

Control Tower

Removal of Pre-arm Button
- Pushing the pre-arm button is no longer required during pre-flight checklists, reducing the time needed between switch-on and flight and reducing the load on the ground operator.
- When the parachute is locked, the drone will still refuse to arm.
Correction of Wind Direction format
- The telemetry now displays the wind angle as the direction from which the wind is coming, aligned with the convention used in manned aviation, rather than the direction it is going.

Planner

Dropping Mechanism Integration:
- Support has been added for planning operations that include a dropping behaviour at the delivery point, using the dropping mechanism add-on for Eiger drones.
- Note: this feature is only available for drones with a dropping mechanism enabled.

Drop

Fleet Management

Edge Node Management and Software Update Interface
- A new interface is available for all Edge Nodes that consolidates metadata including position (when available) and synchronisation status for every Edge Node.
- Software updates can be performed directly from this interface, and a history of previous updates (including date and user that initiated it) is tracked and displayed, starting at the release date of this feature.
- Software updates can also be performed directly from the Edge Node Dashboard, with progress and update status synchronised with RigiCloud.
  - Note: Edge Nodes updates to version v1.13.0 or posterior need to be done by RigiTech.

Edge Node Update

Simulated drones now have their parameters updated at connection, and no longer require manual parameter synchronisation.
Remaining distance is now displayed more accurately in the Control Tower during flight, especially during contingency maneuvers such as SRP which alter the destination of the operation.
A soft reboot of the drone's onboard systems can now be performed by the remote operator, simplifying remote debugging before flight.
Bug fixes, reliability improvements, software refactors.

Contingency actions such as SRP or Hold are handled more consistently during edge cases of multiple consecutive actions.
Bug fixes, reliability improvements, software refactors.