Saillogger Community

Hello John, That’s a good catch, I’m not the developer but I’m assuming that that was the most intuitive direction when he developed it. I’m guessing he’ll comment on this if need be. Thanks, Kevin.

@admin

Thank you for the magic. I have now activated the Windy reporting option and will monitor the data on Windy to confirm all is as expected.

Cheers, Bill on SV Denali Rose

Thanks for hoping on it and deploying a fix so quickly. Behavior looks correct now. 😉

Thanks! Will do that.

Thank you very much. Sadly we moved since Saillogger went down and I updated it. The .GPX track was to fill in our transit from when it went down and our new location where I brought it back up. Not the end of the world. Glad to have our beloved Saillogger back up and running!

Hi Brian, replied over e-mail but I suspect Venus 3.63 upgrade will not help as Signal K configuration is persisted across upgrades. There is no harm to try though.

Glad to hear you sorted it out! For future reference, it may take up to an hour for new data keys to show up in Saillogger. This is only applicable for the initial configuration, once done data flows in regular one minute intervals.

@admin Thank you for the work!!!

This was resolved in a different thread. Upgrading to the latest Victron firmware and installing Saillogger plugin 4.2.1 or later will work.

Hmm, spotty access point should not cause this. It is almost always due to GPS. Please keep monitoring and let us know if you observe anything else that is unusual.

@jonnys , we have been investigating this and it turns out this is an issue in the latest version of VenusOS v3.62, please see the following post for details and potential workarounds:

Link Preview Image FIXED: Saillogger plugin fails to install on Venus OS v3.62

IMPORTANT NOTE: This issue has been resolved in Saillogger Signal K plugin version 4.2.1. In collaboration with Victron, we identified the root cause and fix...

favicon

Saillogger Community (community.saillogger.com)

Thank you for sharing this Alastair.

It looks correct, we plan for more improvements for this logbook, so stay tuned.

Ok, please try two things:

Check the interface name on Signal K for the CAN interface, if it is can0 or vecan0, please try vecan1. Make sure to restart it after you make a change. See if you can connect it to first port (even temporarily) and if it makes any difference.

Independently, the first port is galvanically isolated, the second one is not. For NMEA connection, Victron's strong recommendation is to use the first port.

Is Victron GX connected to NMEA 2000? You need a special cable for that (you could also make your own, see this article)

If you verified the connection, make sure your GPS source is turned on (it might be the chartplotter).

When everything is working you should be able to go to Signal K Data Browser and search for navigation.position and it should show your current position.

If you haven't already, do check this tutorial, it explains though:

One more thought, please make sure the times on Cerbo GX and your Chartplotter are in sync and set to the same timezone (including daylight savings). If there is a time mismatch between the two, it could lead to problems like this.

Hi @SV-UNSInn there was a bug with RPMs, we just fixed it. It should work now.

We also added a new type of "Duration", which will convert seconds to hours. You can use it for engine hours.

Happy Saillogging!

Unfortunately this is an annoying Signal K bug. AIS data may override the boat name in some edge cases. It happens more frequently if you happen to have a DataHub but we have seen it happening without a DataHub too.

Signal K team has been working on a fix, here is a link to the tracker: https://github.com/SignalK/signalk-server/pull/1833

In the meantime, restarting Signal K should solve it.