Saillogger Community

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

No, you cannot do it easily without going to CLI

Can you upgrade to 3.62 and try again?

@Andrea this should just work without problems with plugin 4.2.1, did you encounter any issues?

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.

You can definitely delete them, click on the log name and you see a "delete log" option at the bottom of the information panel on the left.

Question is, why these come up though? Is there an erratic GPS on the boat?

@jonnys This issue has been resolved in Saillogger Signal K plugin version 4.2.1. In collaboration with Victron, we fixed it by rebuilding the dependency in a different way. Please install Signal K Saillogger plugin version 4.2.1 and let us see if you see any issues.

Thanks, @Gerler. It turns out the problem is specific to the latest Venus OS (v3.62). Appreciate you uncovering the workaround! We’re coordinating with Victron on a permanent fix. In the meantime, we’ve posted the details here:

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...

Saillogger Community (community.saillogger.com)

@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:

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...

Saillogger Community (community.saillogger.com)

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 fixed it by rebuilding the dependency. Please install Signal K Saillogger plugin version 4.2.1 or later.

The latest Victron Venus OS release (v3.62) misses a critical package that prevents the Saillogger plugin from installing in Signal K (see attached screenshot).

We’re working with Victron on a fix. In the meantime, please use one of these workarounds:

1. If you haven’t upgraded yet: hold off on updating to v3.62 until the issue is resolved. We’ll post an update as soon as a fix is available.
2. If you’re already on v3.62: downgrade to a previous version. On the Victron GX display go to Settings → Firmware → Stored Backup Firmware and choose an older release.
3. If downgrading isn’t possible: install the missing package via SSH:
3.1 Enable SSH access by following these instructions and ssh to your Victron GX device using a terminal.
3.2 Run /opt/victronenergy/swupdate-scripts/remount-rw.sh to remount the filesystem read-write.
3.3 Execute opkg update, then opkg install python3-pip
3.4 Exit the terminal and install the Saillogger plugin normally.

We apologize for the inconvenience and thank @Gerler for identifying the workaround in step 3.

This post will be updated once the fix is released in Venus OS.

@jonnys apologies, the link did not come in the previous e-mail. Here is the link that has the instructions: https://community.saillogger.com/topic/111/new-install-wont-start/2?_=1750903944520

Please try them and let us know if your issue persists.

Hi @jonnys could you try the instructions on this post, specifically to SSH into the device and delete the Signal K directory?

Please let us know if that changes anything.

Thank you for sharing this Alastair.

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

Hi Otto, you need to define a cruise by setting a start log.

Go to monitoring settings and set initial tracking position, then try the printable logbook again.

Let us know if you encounter any issues.

Ok, glad it is solved but this is super awkward, Saillogger plugin has absolutely nothing to do with Python. There must be something else happening in the system, but not sure what it might have been.

That's odd, what is the error message you are seeing?

Ok, please try two things:

1. 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.
2. 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.

Hi @Gerler , you can create a fresh installation of Signal K using SSH. Please see this thread for more details.

Hi Alastair, looks like your Signal K plugin installation got corrupted. Could you try uninstalling and re-installing the Saillogger Signal K plugin? Please do restart Signal K after uninstalling and after re-installing it.