PX4 Sync / Q&A: Aug 14, 2024

farhang · August 12, 2024, 5:41pm

Agenda

Announcements
Release Discussion
Q&A

Announcements

ARK Electronics amazing tutorial for ROS 2+PX4 :

Release Discussion

Note: The release tag is going to be cut today and a stable release the next week is expected.

github.com/PX4/PX4-Autopilot

[v1.15 Release Candidate] - Flight Testing & Flight Issues (log archive)

opened 09:49PM - 01 Aug 24 UTC

mrpollo

feature-request

## :exclamation: About 💡 For the upcoming v1.15 release, we are asking the Comm…unity for flight tests. This issue will be used for keeping track of all the tests from the Community. If you're unsure about upgrading, please read the preliminary release notes on the PX4 docs. Pay close attention to the Upgrade Guide before deciding if v1.15 is right for you. - [v1.15 Release Notes](https://docs.px4.io/main/en/releases/1.15.html) ## Pending Issues - ## ❓ Why we need flight testing 🌏 Thousands of people around the world depend on the stable release of PX4. 🖐️ Before every major release, as much testing as possible is needed to ensure that our release actually works! 😯 Simply said, **more testing = better release** 🤗 We would like to encourage every community member to join us in improving PX4! ## 🤷 How you can help with flight testing 😱 Even if you have never contributed a flight testing report, fear not! Please follow the steps below for the details of how you can contribute to flight testing. 1. **Select** a category from the "flight testing matrix" below 1. **Flash** the firmware (documented below) 1. **Test** 1. **Upload** the log (documented below) 1. **Report** the test in this issue thread! ### :bookmark_tabs: Flight testing matrix 📖 **Here are the table of things we need tests for.** This will constantly get updated, and your contribution to testing the missing slots (tests needed) will be greatly appreciated! | Title | Description | Vehicle/Hardware requirements | Testing procedure | Test logs | Related issue/posts | |---|---|---|---|---|---| | General | By testing your usual setup, we want to capture any regression / weird behaviors you may notice | Any | Test what you usually use for your personal usage, and report it to the comment below | | | ### How to flash v1.15 beta firmware ![beta_flashing](https://user-images.githubusercontent.com/23277211/230138126-c7b02c00-f07b-4a4f-b6b7-866d69db6520.png) 1. Open QGC 3. Click the Q icon on upper right > Vehicle Setup > Firmware (Step 1 in picture) 4. Connect your flight controller to the computer 5. When the Firmware setup window pops up, click "Advanced settings" checkbox 6. Select "Beat Testing (beta)" from the drop down (Step 2 in picture) 7. Click "Ok" This should automatically flash & reboot your flight controller with the latest v1.15 beta release! ### How to share your log First, retreive the log from the flight controller in QGC Q icon > Analyze Tools > Log Download, and find the log you want to download. ![log_uploading](https://user-images.githubusercontent.com/23277211/230143915-4dad89ec-ab6d-43f3-9e5f-7a4624faa56e.png) Then: 1. Go to https://logs.px4.io/ 2. Click on "Flight Report" tab (this allows public viewing of the log in the [browse page](https://logs.px4.io/browse)) 3. Add the ULog file 5. Fill in the description, feedback, and video URL (if available) 6. Click "Upload" 7. Copy and paste the link of the log, and share it to this thread When posting on this thread, please mention what kind of test it was (especially if it is one of the testing matrix options) & general info behind it! ## Questions? Feel free to ask any questions regarding flight testing in the #dev-team channel in the [discord server](https://discord.gg/dronecode)!

Bug report / Q&A

Is it possible to send same PWM output group from HITL?

Either px4io or px4pwm modules could be enabled and used.

github.com/PX4/PX4-Autopilot

[Bug] (v1.14.3) Holybro Pixhawk 5X: Failed to init INA226

opened 02:43PM - 14 Aug 24 UTC

mrpollo

bug-report

### Describe the bug It seems like the INA226 in the Holybro Pixhawk 5X is no…t being detected using PX4 v1.14.3, I suspect there's an issue in the board config files. Here's en excerpt from the `dmesg` output. Screenshots and full `dmesg` output on the forum post linked below. ``` Board sensors: /etc/init.d/rc.board_sensors INFO [ina226] Failed to init INA226 on bus 1, but will try again periodically. ina226 #0 on I2C bus 1 (external) address 0x41 INFO [ina226] Failed to init INA226 on bus 2, but will try again periodically. ina226 #1 on I2C bus 2 (external) address 0x41 WARN [SPI_I2C] ist8310: no instance started (no device on bus?) bmp388 #0 on I2C bus 4 (external) address 0x77 bmp388 #1 on I2C bus 2 (external) address 0x76 ``` https://discuss.px4.io/t/holybro-5x-sensors-not-found-with-px4-v1-14/39815/5?u=rroche **Sensor Status** ``` nsh> sensors status selected gyro: 0 (0) validator: best: -1, prev best: -1, failsafe: NO (0 events) selected accel: 0 (0) validator: best: -1, prev best: -1, failsafe: NO (0 events) validator: best: -1, prev best: -1, failsafe: NO (0 events) [vehicle_air_data] selected BARO: 6780433 (1) validator: best: 1, prev best: 1, failsafe: NO (0 events) sensor #0, prio: 50, state: OK val: 100474.7813, lp: 100477.6953 mean dev: -0.0350 RMS: 1.6701 conf: 1.0000 val: 30.8700, lp: 30.8779 mean dev: 0.0263 RMS: 0.0341 conf: 1.0000 val: 71.0282, lp: 70.7894 mean dev: -0.0049 RMS: 0.1399 conf: 1.0000 sensor #1, prio: 75, state: OK val: 100508.6563, lp: 100508.9922 mean dev: -0.0533 RMS: 1.5992 conf: 1.0000 val: 31.1700, lp: 31.1797 mean dev: 0.0278 RMS: 0.0717 conf: 1.0000 val: 68.1877, lp: 68.1662 mean dev: -0.0034 RMS: 0.1340 conf: 1.0000 BARO 6780705 EN: 1, offset: 0.000, Internal BARO 6780433 EN: 1, offset: 0.000, Ext Airspeed status: no data [vehicle_acceleration] selected sensor: 0, rate: nan Hz, estimated bias: [0.0000 0.0000 0.0000] ACC 0 EN: 1, offset: [0.000 0.000 0.000], scale: [1.000 1.000 1.000], Internal [vehicle_angular_velocity] selected sensor: 0, rate: nan Hz , estimated bias: [0.00000 0.00000 0.00000] GYRO 0 EN: 1, offset: [0.000 0.000 0.000], Internal vehicle_angular_velocity: gyro filter: 85532 events, 1407745us elapsed, 16.46us avg, min 14us max 32us 0.934us rms vehicle_angular_velocity: gyro filter reset: 0 events vehicle_angular_velocity: gyro selection changed: 0 events [vehicle_gps_position] selected GPS: 0 nsh> ```

Review needed

github.com/PX4/PX4-Autopilot

gps(septentrio): add resilience information reporting

PX4:main ← flyingthingsintothings:pr-resilience

opened 01:05PM - 06 May 24 UTC

flyingthingsintothings

+398 -9

### Solved Problem When errors occur in attached GNSS receivers, there is no wa…y to report them to the user so they know what is going wrong. ### Solution - Add automatic configuration for Septentrio receivers to report resilience information every second - Add to Septentrio parser so it can parse the new message types - Change the uORB message for GNSS information to support this new information - Report the changes through MAVLink (submodule still needs to be updated) ### Changelog Entry For release notes: ``` Feature: Report resilience information from GNSS receivers Documentation: Need to clarify page ... ``` ### Alternatives \/ ### Test coverage \/ ### Context Another part has been implemented for QGroundControl to display this new information to users. This feature was proposed during the 2022 Developer Summit and received positive feedback. Messages to report jamming and spoofing state were already in the uORB protocol, but weren't used by any modules. I would love to discuss this during the next Community Q&A call on Wednesday 🙂 - https://github.com/mavlink/qgroundcontrol/pull/11486 - https://github.com/mavlink/mavlink/pull/2110