Logs all seem to start about 30 minutes before we are underway

[Sparohok]

Saillogger is awesome, started using it this summer and I'm loving it. Having said that, on to the quibbles!

I'm not sure if this is normal or something unique about my setup. All my logs seem to start about 30 minutes before we actually weigh anchor, with a bunch of floating around the anchor at 0.2 knots or whatever As a result the duration is longer and average speed lower than expected.

The only thing I can think of that's unusual about my setup is that I have a USB GPS connected to Cerbo GX so my Signal K will have a boat position all the time, even when the boat instruments are turned off. Could that be causing this issue?

Anyway, thanks for the app, its great!

[admin]

Hi @Sparohok, thank you.

This is definitely unusual, Saillogger normally eliminates all those starting points automatically and works without any issues. You’re clearly observing something different.
Having a position all the time is actually a good thing, so that won’t cause the issue, but I suspect it has something to do with that USB GPS.

I presume you have a GPS source on your NMEA network (chartplotter, AIS, etc.) that comes online before you start moving. If so, can you configure a priority so that your USB GPS is always the lowest priority and only used when nothing else is available?

Go to Signal K → Server → Data Connections and, using the Priorities table at the bottom, configure priority for your navigation.position and give higher priority to NMEA sources (make sure your instruments are on while you do this). Put the USB GPS at the bottom, and set a timeout of 5 or 10 seconds.

It will look something like this:

Make sure you restart Signal K afterwards and let us know what happens on your next trip.

[Sparohok]

@admin thanks for the feedback, great info. However I am still seeing the same behavior, tracks have 30 idle minutes before we set out on our trip. I set the priorities with n2k_on_ve.can_socket.* above the USB GPS which is venus.com.victronenergy.gps.ve_ttyACM0 and restarted the Signal K server. Any other suggestions?

[jimholthaus]

If the USB GPS is always (or almost always) available, I'd try making it the highest priority.

[admin]

Hi @Sparohok , @jimholthaus 's suggestion is a good one. Please try it.

Beyond that, the behavior is definitely not normal. We will need to simulate your account here and run some tests. I will see what we can do about it but please try the above suggestion first.