Nice, please share when done!

Got it, thank you!

Looks like there was indeed a problem with zoom. This has been addressed and a fix has been deployed. Thank you for bringing this to our attention.

Hi, unfortunately monitoring page is not customizable right now but we will file a feature request for this.

What were the timestamps for navigation.position? Timestamps are critical here. Signal K may display positions even if they aren’t being refreshed, but Saillogger will only use positions if they are actively refreshed. When you encounter an issue like this, please verify those timestamps.

Generally, there’s no technical reason why a GPS position in Signal K wouldn’t appear in Saillogger. Saillogger retrieves data directly from Signal K, so as long as the position is present and refreshing (refreshing is essential), it should definitely capture it.

Ok, interesting. Thanks for documenting it. You may want to file an issue with that plugin, they should look into it.

@mshulman Unfortunately, that is by design for now. There are a couple of things that make it tricky. Units are shared across all values in a block, so displaying a 38 F and 32% in the same block becomes fairly complicated, both for conversions that need to take place (i.e. SK uses kelvin behind the scenes) and the display on the page. That is the reason blocks share a single unit at this point.

@Brazen-Article , that can be done but requires some thinking. We will file a feature for backlog.

Thanks, I found a problem with one of the gps sources. Turned it off and Saillogger shows correct heading.
I'm underway now and boat speed is showing up, I'll check the log tonight. Attached is a screenshot from yesterday's log showing zero. It has been showing correctly while moving but zero on the processed log for the last several days.

Screenshot 2024-10-19 at 10.19.54 AM.png

Functionality including access to logs and stats is paused with a seasonal subscription pause.

Hello, I have a relatively new install of signalk on openplotter. i just tried to install it and got the failed message as well.

Those two pending transactions indeed finally did clear. Since you got charged multiple times now, we refunded those two payments. It may take a couple of days to show up on your balance, let us know if they don't.

Hello @SV_Atlas

I didn’t mean for it to be confusing, I talked with Ilker just prior to sending you the info. I was experiencing the same issue and I had to reinstall mine. Ilker asked that I relay that info to you.

I unfortunately didn’t see your communication with him till after I hit send.

Sorry for the confusion, just trying to help. I’m glad that your issue was easier to fix.

Kevin N
Saillogger

That’s a very interesting and informative article, thanks!

Happy sailing.
Kevin Nasr
Saillogger team member.

Here is the timeline for the trip:
8/8/2024 8:38:46 AM - boat departed Marina del Rey
8/8/2024 3:53:14 PM - boat lost internet connectivity off the coast of Catalina island
8/11/2024 7:48:21 AM - boat departed Catalina island (without internet service)
8/11/2024 2:59:20 PM - boat arrived Marina del Rey (still without internet service)
8/12/2024 12:31 PM - boat re-connected to the internet, logs sent up

Perfect! Have a good night!

Enjoy your new boat!

@admin
Thank you, I will try to update.

Best regards,
Hanne

That was simple! I didn't realize that empty space was part of the list.
Thanks...

Position is a key data point that is critical for Saillogger functionality, so ignoring it will defeat the purpose of many of the functions. Your use-case is pretty special. I wrote a simple plugin for you to use that can emit static positions every 30 seconds, you can use it to address your use-case: https://github.com/itemir/signalk-fixed-position, hope it helps!

I'm running (right now) on a raspberry pi zero w. After this message, I got a node kernel panic and I had to restart the pi. I think that the poor thing just ran out of resources (threads or whatever). I don't think I was doing anything in particular that caused this error Yes, the plugin and server stopped working.

Now that I've recovered from this error, I'm not seeing it again.