ATON display

[rgleason]

Would Tehani have something to add? He seems to know a lot about PGN too.

[stevead]

I can't say I see SignalK as a competitor of any kind.

For integration with NMEA 2000 networks, it competes against my TwoCan plugin !

For AIS SART, AIS MOB and AIS EPIRB devices, to the best of my knowledge they all generate PGN 129038 messages (Class A position reports), the major difference with a Class A position report from a vessel is that the MMSI number is prefixed with 970 for AIS SART devices, 972 for AIS MOB devices and 974 for AIS EPIRB devices and the navigation status set to 14 to indicate an active transmission and 15 to indicate a test transmission.

These values should be no different to the values parsed by OpenCPN when parsing NMEA 0183 VDM messages, so the same logic should be applied when OpenCPN is parsing a SignalK AIS SART, MOB or EPIRB message.

I assume that none of this has ever been tested ?

[Hakan]

For me it's not about competition but complement. It's very good we have both for different scenarios.



The different classes, like SART and ATON passing through NMEA0183->Signalk are all tested to work as they should and according to your description.
The N2k->SK way is not tested what I know. I my case due to unavailable devices for such a test. But it's good it's now tested and thanks to TVR and you a correcting process may start.

[teppokurki]

Thanks for the heads up on this. I read CF only now and then and SK reference appearing in a thread may very easily escape my attention.

Fix is under way https://github.com/SignalK/n2k-signalk/pull/228

Håkan: it is pretty easy to play back log files with SK server and there's a sample N2K input file included. bin/n2k-from-file starts the server with that. Can't remember off the top of my head how well the non-vessel ais targets are in that file, but I can probably dig up some.

Stevead: I hope your comment about SK being a competitor was in jest, as I think they cover different feature sets. Yes, there's overlap, but both have their sweet spots, and will probably continue to do so. And I really appreciate your detailed help related to this issue!

[Hakan]

All..
The SK team has already updated the n2k-signalk package. See more here: https://github.com/SignalK/n2k-signa...ent-1003190003
Those having a N2k including Aton and Base feed please update and test.


Many thanks to all involved"

[TVR]

And it works!!

I'm away from home at the moment and logging into my RPI remotely on my phone, but here's a screenshot of the new AIS target list

[TVR]

And here's Buoy 382 correctly rendered as Cardinal Mark N :

[TVR]

And the sensors.ais.class field correctly populated in the SignalK data browser:

[TVR]

However - I've just noticed I still can't see Shore Basestations listed in the OpenCPN target list, even if I increase the range limit to a large value. Is this expected behaviour, or is it a bug?

[Hakan]

TVR..
Many thanks for the test.
About BASE.
In your example that base target is sorted out by O due a not valid mmsi number. A base station has two preface zeros so in your case the mmsi should have been 002300048

@teppokurki
Could it bee the "n2k-signalk" logic is omitting the prefaced zeros somewhere in the process, e.g. a integer to string conversion?
As a comparison it's working as it should by "NMEA0183-signalk":

"urn:mrn:imo:mmsi:002655148":{"mmsi":"002655148",
.......................

"sensors":{"ais":{"class":{"meta":..........
"value":"BASE",

[teppokurki]

The base station missing prefix problem seems to lie with canboat https://github.com/canboat/canboat/issues/267

[Hakan]

teppo..
Thanks for finding and the issue.

[TVR]

One final issue I've just noticed - AtoNs are now displayed correctly on the chart, but they're still rendered strangely in the AIS Radar plugin:

radar display.png Views: 56 Size: 212.2 KB ID: 252197" style="margin: 2px" />

[Hakan]

TVR..
That I think you've to discuss with the plugin publisher.
See more here:

https://www.cruisersforum.com/forums...on-190125.html

https://github.com/Verezano/AISradar_pi/issues

[rgleason]

Humm' I thought I had included that file back in august. Will check.