Data Connections
Network on the boat is growing a bit and I noticed (duplicate) data coming into SignalK with 'wrong' ID. Let me explain: I already had a "Data Connection" configured with:
- Data Type = NMEA0183
- NMEA 0183 Source = TCP Server on 10110
This worked fine; showing the ID on the Dashboard as active and the expected data is indeed available.
Recently I added a device (router with GPS) that transmits NMEA0183 data to SignalK. For this I created a second "Data Connection" and this also works as expected. But later on I discovered the data is there now twice, from different sources.
Seems logical I guess; I should not have created a second "Data Connection" for this, right?
But now comes the question: How can I see the two different sources on the Dashboard?
3 Replies
I've looked at http://10.10.10.1:3000/documentation/setup/configuration.html?highlight=connections#set-up-data-connections but it doesn't explain anything about "NMEA 0183 Source". Neither for "ID"; but I think this is just the name shown on the dashboard?
The server configuration is really unintuitive in this case
Tcp server on 10110 meanst that the server is accepting data over tcp over connections made to the default tcp server on that port, that is normally just for outputting 0183 data
The short answer is ”don’t add tcp server as 0183 source on multiple connections”
Using this method there is no way to distinguish between different sources sending data to the server via this connection, as the tcp clients don’t have any esy to identify themselves
We could add client’s ip address in the source information 🤔
If multiple sources use same port then consider to use TAG block with s: flag which defines source.
Tagged NMEA0183 is more common in e.g. merchant marine where messages are broad/multicasted.