Saillogger Community

@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 Let me explain better, the PGN that indicates the hours of use of the engine is shown in Saillogger as soon as I turn on the engine because the interface between the engine and N2K turns on together with the engine. So I should see it recorded in the travellers like the PGN RPM that in the same way comes from the same interface
In the last trip I made it was not recorded
This morning I tried to start the engine and the number of hours of movement carried out by the engine appeared in Saillogger sign that the PGN is read
I hope I have clarified better ?

There is, however, another aspect to consider regarding the data coming from the engine through an interface, for example, YDEG-04, which does not output any data when the engine is off. In this case, on Saillogger, in the N2K parameter monitoring settings fields, the parameter disappears and a blank field is shown. I must say, however, that, at least in the case of RPM, when the engine is restarted, Saillogger starts monitoring the parameter again (at least in my case). This should also happen with the parameter that shows the total engine hours "propulsion.port.runTime" but unfortunately on my last trip it didn't happen and I can't understand why. I say this because this feature is the basis of my desire to know for each trip how many hours of sailing I did and how many of engine.

You're absolutely right (as always), admin. There's a plugin on SK that allows you to send Smart Battery Sense data to SK and therefore to Saillogger. It seems this plugin has crashed. I've now restarted SK and updated VenusOS, and the plugin is back up and running; I can see it on Saillogger. It seems this also happened to the Yachtdevice Yanmar engine interface, YDEG-04, but it only works when the engine is running, so I think it was more of a SK issue. In fact, I can't see the YDEG-04 PGNs now, since the engine is off.

Thanks Admin for the reply, it actually seems as you say, all the "propulsion" data have a timestamp of 9/8 as well as the "propulsion.port.revolutions" data which was recorded at every point of the last trip. The same goes for the "electrical.batteries.starter.voltage" data which has a timestamp of 9/5 which reports a value in Volts that is changing over time due to the self-discharge of the starter battery. However, I can confirm that if I look at parameters such as the wind "environment.wind.speedApparent" I see that the "timestamp" is alive and updating second by second. While I can understand that the data coming from the engine's N2K interface is frozen as a value on last Sunday 7/9 when I turned off the engine, I can't understand the timestamp dating back to 9/8? Even less can I understand the Bluetooth transducer that measures the voltage of the engine's starter battery, which has a value that decreases every day by a few tenths of a volt and has a timestamp dating back to 9/5. Can you help me? Thanks.

Hello everyone, I've honestly already reported this problem (in my case) in another post, but I'd like to bring it up again in the hope that it can be resolved. Basically, some PGNs on my SK server aren't displayed after selecting them in Saillogger settings; the displayed value is zero. Yet, in the SK server data browser, the PGN is displayed with a value, but it's as if Saillogger, although it finds the parameter in the list of available parameters, isn't able to set it and display it. I'll leave some examples in screenshots. Thanks.

@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

@admin I don't remember seeing this pgn among those that my Yanmar to N2K interface provides me but I'll check, however I saw the data of the engine hours expressed in seconds, I could record that and make the delta between the first reading and the last reading and then multiply it by 3600 and obtain the hours, what do you think?

@admin Thanks for the reply, I'm sure it will be great when this is available. Right now, how can I determine how much of a trip was under engine? I connected the RPM data from SK and I see it for every trip, but I don't have a sum of the engine usage time between the times when I was sailing and the times when I was under engine. Is there a way to do it now?
Furthermore, also as a test bench, I tried to connect the SK Fuel Rate data which is expressed in m3/h but I did not find a type of representation given that could read it, I have speed volume etc but not a ratio such as volume/time

Hi JeremyJed, I either installed a Yanmar engine interface that sends engine data to the NMEA2000 bus. When you say that Saillogger can track engine travel hours, is that your wish or does Saillogger already do it? For now, I've only been able to see the engine RPM in the logs, within the additional data (min/max), but I'd like a report that shows how many hours I've been under engine and how many under sail. Regarding fuel consumption calculated by observing the fuel level at the beginning and end of a trip, I doubt it would be precise or indicative. First, because tank level sensors are rheostats that aren't exactly linear, so they only provide an indicative measurement. The other problem is that the readings taken at the beginning and end of a trip could be affected by the boat's rolling. It's much better to take the engine data regarding instantaneous fuel consumption and record it in a database to understand the overall value for a trip, in my opinion.

I take advantage of the dialogue to ask you, the parameters that are added in Monitor & Tracking such as the battery, are not shown with a small display as in the case of the battery that is at the beginning of this list, I show you two screenshots, is there a way to choose whether the synoptic is standard?
As you can see the Starter Battery does not have the name on it

I just tried searching for this parameter again in Saillogger, and it suddenly appeared in the list of available parameters. I can't explain the phenomenon. Now I can see this value and even set an alarm threshold, which was exactly what I wanted. Thanks.

Thanks Admin for the reply, to answer your question, before you asked me, I queried SK Data Browser and searched for the word Starter which is contained in the "electrical.batteries.starter.voltage" pgn in the screenshot I attached to the question. Do you think this check is sufficient or can I look elsewhere? For example, I also use another application for iOS called WilhelmSK which allows me to see all the parameters that circulate on SK and as I show you in the screenshots I attach, this battery is also visible in this app.

I would like to be able to monitor a PGN provided by SK that shows the starter battery voltage but I don't see it among the list of parameters that begin with "electrical.batteries.starter.voltage". Where could I be going wrong?

@admin Hi, I wanted to offer my services as a beta tester for experimental plugins that would test this new feature. I installed the sensor that displays RPM, pressure, and other engine information on SK, and I also added it to Saillogger as data to monitor, and it works (obviously). If you'd like to test this new feature on me, I'm available. Thanks.

@wrwakefield I had no doubts that everything would be fine. These guys at Saillogger are very concrete and good. Hurray!

@wrwakefield Good luck

@wrwakefield Sorry last suggestion, have you tried asking on the Victron website?

@wrwakefield Actually a case study. Since you have the Cerbo GX have you ever installed a plugin in SK? because it seems strange that in a native configuration like that of version 3.50 with Venus Large, Signal K can give problems, I have used numerous Cerbo even with versions prior to 3.50 and both Signal K and Node Red have always worked well. Of course in Signal K has it made your login and password and do you access with those correctly?

@wrwakefield Hi Bill, so since you updated to VenusOs 3.62 on Venus SK have you managed to update to saillogger 4.21 or not?