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

PixRacer: bad gyro health message appearing intermittently #3606

Closed
rmackay9 opened this issue Feb 10, 2016 · 8 comments

Comments

Projects
None yet
7 participants
@rmackay9
Copy link
Contributor

commented Feb 10, 2016

This issue appears both with Copter-3.3.3 and Copter-3.4-dev and it's always the first IMU's gyros and accelerometers that appear as unhealthy.

@rmackay9 rmackay9 added the Copter label Feb 10, 2016

@WickedShell

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2016

I've been seeing this on a pixhawk as well starting when I shifted to using
EKF2 (plane 3.5 and master). Not sure if it is explicitly related to that
shift as I was using a new pixhawk and new firmware at the same time, but
thought I'd note that I've had this problem recently as well.

On Tue, Feb 9, 2016 at 10:36 PM, Randy Mackay notifications@github.com
wrote:

This issue appears both with Copter-3.3.3 and Copter-3.4-dev and it's
always the first IMU's gyros and accelerometers that appear as unhealthy.


Reply to this email directly or view it on GitHub
#3606.

@ycai47

This comment has been minimized.

Copy link

commented Feb 11, 2016

I have the same issue on a brand pixhawk and newly loaded firmware.

@rmackay9

This comment has been minimized.

Copy link
Contributor Author

commented Feb 20, 2016

fixed in Copter-3.3.4-rc2.

@rmackay9 rmackay9 closed this Feb 20, 2016

@mohitgodiya

This comment has been minimized.

Copy link

commented Aug 22, 2016

Hello,
I am facing the same problem since today.
I have a brand new pixhawk that I bought about a month ago, I waited for all my parts to arrive and before going for my 4th liftoff, it made an annoying sound which stopped after some time.
When I armed the vehicle and raised the throttle, it started spinning 360deg on the spot.
Next time when the annoying sound came up again, I connect the pixhawk through usb and mission planner said "BAD GYRO HEALTH"....

Please help.
Can upload video and flight logs if you want.

@magicrub

This comment has been minimized.

Copy link
Contributor

commented Aug 22, 2016

Yes, we always want logs.

On Aug 21, 2016 10:57 PM, "Mohit Godiya" notifications@github.com wrote:

Hello,
I am facing the same problem since today.
I have a brand new pixhawk that I bought about a month ago, I waited for
all my parts to arrive and before going for my 4th liftoff, it made an
annoying sound which stopped after some time.
When I armed the vehicle and raised the throttle, it started spinning
360deg on the spot.
Next time when the annoying sound came up again, I connect the pixhawk
through usb and mission planner said "BAD GYRO HEALTH"....

Please help.
Can upload video and flight logs if you want.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3606 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEj7G8Z8vvFnyiWUebvwWjzwMzBp85znks5qiTpGgaJpZM4HXBc1
.

@mohitgodiya

This comment has been minimized.

Copy link

commented Aug 22, 2016

Please find attachment as requested.

2016-08-21 20-14-40.zip

@TimothyGold

This comment has been minimized.

Copy link

commented Apr 23, 2017

I just installed a pixracer running 3.4.6 into a new Quadcopter and am finding now on every boot, I initially get a bad Gyro alarm. It continues to warn me and the message stays on the Mission Planner screen. The quad eventually passes all the checks and lets me arm and I can fly fine. Once I arm the message disappears. I haven't fully tested all the flight modes yet but Alt Hold seems to be fine. I have the same version of pixracer in a plane running 3.7.1 and I don't get these alarms on the other pixracer. I don't know if I have a bad board or if this is an indication that this bug re-appeared. I enabled logging while disarmed so that I could get a log of the status. I don't see anything in the log to indicate a problem but hopefully someone that knows can take a look and see.
2017-04-23 15-32-34.zip

@OXINARF

This comment has been minimized.

Copy link
Member

commented Apr 23, 2017

@TimothyGold We don't do support here, please post in the forum (http://discuss.ardupilot.org).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.