Saillogger Community

That's great to hear, thank you for sharing!

We have something in the works to completely eliminate this dependency. It is a major rewrite though so requires extensive testing, please stay tuned.

Is this on a Raspberry Pi? Unfortunately this is a new dependency they introduced, if so can you do a manual npm install signalk-saillogger in ~/.signalk directory?

Hi @upstart ,

This is all automated. If Saillogger detects an engine is running (through NMEA data), it sets the state to Motoring. If not, but it knows an engine is present on NMEA, it marks it as Sailing.

Just deployed a change that may address this. Can you try again?

This should be addressed now for outgoing mails. If you see this on your browser, it probably is a local setting though. If so, can you share the details of your OS and browser?

Hi Michael, printable logbook picks the cruise mode settings. In your monitoring settings, set the initial tracking position to the start of your desired log and then you can get the printable log from that point.

No Jim thank you, we are looking into this.

Hi @upstart sorry for the delay. We are working on submitting a new version of the app to Google Play. You can use the attached version until then.

https://cdn.saillogger.com/static/app/saillogger.apk

Hi Jim, thanks for the report. Is this reproducible? We couldn't see the error, if you have any repeatable instructions, it would be very helpful. Thank you.

Hi @piotr-pingo yes we will update the plugin.

Hi @digger , please send email to us at [email protected] from the e-mail that you are registered with.

Hi @Andrea, this is normal. Saillogger requires GPS position data to function. Your GPS is likely coming from the instruments, which is probably the reason for what you saw.

Hi @mshulman sorry for the delay in responding. Is there a possibility that there were multiple GPS sources at the time this is happening? If multiple sources report slightly different positions it may trigger a movement. If so, and this is happening frequently you can consider limiting your position reports to a single device. It is explained in FAQs.

Hi @Andrea , we missed this earlier. Is this issue still happening? Normally when this happens, it means you are missing position data. Do you have navigation.position available in Data Browser and does it refresh?

Sorry, just seeing your last response here.

Can you check again? We deleted the last two monitoring entries for you and it seems to be working now.

These seem to be separate issues. On the timestamp, please check the time you see on your NMEA 2000 (Chartplotter) and Cerbo GX and specifically the timezone setting. What do you see?

@piotr-pingo we don't use either form-data and tough-cookie, these come as dependencies for some of the libraries but they are not used by Saillogger. This should have no impact to the plugin.

Ok, can you then send your monitoring page or boat name or user id?

Hi @Daniel , can you send a link to the log in question?