Saillogger Community

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!

That's interesting but activity is pretty low for NMEA 2000. For reference, check our setup:. 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?

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.

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?

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:

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.

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

1. Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
2. SSH into Venus OS
3. Delete the Signal K directory by issuing the command rm -rf /data/conf/signalk
4. Exit ssh by exit or closing the terminal
5. 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.

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!

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

Here’s what I think happened:

1. Saillogger waits for an hour after a trip is completed to confirm it’s truly finished in case the boat starts moving again.
2. At the end of that hour, Saillogger needs at least one more position update to verify the boat hasn’t moved.
3. 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.
4. 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

Hi there, welcome to Saillogger and glad you are enjoying it!

For RPM, when you are adding a custom configuration block, make sure to choose RPM in the Data Type. It should look like this:

In regards to your second question, wondering if there is a typo there:

The motorboats are displayed seconds

Could you elaborate on this? What data type are you monitoring?

Hi there, there is a difference between being online and reporting and having positions. Position is a requirement for the rest and it is not sent to the server right now. The updated time (April 26th) shows the last time a position report was received. I am pretty sure what you are observing is related to that.

Several reasons why position reports might not be coming along:

1. Internet connection is down (doesn't seem to be the case)
2. GPS source on NMEA 2000 is not currently on. Note that if you don't have a dedicated GPS or an AIS transceiver, the mostly likely GPS source is the chart plotter. If it is off, this could explain it.
3. You might have mistakenly entered a GPS source in your Saillogger plugin settings in Signal K. If there is an entry, and misconfigured it might be blocking GPS positions. This is explained in question 13 of support articles in more detail.

Most likely reason is (2) above. Please test it by turning on all your boat electronics and chart plotter and make sure Internet connection is available, then wait 10 minutes. Last updated field in Saillogger should reflect something like "Updated 10 seconds ago". When you see that you can turn your instruments off.

Let us know what you find.

Thank you for your post. I suspect this has something to do with the order of the data that came in. I see no reports have been received since April 26th, turning the instruments and Internet for 5 minutes will likely solve this problem. Could you please try it and report back?

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.

You can certainly use them with custom monitoring, anything in NMEA2k/Signal K can be monitored with Saillogger.

That said, we are working on a much more integrated experience (imagine engine hours being part of your trip logs by default), but it is probably a couple of months out. First we need to install one on our boat and that will probably happen around June.

Hi Otto,

This is a bit strange, as long as there is a single active monitoring device, where the data is sourced should not matter.

Can you check a few things:

1. First ensure that there is no older device or something else configured with the same collector ID. Multiple devices sending data simultaneously will cause problems.
2. Reboot the Raspberry Pi if you haven't already and wait for 15 minutes to see if the labels in Saillogger or data is changing. Try to reconfigure the monitoring parameters on Saillogger at this point.
3. If still doesn't work, it would help to delete the local cache on Signal K. It is unlikely but it might have been corrupted in a hard reset. Here is how it should look like on Venus OS (I haven't tried this on a Raspberry Pi running Venus OS but should be similar)

• Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
• SSH into Venus OS
• Delete the local cache by /data/conf/signalk/plugin-config-data/signalk-saillogger/saillogger_v2.sqlite3
• Start Signal K process

4. If it is still not working, the best is to reinstall Signal K from scratch, here is how it would look like on Venus OS (I haven't tried this on a Raspberry Pi running Venus OS but should be similar):

• 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 rm -rf /data/conf/signalk
• Start Signal K process
• You will need to download the Signal K plugin again and configure it.

Note that options 3 and 4 can be dangerous in that they may corrupt Venus OS and/or Signal K.

Good luck and keep us posted on what you find.

Hi Jim, yes you can change it per Stay. There is default stay type for a given moorage and it is assigned to all stays there but then you can go ahead and customize each stay as you wish. Go to https://saillogger.com/stays/ and adjust the "Stayed At" drop-down as needed.

Here is an example of how additional data is captured per trip, from our logbook:

This will show up for you the next time you complete a trip, based on custom monitoring data you have added.

Curious if there is a confusion. In regards to wind average/max and SOG average/max, they are already part of each trip log. Here is an example:

Bottom two sections have those.

When you add additional monitoring data, minimum and maximum of those values will also be captured and displayed per log (under a section called Additional Data). Average is a bit more contextual and only makes sense for few types, so these are minimum and maximum right now.

Strangely COG, TWD and AWA are displayed as knots.

You should use the same unit per monitoring block and choose the monitoring type accordingly. So instead of a single "Sailing Performance Data", you could have multiple blocks. All values in a single block will share the same unit.