Good morning, I don't know if it's in this community, but I would like some help from anyone who can. I installed a GPS on the drone and it has a problem with the difference in flight direction and distance. Can anyone tell me what it could be?
#GPS WITH POSITION ERROR
cloud carbon
rocky plaza
more info please
cloud carbon
more info please
There is not much information, I installed a BE122 everything is working fine, but the home point direction arrow is pointing in the wrong direction, and when I press go to home it lands in a different place from where it took off, on average about 30 meters. I couldn't find a way to fix this.
rocky plaza
Are you allowing arming without home point?
Did you wire up a magnetometer as well?
Before you take off, how close to zero is the indicated speed? How stable are the GPS values if you show them in the OSD? How many sats before you take off? Lots of basic things to know.
cloud carbon
It is configured to arm without satellite, but in the configuration I put minimum 6 and I expect connection of 6, not iso magnetometer, the distance and height information is only reset when it is activated and takeoff. I left the barometer, acceleration and rotation turned on in the settings.
rocky plaza
With only 6 sats the home point may well not be accurately determined.
If you connect your quad to a laptop and look in Configurator at the map, it will should the perceived location of the quad on the map.
You will notice that with only 6 sats there is sometimes a good fix, that changes not so much by the time you have 14.
Other times, with 6 sats, they are in poor alignment, and both altitude and position drift many metres from the values when you had 6.
Even 8 is a bit of a compromise, sometimes the home point will drift for perhaps 10m from takeoff with 8.
You can display pDOP in the goggles, and only when that value is low is the accuracy good.
Anyway I think it is best to read the gps rescue wiki, which explains how the arrow is set and how we attempt to determine the current direction of travel of the quad, in order to set the home arrow.
Definitely check that your hover is stable and does not drift, if it does, re-calibrate it using sticks at the field, until the hover is flat and stable.
Now if it turns out that your home point is well defined, and stable, but the quad returns to a very different location, you can observe in the OSD the distance to home when it lands.
If the OSD says that it lands 2m from home, but you notice that in reality it is 20m away from home, then the GPS code worked properly, and landed 2m from home, but there was a change in the home estimate because of GPS drift.
If on the other hand the OSD says that it landed 20m from home, and it did land 20m from home, then there is a problem with the rescue, and you can debug that by logging the various parameters to see if it follows speed and altitude properly or not.
You should probably test waiting until 14 or better still 20 sats. Then check the behaviour.