Nidge
Second Officer
United Kingdom
Offline
|
steamship Posted at 2-23 08:07
I'm not against NFZ's as long as they are implemented correctly. But as DJI are incapable of doing this I decided to remove the NFZ's from my DJI Spark in preference to obiding by the correct NFZ's as dictated by the relavent authorities.
Neither am I, and quite frankly I'd rather keep away from airports, but when I'm 10 miles from the end of a disused runway threshold in a river valley surrounded by trees, it's annoying to say the least that I get warnings from the app.
Be prepared to hear the distant sound of silence, or at best a C&P response thanking you for choosing DJI. I did similar and found myself farming tumbleweeds.
I still use some DJI products, I recently picked up a Mini2 Flymore pack but only because it was heavily discounted, but the last thing I expect is any meaningful or useful communication from DJI. In contrast I have a Yuneec Q500 which also had overly large NFZ’s embedded in it. I contacted Yuneec and explained the situation and in reply I received an alternative Firmware package without the NFZ’s in it.
I’ve dealt with other manufacturers, such as Parrot and Powervision, and in every case I’ve had a quick response from someone directly involved with the software and/or hardware. With DJI I’ve only ever received an initial copy and paste response and my questions and concerns probably never getting any further than DJI’s castle ramparts.
As I said I still use DJI parts - Naza, Wookong, and A2, flight controllers and the propulsion systems - in my builds, but I don’t expect any support for these as they are termed legacy systems. But at the time when I was having issues with the Datalink system it was very much a current product in production but I, and many others, were totally ignored by DJI.
This turned out to be overly ranty the more I typed, my apologies for that. |
|