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

Issue with landing PixRacer FMUV4_K66, FMUv5 #13956

Closed
Tony3dr opened this issue Jan 15, 2020 · 6 comments · Fixed by #14702
Closed

Issue with landing PixRacer FMUV4_K66, FMUv5 #13956

Tony3dr opened this issue Jan 15, 2020 · 6 comments · Fixed by #14702

Comments

@Tony3dr
Copy link

Tony3dr commented Jan 15, 2020

Describe the bug
When flying the vehicle in Mission mode and trigger RTL, upon landing the vehicle does not descend vertically but drifts away with the wind. I had to take command of the vehicle in position mode and landed the vehicle manually. This is an issue that we have seen constantly, with the PixRacer and K66, FMUv5. We are seeing this issue when the wind is 6 m/s and over.

To Reproduce
Steps to reproduce the behavior:

  1. Drone switched on
  2. Uploaded mission to the vehicle
  3. Took off in Mission Mode
  4. All commands were sent form QGC (Armed and takeoff)
  5. Once all waypoint completed vehicle switched to RTL
  6. When the vehicle was landing, it did not descend vertically, drifted away with the wind and landed the vehicle manually

Expected behavior
The vehicle should land and disarm.

Log Files and Screenshots
This is the latest PR tested with the PixRacer and issue persisted, Reference #13678
Logs: https://review.px4.io/plot_app?log=67a2120c-a473-43a3-a556-6a542f62f7b1

Issue noticed on Reference #13701, wind 10.2 m/s, PixRacer.

Issue noticed on Reference #13745, wind 10.2 m/s, PixRacer V4.
Log: https://review.px4.io/plot_app?log=719ab88b-d993-47c8-a9ca-eaf429d4577e

Issue noticed on Reference #13613, 10.2 m / s, PixRacer V4.
Logs: https://review.px4.io/plot_app?log=b0f1f872-fc9e-41ee-89e3-4e146862efc7
Log: https://review.px4.io/plot_app?log=a8a1391c-06c0-475e-943a-48bea5da2e24

Issue noticed on Reference #13065, NXP_FMUK66_V3,
Logs: https://review.px4.io/plot_app?log=792db7ac-8738-4bdd-8a03-aa6d88b371b3

Drone (please complete the following information):
PixRacer
Frame: DJI F450
Flight Controller: PixRacer
GPS: Readytosky M8N GPS Module Built-in Compass
Motors: T Motor 2212-920kv
Propellers: DJI Phantom Built-in Nut Upgrade Propellers - MR PH 9.4x5
Receiver: FrSky D4R-II 2.4G 4CH ACCST Telemetry Receiver
Telemetry:Holibro Telemetry, 100mW Telemetry Radio V3 915MHz
ESC: Hobbywing XRotor 20A APAC Brushless ESC
Battery: 3S 5200mAh(Hobbyking)

NXP:
Vehicle description: RDDRONE-FMUK66
Flight Controller: FMUK66
Frame: ReadytoSky LJI X4 500
Motors: ReadytoSky RS2212 920 kV CW & CCW
Propellers: LJI 9450 self-locking propellers
GPS: Holybro Pixhawk 4 GPS
ESC: ReadytoSky 2-6S 40 A OPTO ESCs
Battery: 3S 5200mAh

Additional context
We will test when windy on Master and Stable and see if the issue persists.

@julianoes julianoes removed their assignment Jan 16, 2020
@julianoes
Copy link
Contributor

FYI @MaEtUgR

@devararendy
Copy link

Woww I also have same problem.
Unfortunately I only have the video. I don't have the flight log.

I'm using PixRacer with PX4 v1.9.2 firmware. And I'm using ublox m8n + LNA. I got 18 satelites and the compass also working correctly.

And actually the battery is still enough, I only set the minimum voltage per cell a bit higher.

When I started Auto Mode, it flew a couple meter then changed to Land Mode due to the drone detect low battery. But instead of landing, this drone flew away and landed quite far and I dont know where is it.

I only have the video from GCS.

A few second before loss os at 13:30

Here is the video.
Raw footage PixRacer before flew away

@julianoes
Copy link
Contributor

@devararendy sorry about your fly away! What concerns me in the video is that you repeatedly get preflight errors about GPS velocity not being accurate enough. I'm not sure if that has something to do with it.

@devararendy
Copy link

@devararendy sorry about your fly away! What concerns me in the video is that you repeatedly get preflight errors about GPS velocity not being accurate enough. I'm not sure if that has something to do with it.

Thank You very much @julianoes hmm yeaaa, btw why i got GPS velocity not being accurate ? cuz I got 18 satellites.
And if you see the last mode is Land Mode, but it's not descending. is it due to the GPS velocity is not accurate, so the FC trying to maintain the horizontal velocity to zero before descending ? Hopefully you can help us figure it out. cuz i would like to build another drone again

Thank You very much
Best Regards

devararendy

@julianoes
Copy link
Contributor

btw why i got GPS velocity not being accurate ?

Yes, I wonder too. A log would probably tell us.

@MaEtUgR
Copy link
Member

MaEtUgR commented Apr 16, 2020

Thanks to @Tony3dr for reporting this issue in this exemplary manner. I remembered it when debugging different issues today and found the cause:

Clearly visible in the posted logs e.g.

Issue noticed on Reference #13701, wind 10.2 m/s, PixRacer.

image

I'm looking into the proper way to fix this particular issue.
That said the complexity of the architecture going from RTL state to mission item type to triplet.current type to special case mapping in the setpoint generation to then result in control tracking problems shows to me that we'll need to change that to scale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants