This most probably WILL NOT solve the DJI dodgy SDK/no RTH in Autopilot issue. I say that because autoflight logic have informed us that all flight modes are affected. Joystick mode almost cerrainly uses the custom flight controller (just like waypoint and other flight modes). Loss of control signal will be hover untill critical battery.
Hi- no one said it would. The OP just wanted a method to slowly and manually fly along the waypoint flight path to see when/where his signal may begin to drop.
You can use the Mission Start Marker to start a Waypoint Mission from where you left off. Just long press on the path location where you want it to resume and place the Start marker.
Autopilot is iOS only right now. There is a lengthy thread comparing the two here.
Yes, I personally would prefer the mission to continue, even if signal is lost. Far safer and would allow shooting behind obstructions that manual flying would prohibit.
Understood. My intent was only to ensure that those cautious about flying with the current SDK issue
yep... And if his signal drops completely it's hover until critical battery level. My point was to ensure people don't get a false sense of security. That's all.
It wasn't a question of deciding to allow or disallow it. We had to make a choice between offering several other unique features, or give up those features in order to offer this one particular feature (LCMC). The decision and resulting list of gained features is documented here. We are open to implementing LCMC in the future, but realize that it will result in a "stripped down" version of Waypoint Mode without the above features, and further encourage people to do unsafe things with drones (for example fly on the other side of buildings without any ability to see or control the aircraft in the case of an emergency).
People will always find ways around restrictions. The point is that knowing RTH will activated in Autopilot will (hopefully) discourage users from executing the mission in the first place. If they want to look elsewhere for the functionality, there is, of course, nothing stopping them. My point is that we wanted to offer a very specific set of features that we couldn't offer if we supported LCMC. Given that most LCMC situations are unsafe, we are okay with that decision, at least in the short to medium term until the FAA formalizes the rules.
Without wising to offend, you've already stated your position is that anyone flying BLOS is flying illegally, so no matter how safe or prudent a LCMC is (say with a spotter), you won't enable "illegal" maneuvers, which leaves us, instead, with a drone eventually landing in place, after a loss of signal while flying a mission, which, in fact, could be far more dangerous. Let the user decide how they want to use the software, rather than imposing your personal agenda upon its use. If we wanted that, we'd all still be using DJI GO with geofencing, and all the limitations and restrictions DJI places upon waypoints and orbits.
Not true, here is what we actually stated:
You, of course, challenged that on a technicality:
Are the FAA guidelines a law that has been signed by congress? No.Isn't the phrase you are looking for "inconsistent with FAA Guidelines" and not "illegal"?
I am not questioning the benefits of your app for VLOS flying, and will likely purchase it for them. The DJI GO app implementation of waypoints is quite crippled, and imposes limitations in terms of preflying and 500m distance limitations. No one wants those features copied. We would like them circumvented. LCMC would be a big safety advantage over landing in place. Your initial responses sounded judgemental, but I can see you are doing the best you can within the parameters. Keep up the good work!
We are currently still looking into it.
They still maintain that it will be fixed in the next firmware release.
You might consider using Airspace and leaving the RC on dry ground with someone.
