PX4 Sync / Q&A: Oct 23, 2024

farhang · October 22, 2024, 5:25pm

Agenda

Announcements
Release Discussion
Q&A

Announcements

1- ROSCon24 Aerial Robotics group meetup hosted by Kimberly McGurie PX4 Autopilot on LinkedIn: #roscon #roscon2024 #odense

2 - Dronecode Istanbul meetup thanks to @Ayshine PX4 Autopilot on LinkedIn: 🙌 We had a fantastic time connecting with fellow developers and…

Release Discussion

We have a release tag:

Bug report / Q&A

1- @conor_strat : Not having any connectivity using St-link and CubeOrange Plus.

@dagar The initial solution for now is to check gdb-server and the versions mismatching. If not working, then we can work around other solutions.

2- @TOTON95 What is the status of CSRF/ELRS adaption to the PX4 supported boards?

github.com/PX4/PX4-Autopilot

Make CRSF telemetry protocol by default on new builds

opened 04:11PM - 18 Oct 24 UTC

zarte13

feature-request

### Describe problem solved by the proposed feature I want to use ELRS with m…y drone, but every time there is a PX4 update, I have to make a custom build to include CRSF. I feel like, it would be better to include CRSF for ELRS by default, as it is becoming an increasingly popular option for RC control and basic telemetry. ### Describe your preferred solution Include CRSF telemetry by default on new builds. ### Describe possible alternatives Add an option inside the configuration that wouldn't require creating a new build for switching between the old RC input driver and the new CRSF drive. ### Additional context https://docs.px4.io/main/en/telemetry/crsf_telemetry.html#px4-configuration

@dagar @MaEtUgR There are to options to use the CRSF protocol:

Either over UART with the dedicated CSRF RC driver for which you connect TX and RX to a UART e.g. Telem1 port and then have all features like telemetry, the bind command that’s about to be added.
Connect the receiver’s TX port to the RC in board which then uses either the IO or FMU’s monolytic driver to just parse the unidirectional input without telemetry and so on.
We recommend using option 1 if you have a spare UART port and care about best possible support.
Relevant PR and docs link:

3- Marlene: A custom-made driver is written and cannot be launched. The driver is needing i2c.

@dagar check with i2c detect command first to find out which address your sensor is on and then initialize your driver accordingly based on that port.

PRs needing review:

1 - @dirksavage88 Add relposheading in process fix uavcan driver (AP Periph Dronecan Dual RTK support) by dirksavage88 · Pull Request #23821 · PX4/PX4-Autopilot · GitHub