Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v1.16 Release Candidate] - Flight Testing & Flight Issues (log archive) #24188

Open
mrpollo opened this issue Jan 8, 2025 · 9 comments
Open

Comments

@mrpollo
Copy link
Contributor

mrpollo commented Jan 8, 2025

❗ About

💡 For the upcoming v1.16 release, we are asking the Community 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.16 is right for you.

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
  2. Flash the firmware (documented below)
  3. Test
  4. Upload the log (documented below)
  5. Report the test in this issue thread!

📑 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.16 beta firmware

beta_flashing

  1. Open QGC
  2. Click the Q icon on upper right > Vehicle Setup > Firmware (Step 1 in picture)
  3. Connect your flight controller to the computer
  4. When the Firmware setup window pops up, click "Advanced settings" checkbox
  5. Select "Beat Testing (beta)" from the drop down (Step 2 in picture)
  6. Click "Ok"

This should automatically flash & reboot your flight controller with the latest v1.16 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

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)
  3. Add the ULog file
  4. Fill in the description, feedback, and video URL (if available)
  5. Click "Upload"
  6. 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!

To Reproduce

No response

Expected behavior

No response

Screenshot / Media

No response

Flight Log

No response

Software Version

No response

Flight controller

No response

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

@afwilkin
Copy link
Contributor

afwilkin commented Jan 16, 2025

From @PX4/testflights

No control in stabilized mode. the drone was not reacting to my movement commands. The drone started to slide back, I would pitch forward, and the drone would not react in accordance. Tried to then pull back in case the controls were flip flopped somehow, nothing happened. Crash

https://review.px4.io/plot_app?log=fb2ea683-bfaa-449b-991f-58eae53c97dd
https://review.px4.io/plot_app?log=35493241-0b0a-42c1-9a49-3bbc1670e2ca

Drone that was being used (quadcopter, vtol, etc...): quadcopter x500
Flight controller (holybro pixhawk 6c, cube orange, etc): pixhawk 4
Radio (SBUS, sik telemetry, etc): sbus
Controller (joysticks, RC): RC
Position (GPS, VIO, Flow): GPS
ESC (dshot, pwm, etc): PWM

@afwilkin
Copy link
Contributor

afwilkin commented Jan 24, 2025

Wanted to post this here as well. Pixhawk4 with arkflow running 1.16

Video: https://www.loom.com/share/141ee5ee32f64e519b5aaf798f495941?sid=f34c75a7-4a02-4fea-be0c-6a24d3742b98
Logs:
https://review.px4.io/plot_app?log=4f5c42ac-5696-44e7-8a57-03a033661189
https://review.px4.io/plot_app?log=bb955f4b-f2d9-49d1-b96a-0ba4e06be0a6

I fly in position mode with joysticks instead of RC that i did in my initial testing

Drone that was being used (quadcopter, vtol, etc...): quadcopter x500
Flight controller (holybro pixhawk 6c, cube orange, etc): pixhawk 4
Radio (SBUS, sik telemetry, etc): sik telemetry
Controller (joysticks, RC): Joysticks
Position (GPS, VIO, Flow): ArkFlow
ESC (dshot, pwm, etc): PWM

@bresch
Copy link
Member

bresch commented Jan 24, 2025

@afwilkin Thanks for the tests.

Could you please also add a quick overview of the setup (looking at the log it's a multirotor with optical flow and range finder, no GNSS) and what's the outcome of the flight test from your perspective (e.g.: all good, height oscillation, position drift lower/higher than 1.15).

@afwilkin
Copy link
Contributor

Apologies for the delay, I thought this was in the other PR we were working on. I just updated my comments above

@afwilkin
Copy link
Contributor

From @PX4/testflights

No control in stabilized mode. the drone was not reacting to my movement commands. The drone started to slide back, I would pitch forward, and the drone would not react in accordance. Tried to then pull back in case the controls were flip flopped somehow, nothing happened. Crash

https://review.px4.io/plot_app?log=fb2ea683-bfaa-449b-991f-58eae53c97dd https://review.px4.io/plot_app?log=35493241-0b0a-42c1-9a49-3bbc1670e2ca

Drone that was being used (quadcopter, vtol, etc...): quadcopter x500 Flight controller (holybro pixhawk 6c, cube orange, etc): pixhawk 4 Radio (SBUS, sik telemetry, etc): sbus Controller (joysticks, RC): RC Position (GPS, VIO, Flow): GPS ESC (dshot, pwm, etc): PWM

Re - Stabilization Issue,

What caused the crash in my earlier post MIGHT have been more of a heading issue than a broken stabilization flight mode or RC issue. I

  1. reflashed 1.15.2 on the vehicle
  2. flew in stabilized over RC and did not see any issues
  3. Flashed 1.16.0 alpha
  4. Recalibrated the RC
  5. Reran the same tests
  6. Did not see an issue, BUT I did see points where the vehicle would randomly yaw without my input

This makes me think there might be something about the mag that is feeding in to the heading that is causing some inconsistencies between 1.15.2 and 1.16.0

@MaEtUgR
Copy link
Member

MaEtUgR commented Jan 30, 2025

@afwilkin I had a look at your original log. RC input data looks fine. Translation to setpoints also looks high level ok, tracking is not good and I think this is because the yaw rate and hence also the yaw goes unstable:
Image

Could it be that your vehicle's motor mounts on the arm are not rotated the right way or even rotated slightly the wrong way? That could explain the lack of yaw authority even if the propeller turn direction and motor assignment is correct. For reference the motors should be ever so slightly (2-5°) tilted like indicated on my drawing (assuming props turn in default "cleaning" direction otherwise everything is the opposite way):
Image

It can well be a combination e.g. the heading estimate had a problem and the lack of yaw rate control authority made it unstable or at least unable to settle in the short flight time.

@MaEtUgR
Copy link
Member

MaEtUgR commented Jan 30, 2025

I found proof for my hypothesis with the yaw authority. Two motors are basically idling and the other two carry all the weight and still the yaw turns in the wrong direction. Please verify the airframe according to my scetch. I'm happy to explain if it's not clear.
Image
Note that in the later logs you posted it's slightly better but the issue clearly still persists:
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

4 participants