Saillogger Community

I have a very old account with sailloger.com and I no longer have the password. I tried to do a password reset, and got the confirmation that the password reset email was sent, but I never received it, and it's not in my spam or junk folder.

I do have an account, because I tried to create a new account with that email address, and I got a message that the email was already in use.

mshulman at gmail dot com

How is the home port determined? If we move the boat, how long before the home port is updated?

It seems like I should be able to set it in Settings, but I don’t see it.

Michael
S/v A Bientot

Oh, I can click Marina del Rey because it’s the termination of my latest log. Done and done

Hi!

We just went out for a four hour sail today. While we were out, I noticed that the realtime monitoring feature was working.

Then we got back to the slip. I left the raspberry PI running signalK on. After we put the canvas on the boat, I turned off the cockpit MFD, which is the GPS source for the NMEA network.

Now I see under Monitoring > Realtime, that spillover thinks that the voyage is still under way, and the last reading from the boat was 29 minutes ago.

When I look at the signalk sailloger plugin, I see:
0 entries in queue, last connection to the server was 29 minutes ago.

That's roughly the time that I turned off the MFD.

So a few questions:

1. If I want to monitor windspeed, direction, temperature, do I need the MFD on so that there's a GPS source?
2. Do I have to do anything to "close" the trip? If I had left the GPS on, would that have automatically closed the trip after not moving for a certain amount of time?
3. Is there a way to predict how long it takes for the voyage to show in the logs? Does it depend on having a GPS source for the SignalK server?

xMay 18 15:28:32 Error: SQLITE_MISUSE: Database is closed at plugin.stop (/home/pi/.signalk/node_modules/signalk-saillogger/index.js:78:10) at stopPlugin (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:239:16) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:445:17 at savePluginOptions (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:135:13) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:437:13 at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:149:13) at Route.dispatch (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:119:3) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at /usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:284:15 at Function.process_params (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:346:12) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:280:10) at Function.handle (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:175:3) at router (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:328:13) { errno: 21, code: 'SQLITE_MISUSE' }

I want realtime monitoring of my boat at the slip, so I enabled the Fixed Position plugin at a lower priority. I don't know if it's related to this error.

1. 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).
2. I don't think I was doing anything in particular that caused this error
3. Yes, the plugin and server stopped working.

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

I am trying to used the Fixed Position plugin instead of a GPS source while at the slip. I mistakenly put in the lat/Lon with a + longitude instead of -, and it put me in Asia. So I fixed that and now the realtime position is putting me in California, but inland.

I tried to fix the longitude again, but now the new longitude isn't getting picked up by the realtime monitor.

Is there something I can do to force the realtime monitor to snap to the location that I'm currently sending? I tried restarting the plugin and restarting signalk but that didn't help.

Makes sense. I think we just won't recommend that particular sensor, since it's refresh rate is r fast enough for monitoring.

I'm really excited to have SailLogger on the boat. That you for making it available.