Saillogger Community

The monitoring history page (24h) shows correct values, both on the vertical axis as the time stamps. The only outlier is the very last data point. It seems as if the database has one datapoint in the future with values that are a bit off.
So I don’t think the issue is with the plugin side on the boat, or maybe it sent one time wrong values, but rather I think those values remain in the central server database, and keep popping up in the monitoring history page and the monitoring page with a negative “updated since” data field.

ok thanks, just wanted to let you know as the warning was mentioning 2 your plugins. I will happy ignore it now

@Voodoo I don't really need to integrate my 2 old yanmar 4jh4 with the nav system.
Im happy with old fashioned analogue control panels, no need to monitor Bar and Celsius in NMEA or sailllogger. All I would like to achieve is engine status monitoring (running/not running) for trip's logs and statistic.
In my current setup I already have a Victron shunt for engines' alternators (separate 24v 110A alternators) that tiggers "motoring" path in SignalK when minimum 1 engine is running (and alternator charging the house batteries. I can also try using digital inputs of Cerbo to get on/off status control of each engine (we are a catamaran).

Works fine for me obviously for below surface (all other make no sense)

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.