If you were charging it in the car after it being discharged for 10 days, how did you fly the day before?
If you were charging it in the car after it being discharged for 10 days, how did you fly the day before?
Ok, that's what I figured. So yeah, it must be a parameter saved bird side, like RTH height, etc, which as we know is controlled by the app and independent of which device you use to connect. So in order to test the hypothesis you would need to:I flew using my phone, so maybe the phone updated the drone on the new nfz? I have auto updates turned off though so the app didn't update it must have done it in the background
Ok, that's what I figured. So yeah, it must be a parameter saved bird side, like RTH height, etc, which as we know is controlled by the app and independent of which device you use to connect. So in order to test the hypothesis you would need to:
1) Downgrade the FW on the bird to a previous version. I believe FW downgrades reset all previously stored parameters on the bird.
2) Keep the data connection turned off on your tablet. Since it's the only virgin copy of the Go app.
3) Try flying with your tablet and the downgraded firmware.
If the NFZ is smaller, we know what's going on.
To be super diligent, upgrade the bird's FW and try flying w/ the tablet again. If the NFZ is still smaller, then we're certain the Go app is phoning home.
I would bet that you are correct. DJI is being pro-active in the area of public safety. It's in their best interests not to piss off the authorities. One or two customers, yes. A regulatory body pressured by citizens incited by misleading news articles, no.Just a thought. Maybe its just DJI playing safe so they can avoid any issues from law enforcement agencies. I think the amount of NFZ will continue to spread in built up areas.
DJI doesn't use the Hover app to determine NFZs, so this tests nothing. The true test would be to fly before DJI adds the pope-zones to their map (assuming they do), and then immediately after, in order to determine whether NFZs are dynamic. An even truer test would be to do it w/ a live data connection, while someone w/ their data connection disabled does the same thing.Not sure if there is a Canadian equivalent of the Hover app, but if there is that may tell you what is going on.
Just now, after reading this post I opened up Hover and found that there are temporary flight restrictions over huge areas on the East coast of the US, that weren't there a few days ago... Possibly due to the Pope visit next week? Not sure if my Phantom knows about these restrictions but I can test. My workplace is within the huge restriction circle but my home is not, so maybe I'll bring the Phantom to work tomorrow and see if it'll fly or not. That should tell us if our apps are 'phoning home' via a web service or not.
I don't think you read my entire post. What do you mean it tests nothing?DJI doesn't use the Hover app to determine NFZs, so this tests nothing. The true test would be to fly before DJI adds the pope-zones to their map (assuming they do), and then immediately after, in order to determine whether NFZs are dynamic. An even truer test would be to do it w/ a live data connection, while someone w/ their data connection disabled does the same thing.
You'd be testing the NFZs appearing in the Hover app, which don't necessarily coincide w/ what DJI thinks are NFZs. DJI controls where you fly, not Hover. My suggestion was to determine if/when DJI adds the pope-zones to their list, and fly before/after with data off/on to see if NFZs are dynamic.I don't think you read my entire post. What do you mean it tests nothing?
I guess my point was that since Hover's NFZs are sourced from FAA data, one would think that if DJI is doing dynamic NFZs based on FAA restrictions they are probably pulling from the same data set. If that is the case, and if our Phantoms are checking for NFZ via the app calling home, then my Phantom should fly at my home but not at my office.You'd be testing the NFZs appearing in the Hover app, which don't necessarily coincide w/ what DJI thinks are NFZs. DJI controls where you fly, not Hover. My suggestion was to determine if/when DJI adds the pope-zones to their list, and fly before/after with data off/on to see if NFZs are dynamic.
Now I understand. And yes, assuming that's the case, I would think so too.I guess my point was that since Hover's NFZs are sourced from FAA data, one would think that if DJI is doing dynamic NFZs based on FAA restrictions they are probably pulling from the same data set. If that is the case, and if our Phantoms are checking for NFZ via the app calling home, then my Phantom should fly at my home but not at my office.
I dug a little deeper. Temporary restriction issued 9/10, effective 9/26 -9/28. "Temporary flight restrictions for Special Security Reasons". Restriction is 'from the surface up to and including 17999 ft...'Now I understand. And yes, assuming that's the case, I would think so too.
Ok, that's what I figured. So yeah, it must be a parameter saved bird side, like RTH height, etc, which as we know is controlled by the app and independent of which device you use to connect. So in order to test the hypothesis you would need to:
1) Downgrade the FW on the bird to a previous version. I believe FW downgrades reset all previously stored parameters on the bird.
2) Keep the data connection turned off on your tablet. Since it's the only virgin copy of the Go app.
3) Try flying with your tablet and the downgraded firmware.
If the NFZ is smaller, we know what's going on.
To be super diligent, upgrade the bird's FW and try flying w/ the tablet again. If the NFZ is still smaller, then we're certain the Go app is phoning home.
What Canadian city are you in? Is it possible there's a TFR/NOTAM for the federal leaders coming thru for the federal election campaign?