[Bug] Preflight check: FAILED without further information

[christianrauch]

Describe the bug

commander check returns Preflight check: FAILED without further information why the check fails.

QGroundControl reports an "X/Y position control Error" and all other sensors as "Normal".

To Reproduce

commander check

Expected behavior

No issues or information about the reason for the failure.

Screenshot / Media

No response

Flight Log

No response

Software Version

HW arch: PX4_RASPBERRYPI
PX4 git-hash: 1ea672e87d1d6c5d03ecee6ff2fbe616e6059288
PX4 version: 1.16.0 80 (17825920)
PX4 git-branch: main
OS: Linux
OS version: Release 6.8.0 (101187839)
Build datetime: Apr 21 2025 12:50:09
Build uri: localhost
Build variant: default
Toolchain: GNU GCC, 13.3.0
PX4GUID: 100449495052303030443030303030303030
UNKNOWN MCU

Flight controller

Raspberry Pi 5

Vehicle type

Multicopter

How are the different components wired up (including port information)

pca9685, mpu9250, ak8963 via I2C

Additional context

No response

[sfuhrer]

Could you share a log file by chance? You can create one without flying through the MAVLink shell:

logger on 
logger off

then download the log and share it here.

[christianrauch]

I am unable to log to file:

ERROR [logger] failed creating log root dir: /fs/microsd/log (2)

and it does not seem possible to change the file path.

With

logger start -m mavlink

I don't see log messages in the MAVLink Inspector in QGroundControl.

Edit: Even after creating directory /fs/microsd/log and running px4 via sudo, I don't see log files created under this path.

[christianrauch]

I could only find the X/Y position control string in QGroundControl:
https://github.com/mavlink/qgroundcontrol/blob/ace8f62c730d9c1553b8b4e2d33cd24982a7eed9/src/MAVLink/QGCMAVLink.cc#L285

The MAV_SYS_STATUS_SENSOR_XY_POSITION_CONTROL relates to health_component_t::local_position_estimate in PX4 and I could finally track this down to:

PX4-Autopilot/src/modules/commander/HealthAndArmingChecks/checks/modeCheck.cpp

Lines 83 to 85 in 38d67f5

	reporter.armingCheckFailure(local_position_modes, health_component_t::local_position_estimate,
	events::ID("check_modes_local_pos"),
	events::Log::Error, "Navigation error: No valid position estimate");

It is suboptimal that you have to crawl through two code bases to get a hint on what the FC is doing. Still, there is no information presented that explains where this issue originates from.

[sfuhrer]

So you have no way of creating a log file? Here is some further information about the topic FlightReporting