hkapanen / ais-forwarder Goto Github PK

Using n2k connected AIS rx , it appears that own AIS details are not being sent by the plugin.
(works correctly for all other vessel AIS)

assuming this resulting for differences between 0183 and n2k connected AIS rx messages.
( not sure if? own AIS details are being output by AIS onto n2k.? but either way,
the plugin is not seeing own AIS details and not sending to marine traffic)

Hi,
I've just installed on my Signal K on an Openplotter installation.
Version installed 0.2.0
It works, but I see from the server log, that it send same information more time in a few millis.
Example:
Dec 03 18:53:34 2020-12-03T05:53:34.915Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Dec 03 18:53:34 2020-12-03T05:53:34.916Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Dec 03 18:53:34 2020-12-03T05:53:34.917Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Dec 03 18:53:34 2020-12-03T05:53:34.918Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Dec 03 18:53:34 2020-12-03T05:53:34.918Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Dec 03 18:53:34 2020-12-03T05:53:34.919Z ais-forwarder sending "!AIVDM,1,1,,A,B5NNsOP00;7P7<JpsNS3Kwi5oP06,054"
Example2:
Dec 03 18:54:31 2020-12-03T05:54:31.315Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,0*4B" Dec 03 18:54:31 2020-12-03T05:54:31.316Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,04B"
Dec 03 18:54:31 2020-12-03T05:54:31.316Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,0*4B" Dec 03 18:54:31 2020-12-03T05:54:31.317Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,04B"
Dec 03 18:54:31 2020-12-03T05:54:31.318Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,0*4B" Dec 03 18:54:31 2020-12-03T05:54:31.319Z ais-forwarder sending "!AIVDM,1,1,,A,B7fvp000;7Ow1Jpt>:dGwgUWP06,0*4B"

As you can see also from the picture attach, Marine Traffic graphics show the message per minutes, since I used your plugin, the messages are more than double compared with before,

Regards
Thanks
Max

When configuration of the plugin is changed to specify a new IP address or port number, AIS forwarding still continues to the old IP address/port until the server is restarted.

Oddly enough, this serves as a workaround for issue #1 but the state is obviously not persisted across server restarts.

Hi,

It seems the plugin is losing connectivity to marinetraffic after a loss of network. In our marina the accesspoints are rebooting daily so the RPI loses connectivity every night. After the network is reconnected (Aprox 2 to 3 minutes) the connection to marinetraffic stays down.

Can you please investigate this?

Best regards,
Patrick

Hi,

The plugin is really good and simple to use. I would like to have the option to forward to multiple destinations, similar to the AIS-Reporter plugin. Add multiple IP address and port numbers.

Is this something that could be achieved?

Hello,

And thank you for your useful plugin.
I'm using it to send data to MarineTraffic, where my boat is acting like a roaming station.
In the last period (since the Ukraine/Russia war started) some GPS signals are jammed, and my AIS receive wrong position for some ships.
Because of these invalid positions, MT set my AIS station as offline, even over 90% of data is accurate.

So, I want to ask if is possible to add a feature for filtering (forward reporting) only ships which are closer than some distance which can be real data. Right now, I receive good data 30Nm around me but because the GPS jammers some ships are reported 250Nm away which is wrong.

Thank you,
Seb

Note on cmdline out at server startup.