Browse Source

Update PX4 Firmware metadata Mon Sep 27 15:59:52 UTC 2021

QGC4.4
PX4BuildBot 3 years ago
parent
commit
a9fcebc274
  1. 21
      src/FirmwarePlugin/PX4/PX4ParameterFactMetaData.xml

21
src/FirmwarePlugin/PX4/PX4ParameterFactMetaData.xml

@ -9230,6 +9230,15 @@
</parameter> </parameter>
</group> </group>
<group name="SD Logging"> <group name="SD Logging">
<parameter name="SDLOG_ALGORITHM" default="2" type="INT32">
<short_desc>Logfile Encryption algorithm</short_desc>
<long_desc>Selects the algorithm used for logfile encryption</long_desc>
<values>
<value code="0">Disabled</value>
<value code="2">XChaCha20</value>
<value code="3">AES</value>
</values>
</parameter>
<parameter name="SDLOG_BOOT_BAT" default="0" type="INT32" boolean="true"> <parameter name="SDLOG_BOOT_BAT" default="0" type="INT32" boolean="true">
<short_desc>Battery-only Logging</short_desc> <short_desc>Battery-only Logging</short_desc>
<long_desc>When enabled, logging will not start from boot if battery power is not detected (e.g. powered via USB on a test bench). This prevents extraneous flight logs from being created during bench testing. Note that this only applies to log-from-boot modes. This has no effect on arm-based modes.</long_desc> <long_desc>When enabled, logging will not start from boot if battery power is not detected (e.g. powered via USB on a test bench). This prevents extraneous flight logs from being created during bench testing. Note that this only applies to log-from-boot modes. This has no effect on arm-based modes.</long_desc>
@ -9241,6 +9250,18 @@
<max>1000</max> <max>1000</max>
<reboot_required>true</reboot_required> <reboot_required>true</reboot_required>
</parameter> </parameter>
<parameter name="SDLOG_EXCH_KEY" default="1" type="INT32">
<short_desc>Logfile Encryption key exchange key</short_desc>
<long_desc>If the logfile is encrypted using a symmetric key algorithm, the used encryption key is generated at logging start and stored on the sdcard RSA2048 encrypted using this key.</long_desc>
<min>0</min>
<max>255</max>
</parameter>
<parameter name="SDLOG_KEY" default="2" type="INT32">
<short_desc>Logfile Encryption key index</short_desc>
<long_desc>Selects the key in keystore, used for encrypting the log. When using a symmetric encryption algorithm, the key is generated at logging start and kept stored in this index. For symmetric algorithms, the key is volatile and valid only for the duration of logging. The key is stored in encrypted format on the sdcard alongside the logfile, using an RSA2048 key defined by the SDLOG_EXCHANGE_KEY</long_desc>
<min>0</min>
<max>255</max>
</parameter>
<parameter name="SDLOG_MISSION" default="0" type="INT32"> <parameter name="SDLOG_MISSION" default="0" type="INT32">
<short_desc>Mission Log</short_desc> <short_desc>Mission Log</short_desc>
<long_desc>If enabled, a small additional "mission" log file will be written to the SD card. The log contains just those messages that are useful for tasks like generating flight statistics and geotagging. The different modes can be used to further reduce the logged data (and thus the log file size). For example, choose geotagging mode to only log data required for geotagging. Note that the normal/full log is still created, and contains all the data in the mission log (and more).</long_desc> <long_desc>If enabled, a small additional "mission" log file will be written to the SD card. The log contains just those messages that are useful for tasks like generating flight statistics and geotagging. The different modes can be used to further reduce the logged data (and thus the log file size). For example, choose geotagging mode to only log data required for geotagging. Note that the normal/full log is still created, and contains all the data in the mission log (and more).</long_desc>

Loading…
Cancel
Save