A
Checking the configuration, it looks like that section may be misconfigured. Make sure the Data Field section in the configuration is not empty. Also, for testing, please make sure you don’t change your monitoring configuration during a trip. Make any changes before starting or after completing the trip, but not in between.
Let us know the outcome.
Hi @Andrea , sorry we didn't see your previous message. Looks like your RPM is logged in trip logs and monitoring but we don't see anything about engine hours.
First step is to make sure it does show up in Saillogger monitoring, if it does, then it will show up in trip logs.
Do you ever see it in Monitoring? Make sure you give a proper field name and it maps to the Signal K path. Engine should be running or at least the ignition should be on when you do this.
Hi @joyride , not sure what happened here but it clearly didn't mark the trip start, so that was the issue but not sure when. Were the instruments on and was Saillogger receiving the position reports then?
When you leave the dock again, please check if Saillogger sees your position and in about 15 minutes recognizing you as being underway.
Hi @Andrea, it is hard to debug this from the screenshots, as it appears there may be multiple factors at play. I am not entirely sure Smart Battery Sense works with Signal K, since we do not have one to test, but one thing to check is the frequency of its updates. Something feels off there.
For Saillogger, it watches these signals and checks their age. If they are fresh, it processes them; if not, it ignores them. Saillogger uses one-minute granularity for data but allows a bit of buffer time since not every source emits data regularly. That said, any reliable source should definitely send data every minute; otherwise, it is not ideal for monitoring purposes.
Hi @Andrea, when you see these in Data Browser, how fresh is the data? In other words, can you confirm the timestamps are being updated and are recent? It’s possible the data you saw was older and retained in Data Browser history. Saillogger normally only logs data that is fresh (less than about a minute and a half old), so if the data is stale, Saillogger won’t pick it up.
@Andrea you should be able to use /vessels/<RegExp>/propulsion/<RegExp>/runTime which is the total running time for engine in seconds. This will show up as something like propulsion.0.runTime in your Signal K. You can add this to your custom monitoring and look at the delta between the last tracepoint and the first one. Not the ideal UX but it will be automatically logged for you.
Hi @JeremyJed and @Andrea, Saillogger can track engine hours by adding them manually to your monitoring data, and they will be part of your trackpoints. This way you can see the engine hours at the beginning and end of the trip by clicking on those trackpoints.
However, this can certainly be improved. We always aim to provide the best UX, and it is important for Saillogger that things “just” work. We are working on making this an integral part of the log that works automatically (for example, Saillogger can detect when you are sailing or motoring, handle multi-engine scenarios, and give meaningful stats). Creating the right experience is a bit involved, and we did not have a good test bed for this until recently. We finally installed sensors on our twin Yanmars (running the N2K cables was the hardest part), and this is now at the top of our list of new features. It needs proper thought and testing since it is an important feature.
Automatically tying it to fuel consumption is more complex. The math is simple, but there are many scenarios that must be accounted for in order for it to work well. For example, fuel sensors are not always precise, logic must account for multiple tanks, transfers between tanks, additional equipment like generators drawing fuel, or swells causing fluctuating readings. We aim to provide a great UX, so this will likely not be part of the initial version. A better approach may be to rate the engines’ consumption and associate it with conditions like those above. This aligns with @Andrea’s note. It is possible but not a trivial implementation.
Taking a step back, and to summarize, you can already monitor engine hours and tank levels, and we will improve the experience as soon as we can run experiments on our test bed. Fully automated stats that provide smart insights into fuel consumption will likely take longer, until we can convince ourselves that the data is really good.
Thank you for your interest and for such an insightful discussion!
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 @stiggy, do you see the paths available on Cerbo’s Signal K? You can check in the data browser. If they show up there but not in Saillogger, make sure Signal K is configured with an MMSI and restart after making any changes. If it still doesn’t work, enable debugging in the Signal K Saillogger Plugin and check the logs.
Hi @Sparohok, thank you.
This is definitely unusual, Saillogger normally eliminates all those starting points automatically and works without any issues. You’re clearly observing something different.
Having a position all the time is actually a good thing, so that won’t cause the issue, but I suspect it has something to do with that USB GPS.
I presume you have a GPS source on your NMEA network (chartplotter, AIS, etc.) that comes online before you start moving. If so, can you configure a priority so that your USB GPS is always the lowest priority and only used when nothing else is available?
Go to Signal K → Server → Data Connections and, using the Priorities table at the bottom, configure priority for your navigation.position and give higher priority to NMEA sources (make sure your instruments are on while you do this). Put the USB GPS at the bottom, and set a timeout of 5 or 10 seconds.
It will look something like this:
Make sure you restart Signal K afterwards and let us know what happens on your next trip.
Hi John, this is a great catch. It was actually updating the starting log, but the track you were seeing was from the cache. In other words, it would have started showing correctly once the cache expired in approximately an hour. Anyhow, it was a bug and we’ve just deployed a fix. Thank you for the report.
