Auterion Enterprise Px4 2.0 Release Notes 1

AOS 2.0.0

Compatibility

This version of AuterionOS comes bundled with APX4 2.0.2:

{% content-ref url="../../../flight-control/apx4-2.0/auterion-enterprise-px4-2.0-release-notes-1.md" %} auterion-enterprise-px4-2.0-release-notes-1.md {% endcontent-ref %}

Please use Auterion Mission Control 1.9.1 or newer with this version of AOS:

{% content-ref url="../../../auterion-mission-control-release-notes/amc-1.9/auterion-mission-control-1.9-release-1.md" %} auterion-mission-control-1.9-release-1.md {% endcontent-ref %}

New Features

• Sony R10C support. AEPX4 automatically detects and sets up the Sony R10C when it is connected to the mission computer USB port. This means you can immediately control the camera via AMC and receive its video stream.
• Sony A7R support. AEPX4 now supports Sony A7R for: taking photos, video recording, video preview, switch between manual & auto exposure modes, setting ISO, shutter, aperture and white balance in manual mode, etc.
• Local updating of Firmware. The vehicle local updater allows you to update the AuterionOS together with all the Distro applications via USB-C or WiFi without needing to re-flash the board. A standard API was created to trigger an update, get update status and get general info about the release. It can also be used during manufacturing as it is part of the AuterionOS and not the customer distro.
• Pairing through secure VPN-based networks.
• Multi-GCS pairing. It is now possible to pair AMC (with 1 Microhard) to multiple secure networks.
• Flight controller can now be flashed as an OEM Developer. With one command, a developer can now update the APX4 firmware over USB-C or WiFi AP in a matter of seconds.
• Reduced delay when switching camera mode. In particular we reduced the delay when switching between video and photo capture.
• Local flight log download using AMC. Flight logs can now be downloaded from the vehicle using AMC rather than having to get them via Auterion Suite.
• Automatic log upload from devices to Auterion Suite.
• Sony cameras can now choose photo destination (USB host vs camera’s SD card). This is necessary for surveys because when the photos are stored on the camera’s SD card, the trigger interval can be much faster (5 seconds vs 2 seconds). It is configured using a parameter.

Fixes

The following issues have been fixed:

• In the Payload Manager, sometimes the camera doesn't have enough time to stop recording and it starts switching mode. The mode switching then hangs and never recovers.
• One receives the QX30 xml definition even when using the Sony R10C, causing many parameter values to not exist.
• With the Sony R10C, the first time one tries to go to photo mode it fails. When this happens the video stream breaks and the camera controls in AMC disappear and then come back after a few seconds. When they come back it’s still in video mode. Sometimes it works if one tries again while some other times one gets this issue multiple times before it succeeds to switch.
• Flashing status in the Suite is broken.
• Pairing Manager sometimes runs into a race condition that invalidates the pairing process.
• Several issues cause the Sony cameras to crash. The biggest issue is caused by a misuse of the auto-exposure.
• The round trip time delay between mission computer and autopilot is now fixed.
• A case of package duplication from processes running MAVSDK might lead to a wrong package drop estimation in AMC. This behavior is now fixed.
• hostname is being wrongly set on the distro.
• One cannot get a video stream from the Sony QX30 over USB-C or WiFi, though the camera controls are available and the video streaming over Microhard radio works.
• One gets a MAVLink packet loss rate of >=97%, as reported by AMC. This is observable over USB-C.
• MAVSDK timesync reports RTT too high for timesync.