Real Time monitoring location?
-
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.
-
May 20 10:50:59 2024-05-20T17:50:58.965Z signalk-saillogger Running on Raspberry Pi Zero W Rev 1.1 ARMv6-compatible processor rev 7 (v6l)
May 20 10:50:59 2024-05-20T17:50:59.061Z signalk-saillogger Starting the plugin with collector ID 7649190e-e2a4-4bdd
May 20 10:51:01 2024-05-20T17:51:01.277Z signalk-saillogger Running on Raspberry Pi Zero W Rev 1.1 ARMv6-compatible processor rev 7 (v6l)
May 20 10:51:01 2024-05-20T17:51:01.284Z signalk-saillogger Starting the plugin with collector ID 7649190e-e2a4-4bdd
May 20 10:51:03 2024-05-20T17:51:03.620Z signalk-saillogger Successfully sent metadata to the server
May 20 10:51:03 2024-05-20T17:51:03.635Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:51:03 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))
May 20 10:51:03 2024-05-20T17:51:03.884Z signalk-saillogger Successfully sent metadata to the server
May 20 10:51:03 2024-05-20T17:51:03.889Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:51:03 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))
May 20 10:51:05 2024-05-20T17:51:05.092Z signalk-saillogger Successfully sent 2 record(s) to the server
May 20 10:51:05 2024-05-20T17:51:05.223Z signalk-saillogger Successfully sent 2 record(s) to the server
May 20 10:52:01 2024-05-20T17:52:01.355Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:52:01 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))
-
I turned on the Axiom and signalK is now getting location from that. One thing I noticed is that the lat/Lon fields are in a different order between the Axiom and the Fixed Position plugin. I wonder if the parser in the SignalK client knows how to deal with that?
-
I am not super familiar with Fixed Position plugin but a few things.
- Saillogger is indeed not receiving the position information, you can see that in the debug logs:
signalk-saillogger No position data, not sending monitoring information - Order of "latitude" and "longitude" keys should not matter, as long as the key names and values are correct. Saillogger picks the right value based on the key.
- I suspect this is about the frequency of the position information that
Fixed Positionplugin sends. - Sailogger monitoring requires the position data to be fresh (not older than 2 minutes), I suspect Fixed Position doesn't publish position information frequently enough.
- Can you check the how often that position data is refreshed through
Data Browser? - I would also keep that timeout configuration to less than 2 minutes.
- Saillogger is indeed not receiving the position information, you can see that in the debug logs:
-
You're right. https://github.com/inspired-technologies/signalk-fixedstation-plugin doesn't appear to ever refresh the data.
I can still see the use case for monitoring the boat at the slip, and thus not requiring a fresh GPS position. Maybe that could be a user-configurable setting in sail logger?
-
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!
