<![CDATA[record engine hours on trip logs]]>Hi, I've already started a similar thread but haven't gotten a response. I'd like to be able to record the number of engine hours at the start and end of a trip in additional data. The data is available on SK (Propulsion.Port.runTime) and is accepted by Saillogger (I see it from the app while the engine is running) , but it isn't recorded at any point during the trip. I also read another parameter from the engine which is the RPM and that is recorded regularly. Any idea how to fix this? Thanks.

]]>https://community.saillogger.com/topic/140/record-engine-hours-on-trip-logsRSS for NodeThu, 11 Jun 2026 18:59:51 GMTMon, 13 Oct 2025 07:20:05 GMT60<![CDATA[Reply to record engine hours on trip logs on Mon, 03 Nov 2025 01:32:50 GMT]]>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

]]>https://community.saillogger.com/post/558https://community.saillogger.com/post/558Mon, 03 Nov 2025 01:32:50 GMT<![CDATA[Reply to record engine hours on trip logs on Mon, 20 Oct 2025 07:09:44 GMT]]>@admin I configured another "engine hours" data item, taking the same variable from SK, namely "Propulsion.Port.runTime." In fact, I now have two in my configuration. Both now work; even the one that wasn't previously recording data on the graph now records values ​​over time. I can say that the problem is solved. Thanks.

3a1f4e53-b95e-4274-9a70-886f5829fe13-image.png

68ba75f1-89ba-4f91-a392-90481ed90944-image.png

]]>https://community.saillogger.com/post/553https://community.saillogger.com/post/553Mon, 20 Oct 2025 07:09:44 GMT<![CDATA[Reply to record engine hours on trip logs on Mon, 13 Oct 2025 21:12:59 GMT]]>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.

]]>https://community.saillogger.com/post/552https://community.saillogger.com/post/552Mon, 13 Oct 2025 21:12:59 GMT<![CDATA[Reply to record engine hours on trip logs on Mon, 13 Oct 2025 13:24:02 GMT]]>Thanks for the reply, I'm copying the screenshot of the configuration which, as I explained before, works when the engine is on, in the sense that if I look in the iPhone application on the monitor page, the one with the instrument symbol, I see the number of hours the engine has been running , so I think the configuration is correct?
It just seems like it's not recording that parameter

25056683-9166-4405-9b1e-f8602f4176fe-image.png

b41b5810-4199-474d-8a0b-c9bf73b05612-image.png

]]>https://community.saillogger.com/post/551https://community.saillogger.com/post/551Mon, 13 Oct 2025 13:24:02 GMT<![CDATA[Reply to record engine hours on trip logs on Mon, 13 Oct 2025 12:54:06 GMT]]>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.

]]>https://community.saillogger.com/post/550https://community.saillogger.com/post/550Mon, 13 Oct 2025 12:54:06 GMT