2018-10-08, 07:35 PM
(2018-10-06, 10:15 AM)Newt2u Wrote: One more query in relation to the wiring diagram above and in the docs. Is the TCP connection from signalk on 10110 bidirectional. E.g. will NMEA sentences generated on one of the devices connected to this link be received in signalk and made available on serial or other 10110 connections? My use case is generating autopilot sentences in isailor connected via port 10110 which I will need to be available to the 10110 connection to opencpn? If not, should they be directed to port 30330, isailor does have the facility for setting multiple network connections?
I notice the standard link in opencpn is input only, how to autopilot sentences generated there sent to the rest of the system?
The Signal K Server's TCP 10110 is currently output only. In fact there is no way today to use SK server as a TCP server accepting NMEA0183 data. Adding this capability is not much work - let us know if you or somebody else needs that, preferable in Github: https://github.com/SignalK/signalk-serve...issues/637
As for filtering the general idea in SK server is that each input, like NMEA0183 from a TCP server/serial line or NMEA2000 data from an adapter, emits messages as named events. Then you can make an output like a serial connection listen for that particular event and output the event's data.
Then we have a plugin, aptly named nmea0183-to-nmea0183, that listens for a specified event and outputs filtered events under another name. https://www.npmjs.com/package/nmea0183-to-nmea0183
Another option is to use Node-RED for filtering and altering the flow of data, in much the same way as nmea0183-to-nmea0183 works, mapping data from one named event stream to another.