Starting with GUI:
$ make px4_sitl gazebo-classic_typhoon_h480
...
INFO [px4] Startup script returned successfully
pxh> [Wrn] [Event.cc:61] Warning: Deleting a connection right after creation. Make sure to save the ConnectionPtr from a Connect call
INFO [commander] Ready for takeoff!
Starting without GUI:
$ HEADLESS=1 make px4_sitl gazebo-classic_typhoon_h480
...
INFO [px4] Startup script returned successfully
pxh> INFO [mavlink] partner IP: 127.0.0.1
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: High Gyro Bias
WARN [health_and_arming_checks] Preflight Fail: High Gyro Bias
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: High Gyro Bias
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: height estimate error
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: height estimate error
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: vertical velocity unstable
WARN [health_and_arming_checks] Preflight Fail: height estimate error
And so on. Sometimes it finishes with “INFO [commander] Ready for takeoff!” after several such warnings but sometimes it doesn’t (at least at some reasonable time).
“WARN [health_and_arming_checks]” occurs in GUI mode too - but in GUI mode it never happens that many times in a row. I did several dozen tests in each mode.
What’s wrong with drone in headless mode?