If you do have an fpv drone and you haven’t updated the fly safe database don’t, do it a minute hold back, because people who have tried to update over the last couple of days have ended up with a bricked aircraft and they have not been able to Fly now just to explain this issue in a little bit more detail. People over the last few days have been getting prompts to update the fly safe database on their fpv drone. Now, if you don’t know what the flysafe database is, it is the information within the drone that locates all of the nfcs the no fly zones, and it tells the drone where you’re allowed to fly and where you’re not allowed to fly now. Dji have this on pretty much all of their drones and they update it periodically to make sure that you have the latest info in your drone. We, the dji, fly, safe, databases are located and where the zones are located and if there are new ones added or some taken away. Now it seems people since about the 7th of may started to get prompts to update their flysafe database either in assistant 2 and the vision of assistant 2 at the time was version 2.1.0 or via the fly app and after doing that, update their aircraft was blocked. From taking off and they were receiving a fly, safe database error in their goggles now, since then, dji have quietly pushed out an update to assistant 2, which is now version 2.
1.1. That seems to have resolved that issue because i actually updated mine on the new version of assistant and it has gone through absolutely fine. However, i wouldn’t advise updating a second and i’ll talk about that, a little bit more in a minute. Now, if we just jump over to the dji forum, there is a post on this that has been put together and people first of all started to see this issue around the 7th of may and what, as i said, they’re getting is fly safe database error in Their goggles so they’re getting this error down here and they’re being prevented from taking off now. Some people have found a way around it by actually blocking the gps, but for the most part there’s a fly safe database error. You cannot fly at all now. People have tried pretty much everything they can to get around. This they’ve tried refreshing. The firmware. They’Ve tried reloading the database, but nothing has resolved it at this time. They remain in a situation where their drone is stuck and they’re not actually able to fly. Now, as i mentioned just now, dji have quietly pushed out a new version of assistant 2.. When you go to their website. It still says the latest version is version 2.1.0. However, if you try to update today, you should receive a prompt that looks like this one here that asks you to update your assistant to the latest version for the new fly safe database, and i actually did this tonight and i ended up with vision 2.
1.1. When i did this, it also updated the database in my fpv drone and mine has updated absolutely fine and i’ve been given no problems at all. However, other people are not in this position and they are still blocked from flying now. Right now, there has been no real fix for the people who have this problem. Dji have been posting on their forum and taking logs from people, but those who have had their fpv drone locked out don’t seem to have found a fix for this. At the moment. It does seem from my own experience that if you update today with the latest assistant on pc or mac, which is version 2.11, it updates fine and it doesn’t give any problems. However, i wouldn’t be a hundred percent on that, and my personal advice right now is not to update now. What i think has happened here is dji, have pushed out an update for the fly safe database that had either corruption in it or it wasn’t suitable for the vision of the assistant and the apps. People were using and it ended up damaging the fly safe database. In the drone we have seen this happen in the past, then, as a safety feature, the drone prevents you from taking off and you’re not able to fly now. Hopefully, dji will be able to push out a fix for these users via firmware to allow them to be able to fly. However, that hasn’t happened as of today.
All they have actually done is taken feedback and quietly pushed out. The update to assistant 2, which i suspect, solves the issue from happening to people who haven’t updated yet, but doesn’t fix the issue for those who have. As for what the situation is moving forward right now, we simply don’t know those who are stuck remain stuck and we’re waiting for dji to resolve it. Hopefully this isn’t fundamental and it should be able to be fixed via a software update, hopefully that they’ll push out in the near future. But if you do have a bricked fpv drone, i would suggest opening a ticket with dji now and getting that process started. Just in case, we don’t see a fix in the next couple of days as for time scales with how long dji can take to fix these kind of things. It is how long is a length of string. We have seen issues like this resolved in one to two days before and we’ve seen. Issues like this still be there one to two months later. The fact that they have pushed out quietly and an update for the assistant too, does tell you that they are aware of this one and hopefully for the users stuck. They will get an update out shortly to be able to fix it. This is the first issue that we have seen with dji, and it is our uh. The dji fpv drone, i should say – and it is ironic – is a result of one of their nfc database updates um.
Hopefully, though, we should get a fix for this in the near future if you haven’t updated, yet the safest position to be in right now is ignore it. If you get prompts on your phone via the goggles or you get prompt and assistant don’t, do it here and now wait and see what happens and then hopefully, they’ll have a fix for the existing users in the near future. Now that is it for this one? It was just a quick update, as i said, it’s been developing over the last couple of days. I had been tracking it, but it’s got to the stage now where people are talking about it, and i had a user message me to say: look we’re stuck here. Is there anything anyone can do so? I thought i’d put the video out on it and put a warning out on this one.