@admin I configured another "engine hours" data item, taking the same variable from SK, namely "Propulsion.Port.runTime." In fact, I now have two in my configuration. Both now work; even the one that wasn't previously recording data on the graph now records values ​​over time. I can say that the problem is solved. Thanks.

3a1f4e53-b95e-4274-9a70-886f5829fe13-image.png

68ba75f1-89ba-4f91-a392-90481ed90944-image.png

Looks much nicer, thanks!

This has now been fixed - thank you Saillogger for addressing the issue.

Very interested in this! I have the yacht devices N2K gateway as well, and would like to be able to log how much of a journey was motor vs sail, and starting and ending engine hours.

Hi @digger, welcome. You are spot on—if you want to share your position or logs with a select group of people, like your family, you can enable the public profile and set a password. That’s exactly what the password for the public profile is for.

@admin Hi Admin, today I was able to go out by boat and I was able to verify that in the trip the number of engine hours was not recorded and I don't understand why, the RPMs are recorded as long as the engine is running of course and instead the pre-engines are not

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.

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

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!

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)