Lots of error messages including ekf variance,GPS glitch etc.Logs attached

Hi all,
Its my first traditional helicopter build on Blade 450 3D with a flybar.Heli was flying fine before installing arducopter.Board is OmnibusF4V3Pro running latest stable release and is hard mounted inside the frame under the main gear.

When i arm it,everything seems normal and no ekf messages and no gps related messages.But as soon as i start the motor,i start getting all king of error messages.I was only able to hover slightly as its kind of unstable.GPS is mounted on the tail boom.Could it be due to carbon fibre main blades and causing the gps signal issues?But my hdop always stayed good.Could anyone please have a look at my log?Thanks.
Log

ERRORS
TIME Subsys ECode Description
19:25:33 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:25:33 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:25:46 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:25:46 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:25:50 11 2 GPS: GPS GLITCH
19:25:50 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:25:50 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:25:51 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:25:51 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:26:02 11 0 GPS: ERROR RESOLVED/CLEARED
19:26:36 29 1 : OCCURED OR FAILED TO INITILIASE
19:26:36 11 2 GPS: GPS GLITCH
19:26:42 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:26:42 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:26:47 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:26:47 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:26:53 29 0 : ERROR RESOLVED/CLEARED
19:26:58 11 0 GPS: ERROR RESOLVED/CLEARED
19:27:10 11 2 GPS: GPS GLITCH
19:27:10 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:27:10 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:27:18 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:27:18 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:27:28 11 0 GPS: ERROR RESOLVED/CLEARED
19:28:27 29 1 : OCCURED OR FAILED TO INITILIASE
19:28:27 11 2 GPS: GPS GLITCH
19:28:37 11 0 GPS: ERROR RESOLVED/CLEARED
19:28:42 29 0 : ERROR RESOLVED/CLEARED
19:29:00 11 2 GPS: GPS GLITCH
19:29:00 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:29:00 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:29:08 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:29:08 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:29:11 25 1 : OCCURED OR FAILED TO INITILIASE
19:29:14 16 2 EKF CHECK: EKF CHECK BAD VARIANCE
19:29:14 17 1 EKFINAV FAILSAFE: OCCURED OR FAILED TO INITILIASE
19:29:15 29 1 : OCCURED OR FAILED TO INITILIASE
19:29:30 16 0 EKF CHECK: EKF CHECK VARIANCE CLEARED
19:29:30 17 0 EKFINAV FAILSAFE: ERROR RESOLVED/CLEARED
19:29:40 11 0 GPS: ERROR RESOLVED/CLEARED
19:29:45 29 0 : ERROR RESOLVED/CLEARED
LOG
TIME MESSAGE
19:25:34 ArduCopter V4.0.3 (ffd08628)
19:25:34 ChibiOS: d4fce84e
19:25:34 omnibusf4pro 001D0047 324D5007 20333256
19:25:34 Param space used: 1097/9728
19:25:34 RC Protocol: SBUS
19:25:34 New mission
19:25:34 New rally
19:25:34 Frame: HELI
19:25:34 GPS 1: detected as u-blox at 115200 baud
19:25:34 u-blox 1 HW: 00080000 SW: ROM CORE 3.01 (107888)
19:25:45 EKF2 IMU0 is using GPS
19:25:49 EKF2 IMU0 in-flight yaw alignment complete
19:25:50 GPS Glitch
19:26:02 GPS Glitch cleared
19:26:36 Vibration compensation ON
19:26:36 GPS Glitch
19:26:42 EKF2 IMU0 in-flight yaw alignment complete
19:26:42 EKF variance
19:26:53 Vibration compensation OFF
19:26:58 GPS Glitch cleared
19:27:10 GPS Glitch
19:27:28 GPS Glitch cleared
19:28:24 EKF2 IMU0 in-flight yaw alignment complete
19:28:27 Vibration compensation ON
19:28:27 GPS Glitch
19:28:37 GPS Glitch cleared
19:28:42 Vibration compensation OFF
19:28:59 EKF2 IMU0 in-flight yaw alignment complete
19:29:00 GPS Glitch
19:29:00 EKF variance
19:29:11 Potential Thrust Loss (1)
19:29:15 Vibration compensation ON
19:29:29 SmartRTL deactivated: bad position
19:29:40 GPS Glitch cleared
19:29:45 Vibration compensation OFF indent preformatted text by 4 spaces

I will try to look at it tonight and get back to you.

1 Like

Thanks Bill.I really appreciate it!!

Hi,
First GPS fix occurs at: 19:25:45
First glitch occurs around 12sec later at 19:25:50

Everything after that is just repeated glitching.

Whats happening if you let the GPS settle in not armed state for 10-15min?

Thanks Flats.

But heli was on before this flight for around 10 mins. I was watching no.of sats to go high and HDOP to go low before arming.I only armed once HDOP went below .8

After reading more in the docs,looks like i am getting EKF and vibration failsafes.

Not sure if its the GPS that is causing these issues or something else?My GPS is close to Frsky R9mm 900mhz antenna.

@ninja_zx11 I would agree that I think it has something to do with the vibrations. Here is a plot of the vibrations and you notice that they spike pretty high and the error occurs about that time. I’m not sure if the GPS glitch is also due to the high vibrations. I don’t know much about what affects the GPS and causes GPS glitches. Sorry.

Thanks Bill for looking at it.I am going to mount my Flight controller board on rubber dampers as currently it’s hard mounted and there is absolutely no vibration damping.

I don’t see a single clip on the accels in that log. The y-axis might be a bit high on vibes, but not to where it will cause this GPS glitching.

Each GPS satellite transmits data on two frequencies, L1 (1575.42 Mhz) and L2 (1227.60 MHz).

Get that antenna away from the GPS receiver. It is entirely plausible that you are overloading the front end on the receiver, especially if the R9 system is using telemetry. You’re too close to the L2 frequency for comfort with the R9 system.

HDOP doesn’t mean anything as far as xy precision of the GPS. It is merely a relative measure of the quality of the satellite constellation and their position in the sky. The atomic clocks on the satellites produces the fundamental L-band frequency. The L1and L2 carrier frequencies are generated by multiplying the fundamental frequency by 154 and 120, respectively. These corrections are superimposed onto the carrier frequencies, L1 and L2. The measured travel times of the signals from the satellites to the receiver are used to compute the range. If those time stamps are off, you will get “glitching”. It has nothing to do with vibration.

Thanks Chris for chiming in.

I am little confused here.In the docs it says that vibrations under 30 are acceptable.As you said that vibrations on mine heli were not that bad.X and Z under 20 and Y close to 30 when my rotor head reaches its normal speed.Then why i am getting vibration failsafe. Its indicated by vibration compensation on.

We can co-relate EKF fail-safe due to GPS but why there is a vibration fail-safe.I did see in a log that once my GPS location jumped 20~30 meters thou.

I have dismantled my FC board installation but do you think i still should try moving R9mm antenna away or try Frsky 2.4ghz r-Xsr receiver before installing my FC board on a rubber damper plate?Thanks.

If you have a XJT module in your radio and have a XSR receiver handy try that first to see if it gets rid of that GPS problem. That will cause the EKF to fault due to continuous GPS issues and position error, and it looks to me in the GPS outputs that it is really similar to GPS jamming.

You’ll have to do something about the vibration. It didn’t clip the accels (16G limit), but it is pretty high on y-axis and that will cause bad handling. Fortunately that board you have only has one IMU, otherwise without making settings to which IMU is being used it would switch EKF processes and result in loss of control of the machine. The EKF uses the GPS to correct for bias and drift in just about all the other sensors, and without that working properly the system won’t fly.

Your GPS receiver is likely using the defaults. If you are in the U.S. I would configure it to use only one constellation - GPS with WAAS correction. And limit the satellites to no lower than 20 degrees above the horizon. There should be 9 or 10 visible at all times, sometimes up to 12. If you are north of the 50th parallel then configure it to use GLONASS (Russian satellites) which is more accurate in the northern latitudes. This gives you the fastest update rate for your GPS vs the defaults where it acquires every satellite from every constellation it can grab. The receiver is multi-band, but the refresh rate drops if you let it suck in every constellation it can get. You only need 4 satellites for a 3D fix. 7 is enough for a RNAV approach in manned aircraft. Many people think the more satellites they get, the better it is. That ain’t how those GPS receivers work.

Thanks Chris for all the good info.Yes i have Qx7 and i will try R-Xsr and see if that makes any difference.I will be mounting FC on a damper too then for better handling.

Any idea what part on the heli could create Y-axis vibrations?Y axis vibrations are in roll axis right?

I have no idea. Since roll is less damped than pitch it could be something as simple as rotor tracking or balance.

2 Likes

So finally was able to hover nicely in position hold mode!! Thanks all for your help!!

Now X and Y axis vibrations are under control but Z axis vibrations seems to be high.How are Z axis vibrations defined?Does it mean that heli is vibrating in yaw axis or up and down axis?If its up and down then it could be from the slapping airflow under the rotor blades as i mounted my FC board on a rubber dampers under the blades.

I am going to move the GPS on the top of FC and away from Rx antenna as i still get gps glitch sometimes.Also i will fix all the loose wires.I will also remove the training gear once it gets tuned properly:)

Now could anybody please check my log if i need any tuning or i need to do something?

Log is here.

Thanks again.