Fixed Wing Dead Reckoning test of the Zealot H743 Aero Applications Edition

After repairs I now have a simpler plane. I disabled the GPS partway through this longish mission on a day with absolutely no wind (Oh - and a working AirSpeed sensor!) and got this.

I think it looks pretty good (as far as dead reckoning goes) - or maybe I’m missing something?

@timtuxworth that worked, but wasn’t quite a correct test. You should have made RC7 go above 1800 to disable GPS. The switching to a non-GPS EKF source isn’t quite the same thing as disabling GPS.
The results were good though:


about 125m error in 5 minutes, which is 25 meters/minute.
The result was the same for both of your IMUs:

this is definately better than average for this type of dead-reckoning test!

2 Likes

Thanks Tridge. BTW - the Zealot H743 has 3 IMUs.

I’ll try to test again with low wind and (and flipping the GPS switch all the way high). Weather dependent - but it will happen.

Great weather today. 0 m/s windspeed (measured at the ground)

I got 3 flights, switched off GPS on each and switched to second EKF configuration to avoid fallback to DCM. I let the plane fly as long as I felt safe on no GPS. I think there might have been a breeze up higher as there was some drift especially on the second flight. This was running on 4.4.0 beta 4.

I’m kind of disappointed, is this the best we can expect? Should I be doing something different?

Another flight at a different location. 0m/s windspeed where I was standing. Same plane, same FC. After about 3 minutes it was off by about 150m so I pulled the trigger and re-enabled the GPS. Looking forward to some more ideas @tridge

I would try doing few circles before disabling GPS.

Thanks - I’ll try that

Other than that optical flow with appropriate rangefinder could help further constraining drift even when the wind is changing.

Could you tell me how to multiply arsp.airspeed with ctun.e2t, I could not do it with mission planner, thanks

Tridge and I have been using mavexplorer.py. You might also be able to do it in plot.ardupilot.org

thanks, I did it use this link

Just want to note 2 recent improvements to the DCM fallback code that might help with this. I’m hoping to do some more testing of this soon, so don’t want to forget

AHRS_Options to disable DCM fallback AHRS: added AHRS_OPTIONS and jamming simulator by tridge · Pull Request #25676 · ArduPilot/ardupilot · GitHub
Don’t fallback to DCM if DCM has no GPS Don't Switch to DCM to get Better GPS if DCM Isn't Using GPS by njwhite · Pull Request #25707 · ArduPilot/ardupilot · GitHub

1 Like

How is this done? Set GPS_AUTO_SWITCH=0 and then have your script toggle the GPS_PRIMARY parameter as desired?

with RCx_OPTION 65 (GPS disable)

what do you mean by this?, I have set one switch, to switch between AHRS:EKF3 AND AHRS:DCM, i want to test the AHRS:DCM with GPS disabled and how dead reckoning works from the last gps fix.
Also when AHRS;EKF3 is active and when i disable the GPS, it falls back to AHRS:DCM, does that mean AHRS:EKF3 does not provide dead reckoning support in latest ArduPlane 4.6 build?

If we disable the DCM fallback in fixed wing plane and disable the GPS, then the EKF3 supports the location dead reckoning? The dead reckoning in this case (no airspeed sensor is used, only compass, barometer and IMU are the available sensors) is just getting the speed from the intergrated accelerometer data from the IMU and multiplied from known time interval right?

What is the best way to get AHRS:DCM Dead-reckoning results without GPS once the home position is set from the GPS fix, when tried to walk with the plane with GPS disabled, the live view in the mission planner maps looked almost same as the AHRS:EKF with results. Further more when i disconnected the GPS while moving, the live plane shown in the mission planner map window disappeared until unless I connected back again.

This was which the GPS use with AHRS:DCM enabled for postion