Saillogger Community

admin

We're thrilled to introduce the Printable Logbook View, a beautifully organized way to relive, document, and share your boating adventures! This feature is thoughtfully designed for both digital viewing and high-quality physical printing.

Key Features:

Chronological Order: Your journey unfolds clearly from the oldest entry to the newest.
Stunning Full-width Photos: Enjoy your boating memories in crisp, vibrant detail.
Optimized for Printing: Carefully formatted for seamless viewing on screens and paper.
Detailed Locations: Every entry includes precise coordinates for accurate reference.
Distinct Entry Types: Easily differentiate between moorage points and trackpoints.
One-Click Printing: Conveniently print your logbook entries directly from the page.

How to Access:

You can explore the new Printable Logbook feature via:

Printable Logbook under More menu
Direct link: Printable Logbook (Please make sure you are logged in)

Tips for Best Results:

Printing: Select landscape mode for the optimal photo arrangement.
Use the Web App: Mobile devices are not always optimized for printing. Try using the web interface to print.
Digital Viewing: Click photos to expand and enjoy greater detail.
Comprehensive Entries: All your notes and photos automatically included.
Organized View: Entries neatly grouped by location and type.

We hope this enhanced view enriches your boating documentation and makes sharing your adventures even more enjoyable. We look forward to your feedback—please share your thoughts below!

admin

That's interesting but activity is pretty low for NMEA 2000. For reference, check our setup: Screenshot 2025-05-26 at 8.12.29 AM.png . You should easily see 8-10x of the activity you are seeing, so something looks off.

If you see tank levels coming from NMEA 2000, it means at least some part of it is working though. Looks like you have an Ekrano, and connection is at the first port, is that correct? Where does it connect to on the NMEA backbone? Is there a terminator on the Ekrano?

admin

Hi @Kokomo , I think there is an issue with the NMEA 2000 connection from your Victron GX. You do get GPS coordinates but they seem to be coming from a different port and nothing else from NMEA 2000 comes over.

Please check the cable, connection and any errors you may see on the summary page. Also the summary page should have a yellow bar indicator, it should show the NMEA 2000 activity, it definitely should have some visible activity if the connection is up.

admin

Hi, thank you for the note. I wonder if these are PGNs not recognized by Signal K. But it sounds like too many things are not recognized which doesn't sound normal. What kind of data can you see from NMEA 2000?

Related to that, can you search navigation.position and environment in Data Browser and send a screenshot of those as well the Summary screen of Signal K?

admin

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:

admin

Try it again by stopping Signal K first and then delete the directory. Basically repeat the entire process from scratch.

You do not need to change the firmware again, you should already have the large image. Just toggle off Signal K, delete the directory and toggle it back on. It will bring a fresh install from the already loaded large firmware.

Signal K plugin is the Saillogger Signal K plugin. Essentially get a clean Signal K install and follow the step-by-step instructions Saillogger gives you in Getting Started Guide. This video tutorial may also be helpful.

admin

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.

admin

Hi @svcatalyst, it looks like your Signal K got corrupted. Best option is to reinstall it from scratch in a clean way but it will require root access to Cerbo GX. Instructions are here but please read the warnings carefully and proceed at your own risk.

If you would like to do that, please follow these steps after obtaining root access:

Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
SSH into Venus OS
Delete the Signal K directory by issuing the command rm -rf /data/conf/signalk
Exit ssh by exit or closing the terminal
Start Signal K process

This will give you a fresh, brand new Signal K instance. You will need to download the Signal K plugin again and configure it. Make sure you wait long enough for installing the plugin and do not interrupt it. It can take longer than 30 minutes. Interrupting it can corrupt your Signal K again.

Let us know how it goes.

admin

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!

admin

Hi, glad it sorted itself out; nothing has changed on the server side.

Here’s what I think happened:

Saillogger waits for an hour after a trip is completed to confirm it’s truly finished in case the boat starts moving again.
At the end of that hour, Saillogger needs at least one more position update to verify the boat hasn’t moved.
If the boat’s electronics are turned off during that hour, completion will occur the next time they’re turned on.
In the example you sent, the boat stopped reporting positions—likely right after the trip ended. That’s why we suggested turning all electronics back on for a while, which resolved the problem.
Somewhere in this process in your case, the position reports seem to have arrived out of order. We’re not sure why—this might be a bug, though we haven’t seen it before. I’m confident that keeping the instruments on for at least 10–15 minutes after arriving will prevent this. We’ll keep investigating to see if we can reproduce the issue or find a logical explanation; so far, we haven’t seen it happen outside this case.

Taking a step back, please keep your instruments on for at least 10 minutes after arrival and let us know if the problem occurs again.

Thanks,

Ilker

Saillogger Community

administrators

Posts

Key Features:

How to Access:

Tips for Best Results:

Member List