Saillogger Community

Hi @Andrea unfortunately no, all custom monitoring values are displayed in the same format like the second one. The latter one is specialized for reporting the house/main battery.

There is a monitoring option that will automatically convert these to hours, just choose "Duration" while you are adding it.

@admin MMSI was missing. Appreciate it!

Hi @jimholthaus, moorage name lookup in Saillogger is a multi-layer process. It uses four to five different types of logic to identify a moorage name, which can come from GIS sources, community-added moorages, or external references like Wikipedia.

Moorages are created automatically, but once they exist, renaming them is straightforward as Kevin mentioned. Please let us know if you’d like any help with that.

Hi @Sparohok , @jimholthaus 's suggestion is a good one. Please try it.

Beyond that, the behavior is definitely not normal. We will need to simulate your account here and run some tests. I will see what we can do about it but please try the above suggestion first.

Hi @admin , just saw this thread and I have a suggestion. I recently wrote an algorithm to simplify GPS tracks which worked really nicely. I'm not sure if it's original but worked for me. Basically use Shoelace formula (https://en.wikipedia.org/wiki/Shoelace_formula) on a sequence of waypoints. If the area of the polygon formed by those waypoints is less than a threshold, add another waypoint to the sequence; if it's more than a threshold, turn it into a track segment and start over again with the next 3 waypoints. That way the area threshold is a single number that users can tweak for their desired level of detail, you don't have to explain a bunch of parameters. Points all in a line have low area, but the momemnt there's a turn the area increases a lot. Happy to share my Python code.

Hello John, That’s a good catch, I’m not the developer but I’m assuming that that was the most intuitive direction when he developed it. I’m guessing he’ll comment on this if need be. Thanks, Kevin.

@admin

Thank you for the magic. I have now activated the Windy reporting option and will monitor the data on Windy to confirm all is as expected.

Cheers, Bill on SV Denali Rose

Thanks for hoping on it and deploying a fix so quickly. Behavior looks correct now. 😉

Thanks! Will do that.

Thank you very much. Sadly we moved since Saillogger went down and I updated it. The .GPX track was to fill in our transit from when it went down and our new location where I brought it back up. Not the end of the world. Glad to have our beloved Saillogger back up and running!

I second @MacJL
There is already a nice autostate plugin.
No need to reinvent the wheel.

Glad to hear you sorted it out! For future reference, it may take up to an hour for new data keys to show up in Saillogger. This is only applicable for the initial configuration, once done data flows in regular one minute intervals.

@admin Thank you for the work!!!

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

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.

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

Link Preview Image 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...

favicon

Saillogger Community (community.saillogger.com)

Thank you for sharing this Alastair.

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