Please describe in detail, your antenna setup, min speed setting, fix to fix setting.
Let me guess, a single F9P with the wonderful “feature” that stops sending speed information when it senses it isn’t moving…
At which point AOG no longer gets speed updates, so it waits till your F9P starts sending info again.
Ardusimple F9P
Fix to fix and min speed as initial download. 1m and 1K i think.
It’s never done it before apart from WAY back in a much earlier version.
See what the problem is?
It wasn’t a problem with 4.3.10. Never. GPS speed was always roughly right.
Well of course. But, this one doesn’t fix your problematic GPS…
If your gps stops sending speed, what is AOG to do?
No idea. I was just reporting what appeared to be a slight issue.
Yes, an issue with your gps…
…an issue for a lot of us then?
Just the ones who have not configured their gps properly.
It’s got Andreas’s setup on it. Not sure if it’s his very latest.
Something to look into. Please post back what you find out - if it is not fixable, let me know.
Do you have check in Permit COG?
Thank you @Kaupoi .
I’ll check the present setting first to see what is possibly wrong.
FW could be 1.12 on that machine so I’ll update that too.
I assume you are referring to what I was reporting earlier, but I think there might be a misunderstanding so I’ll try to explain the situation more clearly.
When speed gets low, some receivers (like Emlid) stop sending heading as part of VTG. That is clearly intentional, at very low speeds heading is unreliable and the standard says that if data is not available the field should remain empty. So when standing still the message is something like
"$GPVTG,,T,,M,0.01,N,0.02,K,D"
Now in AOG (v4 source code which is available) the conditions to interpret VTG (ParseVTG() ) at all is
if (!String.IsNullOrEmpty(words[1]) && !String.IsNullOrEmpty(words[5]))
{
//kph for speed - knots read
double.TryParse(words[5], NumberStyles.Float, CultureInfo.InvariantCulture, out speed);
speed = Math.Round(speed * 1.852, 1);
//True heading
double.TryParse(words[1], NumberStyles.Float, CultureInfo.InvariantCulture, out headingTrue);
}
which means that whenever the heading field is empty, the whole message is ignored. I think it could be safely replaced with something like
if (!String.IsNullOrEmpty(words[1]))
{
//True heading
double.TryParse(words[1], NumberStyles.Float, CultureInfo.InvariantCulture, out headingTrue);
}
//parse speed if available (why not take kmh directly?)
if (!String.IsNullOrEmpty(words[5]))
{
//kph for speed - knots read
double.TryParse(words[5], NumberStyles.Float, CultureInfo.InvariantCulture, out speed);
speed = Math.Round(speed * 1.852, 1);
}
This way, the speed would get updated even if the heading is missing. Earlier when RMC was also used this problem wasn’t showing, as RMC also contains speed.
I hope this clarifies the case a bit.
Maybe this helps?
https://www.u-blox.com/sites/default/files/ZED-F9P_IntegrationManual_(UBX-18010802).pdf
See page 23 “3.1.7.3 Navigation output filters”.
No. It is as in the screenshot you posted.
That still wouldn’t fix Allen’s problem. You can plainly see the speed is 1kmh, standing still, and the heading is valid - although it is spinning around.
What standard says the speed and heading need to turn off when going slow???
But, that is a good point to check each word separately. I will do that
Do you not just need to move at least the first fix - fix distance? So AOG will resister the first GPS heading