So My 2 XSP's are both ignoring any Go Home altitude I set. I think it a general firmware issue as I've heard numerous similar comments.
NOW - here's the 98ft issue as noted from Autel
IMPORTANT: For safety reasons, if the aircraft is hovering at an altitude lower than 30 meters when the Go Home function is activated, it will ascend to an altitude of 30 meters above the home point before starting to return home.
First of all, it's important to remember that all heights are relative to your take off point which is 0ft.
If you are flying at 60ft and press the Go Home button, the drone will climb to 30 meterss (98ft) and go home. It doesn't matter what your Go Home Altitude is set at (so it seems). This later point is a design flaw in my option, an arguement I am having with Autel currently.
So flying lower than 100ft limits you to go home at roughly that same altitude unless you manually fly higher. Hence, the Go Home feature is useless and in fact, could loose your drone.
There seem to be a number of issues here:
- The above statement from Autel explaining why 98ft (30 meters is 98ft)
- The Go Home Altitudes don't work (at least from 5 XSP's I'm aware of)
- There's a caviate to all of this. The Go Home feature won't initiate at all if your not further than 50 ft from the home point. Again, this is common to all 5 XSP's I tested. If you go out 40 ft (from the home point,for example) and initiate the Go Home feature, you drone will simply crash and burn. Just kidding. But rather than "Go Home", it simply descends and lands. Exactly where it's at at the moment. This could be a problem if your not paying attention.
Personally, I think the XSP should climb to the prescribed altitude as defined in the settings and "Go Home". End of story.
I always manually fly my bird and honestly, haven't really used the Go Home feature until recently.
Ok, I could be full of **** and have been flying at altitude without oxygen for too long. But that's my story and I'm sticking to it until someone proves me wrong. Please do
It's true you may be stuck in the IOS bug issue, but I'n not even using a FPV device IOS or otherwise for these tests.
Let me know if that explains your XSP's behavior or not. If so, your number 6