Getting started with PX4 for Navio2

Navio / Edge Getting started
1

Hello,
I am currently trying to compile PX4 for the navio2 board on a Raspberry Pi 4 Model B Rev 1.5.

Setup: Ubuntu 24.04.1 LTS, Docker Image px4io/px4-dev-armhf:2022-08-12 (according to Raspberry Pi 2/3/4 Navio2 Autopilot | PX4 Guide (main) and PilotPi with Raspberry Pi OS | PX4 Guide (main))
I could not get it to compile or run on the pi on any other versions of the docker image.

Also I can only use the main branch of PX4, which does not run reliably. (Multiple required parameters are missing: SYS_AUTOCONFIG, COM_FLTMODE1-6)

On the stable version 1.15.2 compiling fails.

Can anyone help me to get the pipeline running?

Thanks

Simon

3

Hi @Simon_Exner, could you share more details about which part you’re trying to run? A screenshot of the error message would also be helpful. Thanks!

4

Hi,
As of now, I actually got the build pipeline running for stable version 1.14
this is sufficant for me.
But I have issues with PX4 when it is running:

  • I get output on the console, which I can not find the cause for:
    ERROR [vehicle_imu] 1 - accel 4457218 timestamp error timestamp_sample: 973058839, previous timestamp_sampl
    ERROR [vehicle_imu] 1 - gyro 4457218 timestamp error timestamp_sample: 973058839, previous timestamp_sample
    ERROR [vehicle_imu] 1 - gyro 4457218 timestamp error timestamp_sample: 973096656, previous timestamp_sample
    ERROR [vehicle_imu] 1 - accel 4457218 timestamp error timestamp_sample: 973096656, previous timestamp_sample
  • I get a warning for “no manual control input”, but in QGCs vehicle configuration the inputs from my sticks (frsky sbus reciver) are displayed correctly and calibration is successful. Changing the flightmode for example does not work via the configured switch, so PX4 does not seem to compute the control inputs correctly apart from making them available for configuration.
  • The missing parameters SYS_AUTOCONFIG, COM_FLTMODE1-6 are still missing, unless I set them manually on the px4-console, then they are available via QGC.
  • Gyro calibration continuously fails at 100% due to “motion”. Calibrating when using ardupilot works fine, so no hardware error presumably. Also the artificial horizon shows reasonable attitude estimations with PX4.
  • Arming is not possible “not ready” (apart from control input, there are no warnings and there are no errors at all)
  • The PWM output rate is fixed at 400 or 500 Hz (I do not recall which of both), and can not be changed, the parameter is not available, neither via QGC nor console.

Those are just the issues I found while playing around, probably, there are more.

Thanks for your help!

5

@Simon_Exner Thanks for the explanation, I am checking this!

6

Hi @Simon_Exner,

I’ve gone through the PX4 documentation, and it advises against using newer Ubuntu versions. This can be the cause of some errors and the missing parameter. It doesn’t seem to be a hardware issue with the Navio2 since it works with Ardupilot. As this is using PX4’s code, I’d suggest reaching out to their support team. They’ll be better able to understand the error.