I have read that the default delay of 220 ms is too large got the new M8N series. Some have suggested that 120 might be better but those who have tested that say it’s too small and does not fly well.
Can anyone give me ideas on what parameters to look at to correctly tune the delay? Has anyone done these tests?
.
Replies
I am noticing a small glitch when it transitions from one waypoint to the next. That’s why I wanted to try tuning it. It would be nice to know how the developers cane up with the 220 ms delay number.
Looking at parameters I see the raw GPS velocity but don’t find an equivalent IMU parameter to compare it to.
Maybe the just calculated 220 using the ublox data sheet. I looked at the M8 data sheet and it was not obvious what the velocity calculation delay is.
Has anyone seen any information on this subject?
Which developer is working on EKF. Maybe they would be able to help?
.
If you search the last few pages of the rc3.3 beta thread someone mentions who the EKF developer is, I can't recall the name but saw it recently
I wouldn't mess around with it...I fly m8n with that setting and it works fine