Warning message when I run a status check?

[J.Hernandez]

This is the message:

Conflict between OpenCPN and Signal K in the N0183 data flow over TCP 10110.



This is what my setings look like over in OpenCPN:



And what they look like in Signal K:



In addition to that I have the plugin "SignalK to N0183" enabled.

I suspect that I am getting the N0183 data sent to OpenCPN via UDP which I have also enabled and I am not getting data via TCP.

Any ideas?

[nohal]

The address in your TCP configuration is wrong, must not be 0.0.0.0 (That would be the address for listening to UDP broadcasts), but a real IP - if the source is Signal K server on the same machine probably 127.0.0.1

You should always prefer UDP wherever available though.

[J.Hernandez]

Originally Posted by nohal

The address in your TCP configuration is wrong, must not be 0.0.0.0 (That would be the address for listening to UDP broadcasts), but a real IP - if the source is Signal K server on the same machine probably 127.0.0.1

You should always prefer UDP wherever available though.

Thank you. That fixed it. I changed 0.0.0.0 to localhost and the warning is gone.

Do I understand you correctly and if I have a UDP connection going between SignalK and OpenCPN to send the N0183 data then I don't need to have the TCP connections active from Signal K to send and from OpenCPN to receive?

[nohal]

You of course do not need two connections for the same data from the same data source, why would you do that?

[J.Hernandez]

Originally Posted by nohal

You of course do not need two connections for the same data from the same data source, why would you do that?

I was following the instructions in the manual.

[nohal]

Well... If you were, this thread would not exist. I also don't see it saying that you should set up both TCP and UDP connections at the same time. But will explicitly mention it is neither needed nor desirable.

[J.Hernandez]

I stopped the TCP connections. Everything seems to be running correctly. No need to stress the little RPi if I can help it. The reason I asked is because I didn't understand the instructions.

[stevead]

From the manual:

The next section describes how to use either of the three supported protocols to connect OpenCPN to SignalK Server. Chose one of the options available for the connection that suits your use case. normally using the native Signal K protocol is the best option. In case you need the converted NMEA 0183 messages in OpenCPN (for example for some plugin without native SignalK support, UDP is usually preferred over TCP). Note that OpenCPN does not support the SignalK data format over TCP.

How could this be improved?

[J.Hernandez]

It is clearly stated. I tend to jump ahead and not read everything. My mistake.