Some Nmea2000 parameters are not shown
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
@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 ?
