Saillogger Community

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?

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.

Yes, perfect!

Hi,
thanks for your immediate response ... highly appreciated. When reading your advice, it popped up that I already had once the same problem and it was and still is hökens-anchor-alarm https://www.npmjs.com/package/hoekens-anchor-alarm after deleting the anchor-alarm everything is back to normal. Thank you.

Perfect. Thanks!

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

Screenshot 2025-02-25 at 5.04.16 PM.png

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

Thank you so much.
I'll try that.

OK thank you it's work perfectly !!! Very nice ...

Awesome thanks

Makes sense. I think we just won't recommend that particular sensor, since it's refresh rate is r fast enough for monitoring.

I'm really excited to have SailLogger on the boat. That you for making it available.

Hi Bill,

Actually, you didn’t miss it. We do have the capability to import GPX files, but this option isn’t available in the UI for several reasons:

Granular Data Requirements: Importing GPX files can be tricky because Saillogger requires granular data logging. Not every GPX capture provides the necessary detail, which may lead to inaccurate identification of trips and statistics. Stateful Design: Saillogger is stateful by design. Importing a track risks breaking this state by introducing inconsistent data over time periods that have already been processed. (Imagine a boat "beaming" in and out over a couple thousand miles in a single day!) Streamlined User Experience: Our data model is extremely rich, but to ensure a streamlined experience for regular users, we simplify what is processed and displayed. In practice, we normalize every account to a single boat, maintaining that boat’s state in great detail. For users with multiple boats, we create separate accounts.

That said, we’d love to help you add your deliveries. If you send us the GPX file, we can experiment with it to see if the import process makes sense.

We would need to have a plan for a clean fallback to ensure that Harmonie’s logbook and track remain accurate!

We have also discussed this with Victron. They will address it for all Cerbo GX Mk2s.

The log from today's boating looks much better. Thanks !

Hi @WJGreene2025, Saillogger is a feature-rich tracking and advanced monitoring system designed to go beyond basic location tracking. It offers comprehensive features such as:

Detailed trip logs: Automatically segmented into individual trips, including specific location names where you anchor, dock, or moor.

Micro-blogging: Easily document and share your journeys.

Detailed statistics: Gain insights into time spent at anchor, dock, mooring buoys, or home/foreign ports, and track visits to different countries or regions.

Advanced NMEA2000 monitoring: Ability to associate any custom NMEA2000 data with trip logs for future reference or diagnosis.

Saillogger is compatible with multiple data sources, including PredictWind's DataHub and Victron GX devices. Some features, such as NMEA2000 monitoring, depend on the underlying platform.

You can continue using DataHub as a data source while benefiting from Saillogger advanced tracking and analytics capabilities.

If you decide to transition from DataHub to a Victron-based solution, Saillogger can also support importing your historical tracks from PredictWind.

I hope this helps. Feel free to ask if you have any questions or need further clarification.

The current coverage is stunning! I can appreciate the amount of data involved which I assume could be downloaded in real time in small chunks specific to the localized area of interest? Perhaps have to zoom to a minimum level before data becomes visible. Perhaps a unified Fleet view where vessels which are broadcasting weather can be identified by a small flag (or color). With regard to AIS: more helpful to me than seeing clusters of targets would be searching for a specific boat name/mmsi by submitting that criteria to the server.