Pixhawk, Arduplane 3.2.2.
Hello guys,
having a problem to make EKF to work.
As soon as I put the EKF_ENABLE 1, the massage "BAD AHRS" appears on my Mission Planner screen. I couldn't find any similar topic on other forums so you're my last chance =)
I thought that it's might be a hardware problem, but both of my Pixhawks acts the same. The IMU pin legs connections on PCB are also look fine. All the initial calibration were made.
I also had an idea that it might be a wrong EKF_ or AHRS_ parameters problem, but I varied them without any successful result.
Both IMU seems to work according to log file. But most of EKF'1-4' logs shows zeros. Since it was recorded indoor so I turned off the "AHRS_GPS_USE 0", but even with its on and outdoor the result is the same - "Bad AHRS"
I also noticed that INS_PRODUCT_ID turns to "0", saying that IMU is unknown, but not 5 as it should be for Pixhawk.
Please help, I spent the 2 days solving this problem without any results!
Here are the Parameters and Logs.
Hello guys,
having a problem to make EKF to work.
As soon as I put the EKF_ENABLE 1, the massage "BAD AHRS" appears on my Mission Planner screen. I couldn't find any similar topic on other forums so you're my last chance =)
I thought that it's might be a hardware problem, but both of my Pixhawks acts the same. The IMU pin legs connections on PCB are also look fine. All the initial calibration were made.
I also had an idea that it might be a wrong EKF_ or AHRS_ parameters problem, but I varied them without any successful result.
Both IMU seems to work according to log file. But most of EKF'1-4' logs shows zeros. Since it was recorded indoor so I turned off the "AHRS_GPS_USE 0", but even with its on and outdoor the result is the same - "Bad AHRS"
I also noticed that INS_PRODUCT_ID turns to "0", saying that IMU is unknown, but not 5 as it should be for Pixhawk.
Please help, I spent the 2 days solving this problem without any results!
Here are the Parameters and Logs.
Replies
Any chance you can explain how you arm and any other pointers you may have. Its really strange as the really cheap boards dont have this issue and this was exspensive.
Are you using a compass? I get this using planes without compass and makes sense that I get the error, because the AP can't determine heading while stationary without a compass. As soon I take off the error disappears. If you have a compass, it might be a calibration / variation issue.
Same issue have run through everything. But it seems there has always been issues with this and were told its not GPS the settings are to strict repower. Looking below is questions from 2015 and Ive seen them going back to 2014 so there must be a definitive answer seeing as though its been happening since the inception of the board.
PLEASE HELLLLLP!
i had the same thing, and performed an accell calibration, and it fixed it.
if it happens often, apparently, re-arming with the plane still fixes it for some, but this is the long term solution.
hope my experience helps others.
@Hisham - So to fix the AHRS problem, you just turned off the internal compass?
Hi lately i Have did 3 test flights regardless of the compass variance and bad ahrs i have. All safe landing and recovery.
since the bad AHRS flag went off after 40sec consistently, i assumed like other Avionics on an airplane we have 7 mins to realign the INS IRS and gyro. so i gave it a go call. the only problem i had was with the Compass alignment keep on getting compass variance, by crosschecking with actual compass the primary compass seems to giving out correct reading +- 2 degree which is acceptable for flying. gps hdop was good.. so i turn off the 2nd onboard compass. ARMed and There she goes. though from time to time I had a compass variance flag due to EKF.
I'm about ready to throw away a brand new Pixracer because I can't get rid of this error. I've tried all of the fixes listed here and elsewhere and it continues to happen. It's really starting to piss me off.
I left the Ardupilot world over three years ago because I couldn't get beyond compass problems on the then new Pixhawk, but recent hardware and software looked interesting so I decided to give it a try again. But wasting a weekend on this probably is about ready to drive me away again. We REALLY need some way to get more info about these errors and what's causing them. Does anyone know if it's caused by the IMU, GPS, barometer, magnetometer, phase of the moon???? How can we debug these things?
I'm running the latest release Plane firmware on a new genuine Pixracer with AUAV.co GPS and other accessories.
i have this problem running arduplane on pixhawk, runing the same firmware..only is mine shows up after powering and it goes away after 40sec. consistantly.
I'm with the same version of Fw and same problem as yours. Is there a solution? Any firmware that corrected this error?
Mike said:
-
1
-
2
-
3
-
4
of 4 Next