This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
No data on TCP 10110
#6
(2021-08-09, 07:10 AM)Spidgrou Wrote: When I remove an option in the connection, called: "Suppress nmea0183 event" everything start to appear again on my port 10110

Ah, there's the problem ?
Events can be initially a bit confusing to get your head around. Maybe easier to think of it as "tags" or "channels". 
So with your miniplex, when "suppress nea0183 event" is turned off every nmea0183 sentence which comes in is given an "nmea0183" tag, then in the signalk server any sentence with a "tag" of "nmea0183" automatically gets sent out on tcp10110. SUppress that event or "tag" then the nmea sentence goes nowhere, just gets converted into signalk. 
The signalk - nmea0183 plugin creates nmea0183out events which also automatically get sent to tcp10110. 


https://github.com/SignalK/signalk-serve...tting-Data
Reply


Messages In This Thread
No data on TCP 10110 - by Spidgrou - 2021-08-08, 02:18 AM
RE: No data on TCP 10110 - by PaddyB - 2021-08-08, 09:43 AM
RE: No data on TCP 10110 - by Spidgrou - 2021-08-08, 10:46 AM
RE: No data on TCP 10110 - by PaddyB - 2021-08-08, 11:46 AM
RE: No data on TCP 10110 - by Spidgrou - 2021-08-09, 07:10 AM
RE: No data on TCP 10110 - by PaddyB - 2021-08-09, 10:49 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)