@Adam, thank you very much for the detailed description of your M600’s behavior and for your patience.
My understanding of DJI’s latest SDK is that Pix4Dcapture does not have the ability to determine the navigation tolerances associated with the drone’s flight characteristics in any meaningful way. Including how “close” the drone must be to a waypoint before it is able to move on with the mission or, more importantly, how long the drone will hover at a waypoint before it is satisfied that it has “reached” the waypoint.
This is not the case with other Pix4Dcapture-supported drones, whose SDK provide third-party applications the option to specify waypoint distance, buffer, or tolerance, depending on how you refer to it.
I anticipate that it is not a coincidence that the drone’s flight characteristics changed around the time that Pix4Dcapture first supported custom cameras, because it is likely that an update to DJI’s SDK and firmware was released that enabled third party applications to support custom cameras. Please do not hesitate to let us know if you have reason to believe that this is not the case.
There is no doubt in my mind that it is difficult to watch your drone hover for extended periods of time at each waypoint, especially if the behavior only recently manifested itself. For this reason I have taken the opportunity to report your concerns about efficiently managing your flight time with respect to the amount of time that the drone spends at the beginning and end of each flight line. I cannot make any predictions or guarantees about when changes will be made to the time that the drone spends at each waypoint, but can assure you that the responsible parties have been notified about your concerns.
Please let us know if you experience any unexpected changes in the way that your drone flies while in the immediate vicinity of the beginning or end of a flight line.
@Thomas, thank you for your contribution.