hi daren,
very nice, i just tested your code in navdata.c and it seems to work.
the MagFreezeCount needs to be reset in an else clause of
if (LastMagValue == navdata.mx)
have you tested how the 20ms or so navdata dropout is reflected during
flight? need to rush now, can only try that next week.
cheers, opt
opersupport writes:
I believe the problem might still occur on Paparazzi, considering that this
has happened with the "toilet bowl" effect with one particular incident.
http://lists.paparazziuav.org/Interesting-flight-with-ARDrone2-and-master-branch-td14499.html#a14679
For resetting the nav board, I modified some code by hand and re-compiled,
not with the Paparazzi source. I believe you can write something simple to
reset it yourself. My logic looks something like this, it occurs inside the
navigation update function
Use at your own risk, i've only tested on my custom code which works
similarly to Paparazzi but is not set up exactly the same way
--
View this message in context:
http://lists.paparazziuav.org/Magnetometer-freeze-problem-occurring-AR-Drone-2-0-tp15283p15575.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.
_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel