Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Saillogger Community

administrators

Private

Posts


  • Logs all seem to start about 30 minutes before we are underway
    adminA admin

    Hi @Sparohok, thank you.

    This is definitely unusual, Saillogger normally eliminates all those starting points automatically and works without any issues. You’re clearly observing something different.
    Having a position all the time is actually a good thing, so that won’t cause the issue, but I suspect it has something to do with that USB GPS.

    I presume you have a GPS source on your NMEA network (chartplotter, AIS, etc.) that comes online before you start moving. If so, can you configure a priority so that your USB GPS is always the lowest priority and only used when nothing else is available?

    Go to Signal K → Server → Data Connections and, using the Priorities table at the bottom, configure priority for your navigation.position and give higher priority to NMEA sources (make sure your instruments are on while you do this). Put the USB GPS at the bottom, and set a timeout of 5 or 10 seconds.

    It will look something like this:

    Screenshot 2025-08-13 at 9.00.35 PM.png

    Make sure you restart Signal K afterwards and let us know what happens on your next trip.


  • Initial Tracking Position issue
    adminA admin

    Hi John, this is a great catch. It was actually updating the starting log, but the track you were seeing was from the cache. In other words, it would have started showing correctly once the cache expired in approximately an hour. Anyhow, it was a bug and we’ve just deployed a fix. Thank you for the report.


  • Windy Station option disabled despite requisite settings and data available
    adminA admin

    Hi Bill, thanks for pointing this out. It turns out that this was a logic issue on the server side, we just fixed it. Please try again and let us know if you see any issues.


  • Log does not include last trip
    adminA admin

    Hi Thomas, it is indeed what is mentioned in the FAQ. It takes an hour to finalize a trip, so if you turn on your Raspberry Pi for just a few minutes, it will autocomplete. Alternatively, keep the Raspberry Pi on a bit longer after you complete your trip.


  • User defined granularity of log points
    adminA admin

    Hi @TargaDriver and @Voodoo, thank you both for the suggestion.

    We understand the desire for more granular tracking in certain situations. That said, a key part of Saillogger’s design is full automation, sampling frequency is part of the core logic and is dynamically adjusted based on context.

    That said, we recently deployed updates to improve how frequency adapts, including better handling of maneuvers beyond just speed changes. Let us know how it helps you. We’ll also log a ticket to explore additional enhancements, such as incorporating vectored charts to help Saillogger recognize when maneuvering occurs near islands, ports, channels, and other complex areas.


  • Uploading missing tracks via .GPX file?
    adminA admin

    Hi Brian, thanks for the note.

    There’s no direct way to link a missing track, but we may be able to help. Have you added any monitoring logs since the last missing segment that’s covered by the GPX file? If not, please send us the file and we’ll see if we can import it for you.

    If you’ve already logged anything since that missing segment, unfortunately this won’t be possible, as Saillogger’s state will have changed and will require deep surgery to import that track.


  • FIXED: Saillogger plugin fails to install on Venus OS v3.62
    adminA admin

    Hi Brian, replied over e-mail but I suspect Venus 3.63 upgrade will not help as Signal K configuration is persisted across upgrades. There is no harm to try though.


  • FIXED: Saillogger plugin fails to install on Venus OS v3.62
    adminA admin

    Hi @SV_Atlas, a factory reset should be the last resort. First, try a clean install of Signal K—step‑by‑step instructions are in this post: https://community.saillogger.com/topic/111/new-install-wont-start/2?_=1753236272577

    Let us know if that doesn’t resolve the issue or if you need help with any of the steps


  • User defined granularity of log points
    adminA admin

    Hi John, I thought we had addressed this as part of this thread. Isn't it working as expected?

    In general, if you are moving fast, the granularity is automatically adjusted and can be as high as every minute.


  • FIXED: Saillogger plugin fails to install on Venus OS v3.62
    adminA admin

    Hi @wrwakefield ,toggling Signal K on or off doesn't delete the Signal K configuration. We haven't explicitly tested the factory reset but pretty sure it would wipe out Signal K configuration as well.

    We regularly delete the Signal K config to test out things from scratch, it has never caused an issue but of course operating on the CLI requires diligence. Just make sure "Signal K" toggle is off before you delete that directory. I don't think it is a showstopper if you don't but it is safer to do so.

Member List

adminA admin
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular