search

SignalK / signalk-server

An implementation of a Signal K central server for boats.
http://signalk.org
Apache License 2.0
308 stars 153 forks source link

Block/ignore input from a data connection #1430

Open ckcrs opened 2 years ago

ckcrs commented 2 years ago

Could it be possible to have configuration option at user interface, in order to select "input only" or "output only" or "both" data flow direction to server for serial connection of NMEA0183? Thanks... PS: This is enhancement rather than an issue, relevant info at Slack: "currently using serial connection with my SeaTALK_tiny_usb converter (seatalk/NMEA0183 usb converter) giving two way (input and output) between SignalK and seatalk network. I also tested seatalk-gpio connection with success. So far so good. Now I wonder if I can use seatalk gpio to read from seatalk and SeaTALK_tiny_usb to only send data from SignalK to seatalk network for autopilot commands only? SeaTALK_tiny_usb cannot be configured for one way communication ( and producing unnecessary echos of data), is there a possibility at SignalK serial connection such that “input only/output only/ both way” type communication setting or a way to do so ?"

sbender9 commented 2 years ago

I think this is there already there? It's about the event names.

sbender9 commented 2 years ago

On the 0183 connection page there is "Output Events", AP plugin has the same.

ckcrs commented 2 years ago

Thanks, I understand that "Output Events" is for sending SignalK data to the connection, serial (NMEA0183) , if I'm correct. My case is related sending SignalK Data to this connection while blocking/filtering out all incoming data to this connection and to SignalK from the source. Node Red input handler blocks data but path still there, path-filter plugin kind of works but both requires to configure each path to be filtered out. Actually ,I'm looking for a simple ui configuration such that serial connection can be selected either two way input/output (default) or output only ( which is my case) or input only ( may be required by someone else) Or I'm missing something if it is already in SignalK? Regards, Sancan

ckcrs commented 1 year ago

"Avoiding data loops #1567" will be a more convenient solution, since this request also related with data loops and flooding. So closing this. Thanks

ckcrs commented 1 year ago

"Avoiding data loops #1567" will be a more convenient solution, since this request also related with data loops and flooding. So closing this. Thanks

tkurki commented 1 year ago

Avoiding data loops is a much larger concept & undertaking, whereas this would be valuable on its own for ease of use. Events are....less than obvious to the casual user.