Saillogger Community

Hi there, welcome to Saillogger and glad you are enjoying it!

For RPM, when you are adding a custom configuration block, make sure to choose RPM in the Data Type. It should look like this:

In regards to your second question, wondering if there is a typo there:

The motorboats are displayed seconds

Could you elaborate on this? What data type are you monitoring?

Hi there, there is a difference between being online and reporting and having positions. Position is a requirement for the rest and it is not sent to the server right now. The updated time (April 26th) shows the last time a position report was received. I am pretty sure what you are observing is related to that.

Several reasons why position reports might not be coming along:

1. Internet connection is down (doesn't seem to be the case)
2. GPS source on NMEA 2000 is not currently on. Note that if you don't have a dedicated GPS or an AIS transceiver, the mostly likely GPS source is the chart plotter. If it is off, this could explain it.
3. You might have mistakenly entered a GPS source in your Saillogger plugin settings in Signal K. If there is an entry, and misconfigured it might be blocking GPS positions. This is explained in question 13 of support articles in more detail.

Most likely reason is (2) above. Please test it by turning on all your boat electronics and chart plotter and make sure Internet connection is available, then wait 10 minutes. Last updated field in Saillogger should reflect something like "Updated 10 seconds ago". When you see that you can turn your instruments off.

Let us know what you find.

Thank you for your post. I suspect this has something to do with the order of the data that came in. I see no reports have been received since April 26th, turning the instruments and Internet for 5 minutes will likely solve this problem. Could you please try it and report back?

Unfortunately this is an annoying Signal K bug. AIS data may override the boat name in some edge cases. It happens more frequently if you happen to have a DataHub but we have seen it happening without a DataHub too.

Signal K team has been working on a fix, here is a link to the tracker: https://github.com/SignalK/signalk-server/pull/1833

In the meantime, restarting Signal K should solve it.

You can certainly use them with custom monitoring, anything in NMEA2k/Signal K can be monitored with Saillogger.

That said, we are working on a much more integrated experience (imagine engine hours being part of your trip logs by default), but it is probably a couple of months out. First we need to install one on our boat and that will probably happen around June.

Hi Otto,

This is a bit strange, as long as there is a single active monitoring device, where the data is sourced should not matter.

Can you check a few things:

1. First ensure that there is no older device or something else configured with the same collector ID. Multiple devices sending data simultaneously will cause problems.
2. Reboot the Raspberry Pi if you haven't already and wait for 15 minutes to see if the labels in Saillogger or data is changing. Try to reconfigure the monitoring parameters on Saillogger at this point.
3. If still doesn't work, it would help to delete the local cache on Signal K. It is unlikely but it might have been corrupted in a hard reset. Here is how it should look like on Venus OS (I haven't tried this on a Raspberry Pi running Venus OS but should be similar)

• Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
• SSH into Venus OS
• Delete the local cache by /data/conf/signalk/plugin-config-data/signalk-saillogger/saillogger_v2.sqlite3
• Start Signal K process

4. If it is still not working, the best is to reinstall Signal K from scratch, here is how it would look like on Venus OS (I haven't tried this on a Raspberry Pi running Venus OS but should be similar):

• Stop Signal K process (Toggle off Signal K in Venus OS menu) - This is important
• SSH into Venus OS
• Delete the Signal K directory by rm -rf /data/conf/signalk
• Start Signal K process
• You will need to download the Signal K plugin again and configure it.

Note that options 3 and 4 can be dangerous in that they may corrupt Venus OS and/or Signal K.

Good luck and keep us posted on what you find.

Hi Jim, yes you can change it per Stay. There is default stay type for a given moorage and it is assigned to all stays there but then you can go ahead and customize each stay as you wish. Go to https://saillogger.com/stays/ and adjust the "Stayed At" drop-down as needed.

Here is an example of how additional data is captured per trip, from our logbook:

This will show up for you the next time you complete a trip, based on custom monitoring data you have added.

Curious if there is a confusion. In regards to wind average/max and SOG average/max, they are already part of each trip log. Here is an example:

Bottom two sections have those.

When you add additional monitoring data, minimum and maximum of those values will also be captured and displayed per log (under a section called Additional Data). Average is a bit more contextual and only makes sense for few types, so these are minimum and maximum right now.

Strangely COG, TWD and AWA are displayed as knots.

You should use the same unit per monitoring block and choose the monitoring type accordingly. So instead of a single "Sailing Performance Data", you could have multiple blocks. All values in a single block will share the same unit.

I was about to say that, more stateful things like average and maximum are not normally transmitted on NMEA, I don't believe they have PGNs either. Saillogger definitely calculates the averages and max and gives it as part of a trip/log summary but from what I understand you want to display that during the trip itself? If so, while doable, they are not currently calculated during a trip.

Re-read your message, if this doesn't work, let's focus on one specific item first.

Make sure that field is available in N2k first, then make sure it shows up in the Data Browser for Signal K. If those happen but the path doesn't show up in Saillogger, restart Signal K and wait 10 minutes.

Please share your findings and we can try to help you more.

Hi Brian, we published a detailed tutorial for this: Saillogger NMEA 2000 Monitoring

In a nutshell:

Step 1: Find the Signal K path of the N2k data you want to monitor

Step 2: Add a custom monitoring section in Saillogger to monitor it. Ensure you choose the right type so Saillogger can do the necessary unit conversions for you (to degrees, knots, miles, meters/feet etc.)

It is indeed because it is a composite value. Those need to be split up. You can do so with Node-RED, please install Node-RED plugin to Signal K (Detailed instructions in this video tutorial)

And then import this snippet (courtesy of Scott Bender of Signal K team) using the top right menu item.

[{"id":"03814fb729f94bf2","type":"signalk-subscribe","z":"1a65e795a2e4022a","name":"navigation.attitude","mode":"sendAll","flatten":true,"context":"vessels.self","path":"navigation.attitude","source":"","period":1000,"x":190,"y":200,"wires":[["aa303e3ca247371e","1be984c9b6dbe6d0","7ae5e956a921f72f"]]},{"id":"aa303e3ca247371e","type":"change","z":"1a65e795a2e4022a","name":"yaw","rules":[{"t":"move","p":"payload.yaw","pt":"msg","to":"payload","tot":"msg"},{"t":"set","p":"topic","pt":"msg","to":"navigation.attitudeflat.yaw","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":410,"y":200,"wires":[["74ede648e6a55306"]]},{"id":"74ede648e6a55306","type":"signalk-send-pathvalue","z":"1a65e795a2e4022a","name":"","source":"","meta":"{\"units\": \"rad\" }","x":710,"y":200,"wires":[]},{"id":"1be984c9b6dbe6d0","type":"change","z":"1a65e795a2e4022a","name":"pitch","rules":[{"t":"move","p":"payload.pitch","pt":"msg","to":"payload","tot":"msg"},{"t":"set","p":"topic","pt":"msg","to":"navigation.attitudeflat.pitch","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":410,"y":260,"wires":[["74ede648e6a55306"]]},{"id":"7ae5e956a921f72f","type":"change","z":"1a65e795a2e4022a","name":"roll","rules":[{"t":"move","p":"payload.roll","pt":"msg","to":"payload","tot":"msg"},{"t":"set","p":"topic","pt":"msg","to":"navigation.attitudeflat.roll","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":410,"y":320,"wires":[["74ede648e6a55306"]]}]

It will create a flow like this:

When you deploy, it will give you explicit paths for navigation.attitude.yaw, navigation.attitude.pitch and navigation.attitude.roll.

At some point, Saillogger should decode composite values but there are many paths that have composite values and doing so in a smart way requires some thinking.

I suspect this is due to the type of value, it needs to be a number. Can you share the value of navigation.attitude from the data browser?

You need to do it in plugin configuration, normally accessible at http://venus.local:3000/admin/#/serverConfiguration/plugins/derived-data when you are on the same network with Cerbo.

Thanks for sharing. We just deployed a change to automatically adjust sampling interval if the boat is making quick turns like tacking or gybing.

You do not need to take any action, this should be reflected in your next trip automatically. Hope it helps to improve your experience while logging short distance races!

I presume it is due to missing some of the tacks and gybes, which adds to the distance but not captured by Saillogger, is that the case? How does your Saillogger track compare to the track that logged 5.5 miles? If you could share a screenshot of that, it would be helpful.

Hi, thank you for the question. Reporting interval is dynamic and adjusted automatically by the speed of the boat. At lower speeds, interval is 5 minutes but it can ramp up automatically if the boat speeds up. What speeds are you racing at?