SOG 0.3kts but I am not moving!

[MHTinkler]

GPS recievers are subject to accuracy error. Generaly around a meter or so (if it is a good quality receiver and has a clear view of the sky). So your charting software is trying to interpret a constantly changing data stream it simply intetprets as motion. When actually in motion, it does a great job, when not it is really kinda guessing.

[LifePart2]

Thanks Dave.

Actually I was seeing that error on Windows. However, it is only apparent when one is stopped, and most people are not looking at their chart plotter when they are stopped, so would not notice it. Also, it is hardly a critical error in real life. I only just noticed it, and I guess it has been there for quite a while already.

Anyway we got there in the end. Yes, I would be happy to run the Beta - how do I get to that? Last time I looked it said that the Beta was not available.

Now, the bigger problem for me, in real life, is the freeze up every time I zoom in to a new location. A problem as that is when I am arriving at some destination and want to look more closely at the surroundings - and then the thing freezes up just as I am getting there. This one is, indeed, on RPI only. Today I will play around with going back to the old oeRNC plugin instead of the new o-charts just to see if that is a factor.

Any suggestions on this one?

[bdbcat]

Noel...
Please start a new thread for any other problems. We sort and prioritize work by thread title, and "SOG 0.3" is soon to be solved.


Thanks
Dave

[bdbcat]

Noel...
The current Beta "5.6.1-1" still has the "SOG 0.3" problem. Will be fixed in 5.6.1-2, coming in a week or so.


Please stand by
Dave

[Hakan]

Noel..
For info I've tested Dave's change and while playing your VDR file COG and SOG are now only shown in OCPN the second(s) when both are received from your GPS receiver. Looks good!

[Carryonsailing]

We have had the exact same problem with this and are using the navico sensors. We found that overheating really affects the sensitivity of the sensors. On my VHF from BandG the error was display, however the same error is not displayed off the data stream from the Actisense and into opencpn. Probably something to do which sensor the BandG uses for GPS.
Hope this helps.