Good news from the AIS
unit vendor front. It helps to have very
specific reports, with accuarate message logs
, to get some response from a commercial
vendor like this.
Well done, Matt.
Thinking again about this problem while underway today and daydreaming....
To solve this particular problem in OCPN side, we really don't need a separate options entry field for ownship MMSI. We simply do this:
If we ever see an AIVDO message in the datastream, we snag the MMSI and declare that MMSI
to be the ownship MMSI.
Then, if we ever see an AIVDM message with this same MMSI, we process as normal VDM, but set a flag to preclude doing any CPA calculations and/or alerts for this target.
So, ownship appears in the AIS
target list, but will not cause CPA alerts.
Better than nothing, at least until the transponder firmware is updated.