Fix all possible HTTP to HTTPS docs links (#25153)

This commit is contained in:
Hamish Willee
2025-07-03 18:09:58 +10:00
committed by GitHub
parent 375f421c61
commit 2c31e2bad5
84 changed files with 276 additions and 359 deletions

View File

@@ -20,7 +20,7 @@ Before analyzing a flight log it is important to establish its context:
If a log file ends mid-air, two main causes are possible: a power failure _or_ a hard fault of the operating system.
On autopilots based on the [STM32 series](http://www.st.com/en/microcontrollers/stm32-32-bit-arm-cortex-mcus.html), hard faults are logged to the SD card.
On autopilots based on the [STM32 series](https://www.st.com/en/microcontrollers-microprocessors/stm32-32-bit-arm-cortex-mcus.html), hard faults are logged to the SD card.
These are located on the top level of the SD card and named _fault_date.log_, e.g. **fault_2017_04_03_00_26_05.log**.
You should check for the presence of this file if a flight log ends abruptly.
@@ -28,7 +28,7 @@ You should check for the presence of this file if a flight log ends abruptly.
### Flight Review (Online Tool)
[Flight Review](http://logs.px4.io) is the successor of _Log Muncher_.
[Flight Review](https://logs.px4.io/) is the successor of _Log Muncher_.
It is used in combination with the new [ULog](../dev_log/ulog_file_format.md) logging format.
Key features:

View File

@@ -1,6 +1,6 @@
# Log Analysis using Flight Review
The [Flight Review](http://logs.px4.io) plots for a flight can be used to analyze general vehicle condition.
The [Flight Review](https://logs.px4.io/) plots for a flight can be used to analyze general vehicle condition.
The plots are meant to be self-explanatory, but it takes some experience to know what ranges are acceptable and what a plot should look like.
This page explains how to interpret the plots and identify common problems.