Saillogger Community

Love your work, Ilker and the entire Saillogger team!!

Hi everyone, we just released native support for engine sensors! They are now logged automatically, along with statistics for your sailing and motoring time. Check out the announcement here: https://community.saillogger.com/topic/142/saillogger-plugin-5-x-native-engine-logging

By the way, we just released native support for engine sensors! They are now logged automatically, along with statistics for your sailing and motoring time. Check out the announcement here: https://community.saillogger.com/topic/142/saillogger-plugin-5-x-native-engine-logging

The notifications page isn't very clear. There's a field for depth, for example, but there isn't text saying that the alarm will fire if the depth is less than that setting. But for wind speed, the alarm fires if the wind speed is greater than the number listed.

Also, the interval isn't well described either.

Looks much nicer, thanks!

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

Hi @Andrea This would be a cool feature. We will log this in the backlog and look into it.

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

@admin Hello admin, I entered in the data to be recorded what you suggested and in fact when I started the engine this parameter showed the total running hours of the engine. Unfortunately, however, this data has not been recorded in the path data as per the attached screenshot, although the data is present on the SK server and is available among those shown on Saillogger

c2190cd8-e0f1-4101-88d6-0e82eb26988e-image.png

61b87868-cc00-4215-8adf-9c4b24e24be1-image.png

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.

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