Replies

  • EDIT. I found the bug!

    I have my MP distance set to feet, not meters. When the distance units of feet is selected, it wont fill in the polygon. I changed it to meters and it filled it in with all the waypoints and camera triggers!

     

     

  • Heres the issues condensed:

    Its 8 minutes of me complaining while showing you whats going on, so bear with me...

     

  • T3

    Grid V2 works perfect on Mission Planner 1.2.50.  I had some issues updating from 1.2.47. So i did a clean install.

    3692719375?profile=original

    Matt, ive read most of your posts regarding triggering. Iam not an expert nor i use it, BUT! I think you have mastered the Arduplane flight and now you are stacked with these do commands for the everending searching for perfection/timing.

    What i really mean is. Do you really need triggering for mapping? 

    Supposed devs-you-me fixes the code, what is the advantage in precision? IMHO more failure points, more latency between commant-clik-shutter etc.

    New imagine/photogrammetry softwares, doesnt need coords, imu data, even straight down photos! You just drop your SD card in and they do the magic.. 

    Keep it simple, try something like intervals. It always pays back! 

    Best Regards

    James

  • Can anybody advise on this? Im stuck, unable to do the simplest mapping mission because it only fills in a few waypoints.

  • download?id=705844%3AUploadedFile%3A1227113

  • Is there anybody that can confirm that GridV2 does or does not fill in the polygon??

This reply was deleted.

Activity