Yes this is exactly why I tried the indoor mode
, unfortunately even when not in indoor mode it’s the same. What I can’t recall now is if the error appears before the gps lock or after, the h520 always said something too before full gps was acquired
Since you are using the same controller and getting the same results on different drones it might be a good idea to do a factory reset of the controller to see if any stray settings from the previous version can be cleared.
Yes I have a few of these, I tried the others to update the camera
This is what I get, I add my 16 , not the one in the picture but 3 more and it says it must be 20 characters. When I add 20 it says 17th must be a certain type of character that the controllers keyboard doesn’t have . If I try a different character like € it won’t take it, it only seems to take numbers and letters
Yes so I tried 3 different controllers and they all give this error. So what I noticed is it will indeed give the NFZ error before the gps has acquired the adequate lock or just directly before it. after u delete the error list and the lock is achieved the error never reappears, it also says the beloved gps cross drift too hight
, it might just be a quirk in the software, I’m surprised the coding for the software for all these models don’t allow the gps lock first before suggesting the gps cross error message, without the lock it it shouldn’t arm anyway unless u turn off the gps for indoor mode ect or it least that the way it should be, there must be some logical thinking around it . I’ll for now just ignore the message and try resolving the blinking green lights. Next I’ll try adding the operator id to see will this resolve that
Yea there is , along with compass and gyroscope I think, there is 3 anyway and they all complete with a
beside them
