From the point of OpenCPN
of course it would be nice to accept N2K messages straight away. Only problem is no general purpose computers
have an N2K port.
So we need an interface. But there is no standard for that. Most interfaces comes with a closed source driver, the drivers from different vendors all have different API's, and none I am aware of are cross platform. (CANUSB
seems to work on Linux
but without real support from the vendor)
The closed NMEA standard is no issue, it has been reverse engineered and all the needed information is available for making OpenCPN
understand the navigational related PGN's. And it would fit nicely with the new datastream bus concept launched in the latest beta.
But until we have a standard way of interfacing with the physical cable across our supported platforms I don't see this finding it's way into the core
On the other hand, building a platform and driver API specific plugin
for one vendors interface hardware
is already possible and not difficult.
(Maybe I should add that I already have two different N2K buses with different PC adapters installed on my boat (One CANUSB + one Airmar
, but I still use 0183 to feed OpenCPN and that feels just fine...)