TwoCanPlugIn
commented
2 years ago Some further observations.
BTW, Not sure what happened with the formatting of the NMEA 183 sentences above. Have now learnt to enclose as code.
The DSC Distress alert sentences were
$CDDSC,12,5031105200,,05,00,2380814428,1800,,,R,E*6C
$CDDSE,1,1,A,5031105200,04,19252411*18
When sent over TCP or UDP no other nodes/contexts (or whatever you call them) are generated.
Similarly for a DSC Position Report, using the following sentence, nothing is generated.
$CDDSC,20,5031105200,08,21,26,2380814428,1800,,,B,E*77
$CDDSE,1,1,A,5031105200,04,19252411*18
Instead if a DSC Distress Alert Relay is sent, using the following sentence:
$CDDSC,16,2350763930,12,12,00,2380814428,1800,5031105200,05,S,E*65
$CDDSE,1,1,A,5031105200,04,19252411*18
the following context is created with the following values:
`vessels.urn:mrn:imo:mmsi:235076393
navigation.position { "latitude": -38.13333333333333, "longitude": 144.46666666666667 }
notifications.epirb {"message":"DSC Distress Recieved! Nature of distress: epirb"}`
The values in this Distress Relay sentence should be interpreted as: Format Specifier 16 - All Ships MMSI Address - 235076393 (This is the MMSI Address of the relay vessel) DSC Category 12 - Distress First Telecommand 12 - Distress Relay Type of Communications 00 - F3E/G3E, All modes TP Vessel In Distress 503110520 (this is the actual vessel in distress) Nature of Distress 05 - Sinking
Obviously this is being parsed incorrectly, using the wrong MMSI address for the vessel in distress, and the wrong value for nature of distress (12 being interpreted as MOB).
This is just totally broken.
No need to describe its impact on OpenCPN.
tkurki
Is SignalK meant to parse NMEA 183 DSC and DSE sentences ?
Sending the following sentences does not generate any SIgnalK nodes as far as I can tell:
$CDDSC,12,5031105200,,05,00,2380814428,1800,,,R,E6C $CDDSE,1,1,A,5031105200,04,1925241118
and the following error is logged.
Jan 03 21:55:07 signalk:streams:nmea0183-signalk [error] line is not defined +4h