Serial data in and out?

[sebba]

Come over to the new world of openplotter V2.....
Much nicer 

Hello,

Unfortunately I am still disappointed about NMEA0183 multiplexing, filtering and "routing" in V2
For a more complex design, I couldn't find a nice and easy way to handle different nmea0183 inputs and outputs
The main option is "nmea0183out" but, IMHO, this is not a "feature", is a compromise to send some data to nmea0183 connections.
I don't know why kplex is "lost" and "ignored". In V1, kplex did the hard tasks and did it good.
Unofrtunately, in V2, kplex is almost useless and full of bugs

Imagine an old boat with old nmea0183 devices, like a garmin chartplotter, a raymarine autopilot, a vhf radio, an AIS transponder, as a basic setup.
The garmin chartplotter can work at 38400bps, same for the AIS transponder. Raymarine autopilot and vhf/dsc radio work only in 4800bps.
To get all the data from these devices into SK is nice and easy.
But to select which/what data is coming from chartplotter to autopilot (for Autopilot Track Mode) and what data is coming from AIS transponder and sent to charplotter (to show the AIS targets) is a very complicated task.
The easier option right now is to use the sk to nmea0183 plugin but all input data will be mixed and sent (without reason) to every nmea0183 device.
Is not ok to overload the vhf radio, which need only few sentences, with the data which is coming from/for autopilot
Also, AIS related data shouldn;t arrive in autopilot, 'cos is no needed there.

Maybe I am wrong and I didn't got yet the "new style" of working... but I still consider the "old" kplex did the right job in a very easy and intuitive way.

If I am really wrong, I'm asking you all nicely to point me in the right direction.

Thank you and fair winds,
Seb