PX4 Sync / Q&A: Oct 16, 2024

Coordination Calls PX4 Autopilot
1

PX4 Sync / Q&A: Oct 16, 2024

Agenda

  • Announcements
  • Release Discussion
  • Q&A

Announcements

Release Discussion

Bug report / Q&A

1 -PX4 Sync / Q&A: Oct 16, 2024 - #2 by frogzhang

@frogzhang this seems to be a bug. If possible not to use LPE, maybe better for now?

2 - PX4 Sync / Q&A: Oct 16, 2024 - #4 by dirksavage88

3 - @bresch anyone using bmm350 mag?

@dagar: https://www.st.com/en/mems-and-sensors/iis2mdc.html

4- @dirksavage88 Headings are off in RTK setup with huge nearly 90 degs offset.

@AlexKlimaj @dagar the setup might be not correct. If it is 90 degs clear off then it is the setup.

PRs needing review:

2

If I use the command make px4_fmu-v5_default to build for Pixhawk 4 hardware everything works. But if I use the command PX4_ASAN=1 make px4_fmu-v5_default to build for Pixhawk 4 hardware . I get the following problem:

… /… /src/modules/local_position_estimator/BlockLocalPositionEstimator.cpp: In member function ‘void BlockLocalPositionEstimator::predict(const sensor_combined_s&)’:
… /… /src/modules/local_position_estimator/BlockLocalPositionEstimator.cpp:984:1: error: the frame size of 4640 bytes is larger than 3700 bytes [-Werror=frame-larger-than=]
984 |}
| ^
compilation terminated due to -Wfatal-errors.
cc1plus: all warnings being treated as errors
[832/1209] Performing build step for ‘libmicroxrceddsclient_project’
– libmicroxrceddsclient_project build command succeeded. See also / home/zt / 4.24 / PX4 Autopilot - v1.14.0 / build/px4_fmu - v5_default/SRC/modules/uxrce_dds_client/SRC/libmicroxrceddsclient_proj ect-stamp/libmicroxrceddsclient_project-build-*.log
ninja: build stopped: subcommand failed.
make: *** [Makefile:227: px4_fmu-v5_default] Error 1

How can I fix this? Thank you all

4

Dual RTK GPS is handled differently in PX4 Cannode vs AP Periph (ardupilot’s dronecan firmware).

The fix involves pulling in the dronecan relposheading message. Changes to include this can either be in uavcan driver or in EKF2. What preferable to get these fixes in?

Alternatively we can pull in the uORB gnss relative sub here and make the change in ekf2: PX4-Autopilot/src/modules/ekf2/EKF2.cpp at a0e6f9cd70397dd741efdb5d72d94b9ac88e97ce · PX4/PX4-Autopilot · GitHub

1 Like