Hi there - I'm a new user and have been trying to get my first mission with MapsMadeEasy off the ground.
Despite making sure I am outside any restricted zones for drones (I'm in Australia), my missions haven't been allowed to proceed - and I get an error message something like what I've written in the post title, can't recall the exact wording.
Can I get any comments on why I'd still get this message if I'm outside any restricted zones? (I'm using another app called Safe to Fly to check restrictions). Is there an additional safety tolerance distance being added?
Can I request that when missions are planned back in the office that any geofencing restrictions are raised then - rather than having to launch before finding out Maps Made Easy won't launch in that location? I've been driving further away from no fly zones and launching again without luck which is frustrating.
I'm also going through the pilot registration process here with CASA, which in the future will give me the ability to seek clearance to operate in these restricted areas - will there be any ability to remove those restrictions on an approved mission so I can use MapsMadeEasy?
Thanks in advance - Cheers Jon
This probably isn't actually an issue with a keep out zone. There was a waypoint upload error with the DJI SDK that was throwing a keep out zone error... If you see a no fly zone error and you are super sure that an NFZ is not the issue, try doing a complete system power cycle since that will usually clear the connectivity issue.
We are pretty sure this is fixed in the upcoming release.
Sorry for the frustration.
Iniciar sesión para dejar un comentario.
Thanks Ryan - that's interesting.
I tried a few different locations, each time creating new missions using the app and got the same message each time. I did shut everything down (phone, RC, UAV) between each location, but, I only closed and restarted the app between attempts at the same location. Will have to give this another try.
The first location I tried was here:
According to the Safe To Fly App, this is outside NFZ. Is there any chance I can get you to cross check with your systems understanding of NFZ's?
Cheers Jon
The thing is I don't think there is really any time where the NFZ zone errors will actually be triggered that we have tested. We test fairly close to a large international airport (in a RC flying field) and nothing ever kicks off. This was likely just a DJI SDK weirdness that will hopefully be getting better soon.
Thanks Ryan. If that's the case I will keep doing a system restart and see if I can get flying. Will let you know how I go. Cheers Jon
Hi Ryan - I tried restarting everything (device, RC, UAV) between tries in the same location - and success! Thanks for the tip. Cheers Jon
Great to hear. Thanks for checking back in.
Hopefully this won't be an issue any more very soon.
