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

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.

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

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

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.

Hi @SV_Atlas , it is possible to add any NMEA 2000 data monitoring and with plugin version 4 they are also associated with your trip logs. Please see the announcement here: Plugin 4.0: A Game-Changer for Saillogger!

We have also published a video tutorial explaining how to use this functionality: Saillogger NMEA 2000 Monitoring

Let us know if you encounter any problems using it.

Yes, this was a bug that we also noticed an fixed it (hence you saw it gone). You have probably noticed it before we addressed it.

All should be good now but let us know if not.

@SV_Atlas said in Log Notes editing?:

We are enjoying the new notes editor, thanks again for the really great update.

One request please: Can you please move and/or change the color of the "Cancel" button? It's proximity and similar colors to "Save" have led to more than a few deleted notes which has been frustrating. Ideally if one were to press cancel or delete there would be a second "Are you sure" confirmation.

We re-aligned save to the left and cancel/delete actions to the right, this should create enough spacing and hopefully avoid accidental cancellations.

BTW, for delete, there is already a confirmation but we think it will be an overkill for cancel.

Hello,

For the GPX track, it's an export from TZ Iboat app. I'll send it by mail tonight. I also have other GPX files from my Yach Device router. I'll send it too when I get it.

But I'm sure I will have some trips where I'll have no log at all, whatever the reason (bug, electronic issue, small trip whithout powering on instrument, etc...). And I would love to track it, as I would do it in a real Logbook.

Of course, all informations would have to be entered manually, and automations will not work. Don't you think it's a real use case ?

Wow, this is great, THANK YOU!!!! Well done and so quickly implemented! Thanks again.

Hi Brian,

At the moment, we don’t offer an annual subscription due to accounting complexities.

However, please check out our partner program. By making referrals to Saillogger, you can cover the cost of your subscription or even add to your cruising budget!

Thank you for your consideration.

I, too, agree that the UI needs to be clean.

Perhaps just add them to the History section of the Monitoring tab? Ideally, it would be on the main page so those tracking us could see them, but if they're nerdy enough they can click through to see the more granular data.

Hi there thank you for the questions, this functionality already exists. You can click on the datapoint and it will open a popup that includes a button to delete that tracepoint. Here is a demo:

Saillogger delete datapoint/trackpoint demo

We will also add this to Support documents.

@andreshs1, additionally we also revamped the log details page with the new design and the entire site's color palette has been updated as well. Gradually all pages will be transitioned to the newer look and feel (that of monitoring page and now the log details page).