OpenCPN not reporting a special NMEA 2000 AIS target

[s/v Jedi]

Originally Posted by Hakan

Now the Dutchman's didn't make a mmsi-number rule for that. Only a "diver's radio" See here

Initialize the variable to “Unknown”, then run the lookup table to set the variable to a known ID if available and plot whatever it ends up with

[stevead]

Perhaps I'm being daft, but as far as I can tell OpenCPN does parse PGN 129040, albeit "incorrectly" displaying (or possibly storing it) as a Class A AIS device (Note the Class A dialog and missing draft value).

My dump of one example of PGN 129040 from the attached log file:

AIS Message ID: 19
Repeat Indicator: 0
MMSI: 503067900
Latitude -38 6.90
Longitude: 144 23.40
Position Accuracy: 0
RAIM: 0
Time Stamp: 49
COG: 43.00
SOG: 9.19
Heading: Unavailable
Ship Type: 56
Ship Name: MV DELPHINUS
Regional Reserved A: 0
Regional Reserved B: 2
Reserved A: 15
Reserved B: 15
Length: 17.00
Beam: 4.00
Reference Point from Starboard: 2.00
Reference Point from Bow: 7.00
GNSS Type: 0
DTE Flag: 1
Assigned Mode Flag 0
Transceiver Info: 1
SequenceId: 255

Nonetheless if anyone wishes to send logs containing samples of the offending fishing line AIS transmissions, I would be more than happy to have a look.

[LeaseOnLife]

Steve, for MMSI 503067900, your dump also has a

2021-03-14-01:15:01.111 6  43 255 129809 AIS Class B static data (msg 24 Part A):  Message ID = Static data report; Repeat Indicator = Initial; User ID = "503067900"; Name = MV DELPHINUS; AIS Transceiver information = Channel B VDL rece
ption; Sequence ID = Unknown

and

2021-03-14-01:16:12.972 6  43 255 129810 AIS Class B static data (msg 24 Part B):  Message ID = Static data report; Repeat Indicator = Initial; User ID = "503067900"; Type of ship = Spare; Vendor ID = Unknown; Callsign = VKV5418; Length
 = 17.0 m; Beam = 4.0 m; Position reference from Starboard = 2.0 m; Position reference from Bow = 7.0 m; Mothership User ID = "000000000"; Spare = 20; AIS Transceiver information = Channel B VDL reception; Sequence ID = Unknown

and I think that is where O gets position & name from. I used following command:

cat candump-from-steve.dump |candump2analyzer |analyzer |grep 503067900

When looking at the O NMEA debug window, I see this when a PGN 129040 comes by:

 18:42:03 (N2000) PGN: 129040 Source: nmea2000 socketCAN-vcan0 ID: 43  Desc: No description. Not used by OCPN, maybe passed to plugins

So I still stand with what I said earlier, when a AIS fishing buoy only transmits PGN 129040, O will not display it.

[LeaseOnLife]

Here is a heavily filtered (small) candump with only PGN 129040, from last April. The target(s) should show up around Longitude = -148.097; Latitude = -17.321
Remove the pdf extension, it is just text.

[stevead]

Like I said, perhaps I'm daft.

You are correct, in the previous log there were some PGN 129809 & 129810 messages that referred to the same MMSI number as present in the PGN 129040 message.

Find attached the same log file but with all PGN 129038 (Class B Position Report), 129809 (Class B Static Data Part A) and 129810 (Class B Static Data Part B) messages removed.

Indeed as you observed, PGN 129040 messages are not parsed.

A kind of WTF !

So two bugs,
Firstly PGN 129040 is not processed.
Secondly reception of PGN 129809 or 129810 without a previous PGN 120039 results in an erroneous AIS Class A Position report.