Saillogger Community

Nice, please share when done!

Hi @MacJL, that's an interesting case. Currently, there isn't a way to add it manually, but that shouldn't be necessary. If you check Saillogger about an hour after the engine starts running, the path should show up automatically. It will remain available even after the engine stops, as long as Signal K isn’t restarted.

Hi Michael, you can choose anything you like but Signal K reference actually recommends inside . You can see the reference guide here.

After you make a change to available data keys, it may take up-to an hour for Saillogger to recognize that change, as it requires retrieving updated metadata. Restarting Signal K can speed that up to about 5 minutes but it is not required.

We’re excited to announce a brand-new feature that lets you upload photos of your beautiful boat and specify its make and model!

Here’s what’s new:

Personalize Your Boat Profile
Upload a stunning photo of your vessel, whether it’s gliding through the water or docked at the marina.

️ Add Make and Model Details
Easily specify your boat’s make and model.

See It Everywhere
Your boat’s photo, make, and model will now appear in:

• Tracking views for a more personalized experience.
• Friends’ views, so your sailing companions can admire your vessel.
• Fleet views, making your boat stand out in shared adventures!

How to Use This Feature

• Go to the Boat Settings page.
• Upload your favorite photo of your boat.
• Fill in the make and model details.
• You're all set!
  Your updated profile will now be visible across tracking, friends, and fleet views!

Try It Now!
Add a personal touch to your Saillogger profile and let the world see your amazing boat. We can’t wait to see your uploads!

The Saillogger Team

Curious if i add these additional monitoring sources do they then become a part of my trip logs? This would be a complete game changer as I would have trip/log info on egt and coolant temps for reference.

The capability to integrate additional monitoring directly into trip logs is here with Plugin 4.0!

This major update allows you to capture custom NMEA 2000 data—like depth, battery levels, fuel levels, engine hours and more—seamlessly within your trip logs.

Check out the full announcement: Plugin 4.0: A Game-Changer for Saillogger!

We’re excited to unveil Saillogger Plugin 4.0, a groundbreaking update that redefines how you monitor, log, and manage your adventures on the water. This major release is a complete re-architecture of the plugin, designed to enhance your boating experience like never before.

What’s New in 4.0?

1️⃣ Re-Architected from the Ground Up
This version features a robust new core, optimized for performance and scalability. The revamped architecture ensures smoother operations and seamless integration with your existing setup.

2️⃣ Custom Monitoring, Tailored to You
In Plugin 3.0, you could already monitor custom NMEA 2000 data and add it to your dashboards. With 4.0, we’ve taken it a step further by seamlessly integrating these metrics into your trips. Now, every parameter you monitor—like depth, battery levels, and engine hours—will be automatically logged, giving you unlimited insights into your voyages.

3️⃣ Comprehensive Trip Logging
Plugin 4.0 ensures your custom monitoring metrics are not just displayed but captured throughout your trips. This means every journey comes with a detailed data history tailored to the parameters you choose. Analyze depth trends, fuel consumption, engine performance, and more to gain a deeper understanding of your vessel’s performance and optimize your adventures. Here is how it looks:

Why Upgrade?

Plugin 4.0 empowers you to:

• Stay informed with personalized dashboards.
• Log and analyze detailed data for every trip.
• Maintain your vessel proactively by tracking critical metrics.
• Ready to Explore?

Update to Plugin 4.0 today to transform your monitoring and logging experience. Let’s set sail toward smarter boating!

In order to update, go to the AppStore in Signal K dashboard on your monitoring device. If you are on a Victron GX series device, you can access it using this link when you are on your boat network.

As always, we’re here to help—drop your questions or feedback in the community forum.

Happy Saillogging!
The Saillogger Team

Hi Michael, I think it is there but since it is missing some data points the X axis is misaligned. It is a bug that we need to address but, but the graph will autocorrect itself when refrigerator sends enough data points.

Looks like there was indeed a problem with zoom. This has been addressed and a fix has been deployed. Thank you for bringing this to our attention.

Hi Jeremy,

This should work; we've just tested it. I suspect the issue might relate to how the customized Timelapse is being started. Could you try starting here: saillogger.com/timelapse/customize?

The Timelapse should display the same way in the recording as it does on-screen. However, please note that customizations you do on the map itself after the Timelapse has started (such as changing the base layer or zooming in) may not appear in the recording, that is expected.

Hi, unfortunately monitoring page is not customizable right now but we will file a feature request for this.

What were the timestamps for navigation.position? Timestamps are critical here. Signal K may display positions even if they aren’t being refreshed, but Saillogger will only use positions if they are actively refreshed. When you encounter an issue like this, please verify those timestamps.

Generally, there’s no technical reason why a GPS position in Signal K wouldn’t appear in Saillogger. Saillogger retrieves data directly from Signal K, so as long as the position is present and refreshing (refreshing is essential), it should definitely capture it.

Diagnosing the root cause is challenging by reviewing the log alone. This log confirms that no position reports were received, but understanding why requires local troubleshooting on Signal K. It’s almost certain that Saillogger did not receive position reports during this period.

As you point out, possible causes include hardware issues or overheating on the Raspberry Pi, especially if it lacks heat sinks. The Cerbo GX and Ekrano GX have undergone more extensive testing for this purpose and are expected to be more reliable.

When plugin debugging is enabled, additional details will appear in the Signal K server logs. However, these logs aren’t accessible from the cloud instance, so you’ll need to review them directly on Signal K. If you can share the logs here, we’d be happy to provide further insights. Be sure to collect them while the issue is occurring, and check the Signal K status page for any indicators, such as a static number of entries in the queue.

You can simply share the link to the log. For this problem though, troubleshooting may be necessary when you're underway and lack Internet connectivity.

The Saillogger plugin displays a status on the Signal K home page, showing information such as, "1 entry in the queue; last connection to the server was 8 minutes ago."

Entries in the queue represent data cached locally until an Internet connection is available. When the plugin is working and connected to the Internet, the number of entries in the queue remains low—typically below 2 or 3—as data is transferred to the cloud every couple of minutes, which is dynamically adjusted. If there’s no Internet connection, the count will gradually increase. This isn’t an issue; those entries will upload to the cloud as soon as the plugin detects connectivity.

However, if there’s no Internet connection and the entry count isn’t increasing, there may be an issue—possibly with GPS availability or readings from NMEA 2000 instruments. Enabling plugin debugging for Saillogger can provide insight into the issue.

Saillogger does indeed buffer data locally when there's no internet connectivity, and this feature is widely used by many of our users. Could you share a bit more about what you’re observing?

Regarding the second point, we use some dampening to filter out outliers. However, its effectiveness can vary depending on the number of outliers and the precision of the instruments. So, while it helps, it may not be entirely foolproof.

Ok, interesting. Thanks for documenting it. You may want to file an issue with that plugin, they should look into it.

Hi, what does Signal K data browser show navigation.position and what is the timestamp of that information?

@mshulman Unfortunately, that is by design for now. There are a couple of things that make it tricky. Units are shared across all values in a block, so displaying a 38 F and 32% in the same block becomes fairly complicated, both for conversions that need to take place (i.e. SK uses kelvin behind the scenes) and the display on the page. That is the reason blocks share a single unit at this point.

@Brazen-Article , that can be done but requires some thinking. We will file a feature for backlog.

Hi, the heading discrepancy you're seeing is likely due to the difference between navigation.headingTrue and navigation.courseOverGroundTrue as reported by Signal K. Monitoring and trip logging can use either value based on specific logic. Could you compare these two readings and check if they diverge? Assuming they do, check the sources they come from, there is probably a misconfigured device on the NMEA network.

As for speed, it should be synchronized. When reviewing your last log, we didn't observe the boat speed dropping to zero, although the wind speed was zero. Could you provide an example of a log where the boat speed reads zero? Both monitoring and trip logging rely on the same data keys for this, so there isn’t an apparent reason for them to differ.

Functionality including access to logs and stats is paused with a seasonal subscription pause.

Those two pending transactions indeed finally did clear. Since you got charged multiple times now, we refunded those two payments. It may take a couple of days to show up on your balance, let us know if they don't.