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


  • Some Nmea2000 parameters are not shown
    adminA admin

    Hi @Andrea, not sure if I could fully follow. Do you mean propulsion.port.runTime was available in Signal K with fresh data and it didn't show up in Saillogger?

    Could you capture this when it happens?


  • Some Nmea2000 parameters are not shown
    adminA admin

    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.


  • Some Nmea2000 parameters are not shown
    adminA admin

    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.


  • starter battery monitor
    adminA admin

    Hi @Andrea unfortunately no, all custom monitoring values are displayed in the same format like the second one. The latter one is specialized for reporting the house/main battery.


  • Fuel Economics
    adminA admin

    There is a monitoring option that will automatically convert these to hours, just choose "Duration" while you are adding it.


  • Fuel Economics
    adminA admin

    @Andrea you should be able to use /vessels/<RegExp>/propulsion/<RegExp>/runTime which is the total running time for engine in seconds. This will show up as something like propulsion.0.runTime in your Signal K. You can add this to your custom monitoring and look at the delta between the last tracepoint and the first one. Not the ideal UX but it will be automatically logged for you.


  • Fuel Economics
    adminA admin

    Hi @JeremyJed and @Andrea, Saillogger can track engine hours by adding them manually to your monitoring data, and they will be part of your trackpoints. This way you can see the engine hours at the beginning and end of the trip by clicking on those trackpoints.

    However, this can certainly be improved. We always aim to provide the best UX, and it is important for Saillogger that things “just” work. We are working on making this an integral part of the log that works automatically (for example, Saillogger can detect when you are sailing or motoring, handle multi-engine scenarios, and give meaningful stats). Creating the right experience is a bit involved, and we did not have a good test bed for this until recently. We finally installed sensors on our twin Yanmars (running the N2K cables was the hardest part), and this is now at the top of our list of new features. It needs proper thought and testing since it is an important feature.

    Automatically tying it to fuel consumption is more complex. The math is simple, but there are many scenarios that must be accounted for in order for it to work well. For example, fuel sensors are not always precise, logic must account for multiple tanks, transfers between tanks, additional equipment like generators drawing fuel, or swells causing fluctuating readings. We aim to provide a great UX, so this will likely not be part of the initial version. A better approach may be to rate the engines’ consumption and associate it with conditions like those above. This aligns with @Andrea’s note. It is possible but not a trivial implementation.

    Taking a step back, and to summarize, you can already monitor engine hours and tank levels, and we will improve the experience as soon as we can run experiments on our test bed. Fully automated stats that provide smart insights into fuel consumption will likely take longer, until we can convince ourselves that the data is really good.

    Thank you for your interest and for such an insightful discussion!


  • starter battery monitor
    adminA admin

    Hi @Andrea , looks like Victron is not sending that reason. Are you sure it is available in your NMEA 2000?


  • Moorage Name
    adminA admin

    Hi @jimholthaus, moorage name lookup in Saillogger is a multi-layer process. It uses four to five different types of logic to identify a moorage name, which can come from GIS sources, community-added moorages, or external references like Wikipedia.

    Moorages are created automatically, but once they exist, renaming them is straightforward as Kevin mentioned. Please let us know if you’d like any help with that.


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

    Hi @Sparohok , @jimholthaus 's suggestion is a good one. Please try it.

    Beyond that, the behavior is definitely not normal. We will need to simulate your account here and run some tests. I will see what we can do about it but please try the above suggestion first.

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