Whoohoo!


What’s left?

  • Refine the u-blox NEO-M8T to use the “pedestian” model algorithm which is more accurate than the current “portable” model used.
  • Test the yaw code I’ve been working on in the background so ‘H’ always points in the way she’s going.
  • Stop swearing at Microsoft for the Spectre and Meltdown updates they installed this morning which has crippled my PC just loading web pages!

4 thoughts on “Whoohoo!

    • Can you explain why please? Based on the NEO-M8T spec, page 19 (https://www.u-blox.com/sites/default/files/products/documents/u-blox8-M8_ReceiverDescrProtSpec_%28UBX-13003221%29.pdf), ÔÇťAirborne < 1g". At one meter height and 10 fps, that means absolute maximum speed is ~5m/s as the cameras AOV is about 50 degrees. Put that together and the piDrone is only moving at the same rate / acceleration as a human walking. Don't get me wrong, I'm happy to try it, but I strongly prefer to understand why it would be better first. Thx.

        • OK, I may give it a go, though my UAV is autonomous and has speeds limited to 1.5m/s and low acceleration like a “pedestrian”. What I need is high accuracy of locations.

          The INAV one has to track human controlled drones going much faster and accelerating harder than a car hence I can see why “Airboure <1g" is what you need. Certainly I can see that "pedestrian" would be awful for what you need.

Leave a Reply

Your email address will not be published. Required fields are marked *