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

FW crash v1.7.0-rc2 #8380

Closed
r0gelion opened this issue Nov 28, 2017 · 8 comments
Closed

FW crash v1.7.0-rc2 #8380

r0gelion opened this issue Nov 28, 2017 · 8 comments

Comments

@r0gelion
Copy link
Contributor

Phantom flying wing with Pixhawk mini autopilot running v1.7.0-rc2 (V3).

After 6 successful flights, during the 7th flight, the pilot took off in manual mode, switched to Auto and the plane accelerated to maximum thrust uncontrollably; once switched back into manual the pilot reported only partial control, attempted to land manually but crashed due to the vast acceleration and only partial control over the craft.

Log

Video

@dagar

@dagar dagar changed the title FW crash v1.0.7-rc2 FW crash v1.7.0-rc2 Nov 28, 2017
@dagar dagar self-assigned this Nov 28, 2017
@dagar dagar added this to the Release v1.7.0 milestone Nov 28, 2017
@dagar
Copy link
Member

dagar commented Nov 28, 2017

I saw this log a couple days ago. The major thing that stands out is that the pitch demand is being ignored. There's also a sizable roll offset.

image

The other minor thing is that the maximum roll max is set to 0 (unconstrained). Resetting to the default should be fine.

image

How badly damaged was the vehicle? I suspect some kind of mechanical failure. Servos, linkages, control surfaces, or possibly even the battery coming loose and moving around.

@bresch
Copy link
Member

bresch commented Dec 4, 2017

@r0gelion Link of the log is broken. Could you update it please? Server is down; let's wait.

@bkueng
Copy link
Member

bkueng commented Dec 4, 2017

@bresch Works again. Sorry I messed up an upgrade.

@bresch
Copy link
Member

bresch commented Dec 4, 2017

@bkueng Thanks!

@acfloria
Copy link
Member

acfloria commented Dec 4, 2017

@r0gelion It is probably not related to the crash but which airspeed sensor are you using?
I am asking because this value is quite high: SENS_DPRES_OFF, 122.68370819091797

@r0gelion
Copy link
Contributor Author

r0gelion commented Dec 4, 2017

@acfloria this is the airspeed used.

img_20171204_102102

Thanks!

@dagar
Copy link
Member

dagar commented Dec 4, 2017

@acfloria in my experience that's a pretty typical offset for an MS4525.

@dagar
Copy link
Member

dagar commented Dec 8, 2017

Most likely mechanical failure.

@dagar dagar closed this as completed Dec 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants