So the config is hoover on 1210 , checked with Blackbox, and this are out BF settings.
So when we activate RTH, drone goes up all the time, and not coming back
We tested without fixed altitude and with, this is our CLI
1 messages · Page 1 of 1 (latest)
So the config is hoover on 1210 , checked with Blackbox, and this are out BF settings.
So when we activate RTH, drone goes up all the time, and not coming back
We tested without fixed altitude and with, this is our CLI
We have arround 22 sats, so that's stable.
We have 3 drones with same issue, all use M10 gps
Foxeer H7 MPU6000
Fetec ESC
If this is reproducable please mention it in #bug-reports
You’re the only person in the world with this issue.
What do you mean, “we”?
Test it at close range, set it to return at current altitude, and ensure all gps settings are at defaults. Do not enable arm without fix.
We means 4 people in our team today. Also tested stock, only changed hoover throttle
@compact hamlet if we are the only person, does not mean there is no bug
And we only fly when we have at least 10 sats. So enable arm without fix is not a issue
Sats and fix, osd stops blinked means lock.
Gps vertical or horizontal how much is that a problem? We still get in both options 22 sats easy
No baro
Close range we also tested maby 60 meters away our something. Same issue
Btw this is on ZULU Firmware
BF 4.5 ZULU RTH not coming back
Same issue was also on rc2
Video showing what happend
https://www.dropbox.com/scl/fi/4l3hivagnnbk02twi4okk/gps-rth-bf-4.5-zulu.mov?rlkey=fubh9bucg1xw5y6q560n1pllg&dl=0
make sure that your baudrate for gps is 57600
It is set to auto, m10 is 115700
you should try 57600 not 115200
change to 57600
Double checked it was already on 57600
#bug-reports is the disccusion
I can confirm lots of users having no issues with 4.2 GPS Rescue so something is fishy with these setups.
Now u answer also in 2 discussions 😉
yeah but you started it lol
besides, it wasn't a bug 🙂
so we should not be discussing it there.
the bounce on landing was because it was very soft. most likely there is a significant ground effect. if you make it descend a bit faster, and perhaps lower the disarm threshold, it will get more reliable at disarming. However lowering the disarm threshold on noisy or shaky builds will sometimes disarm early.
Then we don't change that, still weird what is the issue. Could it be the check for arming without sats even we have sats and lock?