I am not seeing True Wind Angle and Speed on OpenCPN

[barcoMeCasa]

Originally Posted by nohal

Because UDP is a much better protocol for this kind of application. People use TCP because of lack of knowledge, hardware limitations or combination of both, but there is no real reason to do it and their life would be better with UDP in the majority of cases.

If Signal K server sends different NMEA 0183 data over TCP and UDP, then it is a bug in that server.

The real question here of course is why use NMEA 0183 at all here as it means double conversion of data.

TCP is being used by many thousands of signalk users by default all over with no problems, it's the way t is & not likely to change so not much point getting into a discussion about it.
In this caseit's not a bug but the user enabling a plugin to double up to send udp as well as tcp seems pointless, the default settings work fine
Seems far easier just to click a few settings in signalk to create the true wind nmea & be done with it.

[barcoMeCasa]

Originally Posted by J.Hernandez

The problem seems to be that these Derived Data is not being send to OpenCPN from SK either as SK data or N0183 data.

Have you told signalk to make an nmea sentence & send that?
In the Convert Signal K to NMEA0183 plugin >

[Hakan]

J.H...
Dashboard STW uses one three sources with this prio order:
HandleN2K_128259
SK: "navigation.speedThroughWater"
m_NMEA0183.Vhw.Knots
So any of them you would have received.

The NMEA Debug shows the source "UDP localhost:2000... $IIxxx " Whats that from?

The SK plugin "convert SK to N0183" I haven't used but it would stream by all N0183 from SK I suppose. If you haven't changed that it use to be TCP xxxxxx/Localhost port 10110

[J.Hernandez]

Originally Posted by Hakan

J.H...
Dashboard STW uses one three sources with this prio order:
HandleN2K_128259
SK: "navigation.speedThroughWater"
m_NMEA0183.Vhw.Knots
So any of them you would have received.

The NMEA Debug shows the source "UDP localhost:2000... $IIxxx " Whats that from?

The SK plugin "convert SK to N0183" I haven't used but it would stream by all N0183 from SK I suppose. If you haven't changed that it use to be TCP xxxxxx/Localhost port 10110

As for STW in SK. Yes. I am seeing 128529 and "navigation.SpeedThroughWater".

The plugin "Convert SK to N0183" should be converting the selected SK data into N0813 sentences so that I can record them with the VDR plugin. Even though I have checked the []VHW sentence, it is not being converted for unknown reasons.

As for the "UDP localhost:2000... $IIxxx " This is the source of my instruments data (Raymarine wind and paddle wheel transducer for STW).

At this point I am guessing that the "Convert SK to N0183" plugin is not working properly to converting PGN 128529 to NMEA 0183 sentence VHW.

[Hakan]

Originally Posted by J.Hernandez

At this point I am guessing that the "Convert SK to N0183" plugin is not working properly to converting PGN 128529 to NMEA 0183 sentence VHW.

To verify your connection settings enable some more sentences like RMC to see if your TCP/UDP connection to Signal K is actually working.

[J.Hernandez]

Originally Posted by Hakan

To verify your connection settings enable some more sentences like RMC to see if your TCP/UDP connection to Signal K is actually working.

All of these sentences are being passed:
$IIMWV,$IIVWR,$IIMTW,!AIVDM,$GNRMC,$GPRMC,$XXMWV,$ IIVTG,$XXHDT,$GNVTG,$GNGGA,$GNGSA,$GPGSV,$GNGLL,$I IDBT.

The one not being passed as N0183 is only STW ($-VHW).

[barcoMeCasa]

Originally Posted by J.Hernandez

All of these sentences are being passed:
$IIMWV,$IIVWR,$IIMTW,!AIVDM,$GNRMC,$GPRMC,$XXMWV,$ IIVTG,$XXHDT,$GNVTG,$GNGGA,$GNGSA,$GPGSV,$GNGLL,$I IDBT.

The one not being passed as N0183 is only STW ($-VHW).

I have a linux machine on the cloud which I just ran with sample n2k data, selected the VHW box in sigk to nmea0183 & it works OK on there >





One option to try might be a fresh install of openplotter on a spare sd card, it's known to work straight away with the default settings

[J.Hernandez]

Following the advice recieved I started from scratch and reinstalled OpenPlotter 3. Made the connections and I get the same result. STW is in the Signal K server as data coming from my sensors (NMEA2000) but it is not being forwarded to OpenCPN as a NMEA0183 sentence VHW using the N2K to N0183 convert plugin. I can see the STW value in OpenCPN dashboard while the Network 3000 connection to Signal K is up. If I disconnect that and only go on the UDP 2000 connection which carries only the translated from NMEA2000 PGNs to NMEA0183 sentences then I lose the STW value.

[barcoMeCasa]

Originally Posted by J.Hernandez

If I disconnect that and only go on the UDP 2000 connection which carries only the translated from NMEA2000 PGNs to NMEA0183 sentences then I lose the STW value.

Where did the UDP connection come into from? Out of the box openplotter opencpn is connected to the signalk server using localhost tcp port 10110, the signalk to nmea app sends data out over tcp port 10110, should be no need for a udp connection?
This is sample nmea2k data with the n2k to nmea0183 just converting to VHW, it uses navigation.speedThroughWater, I just used nore red as a quick way to look at tcp data on 10110 >



You could try opencpn with just a tcp connection to localhost port 10110 & have a look

Another place to look is the server log & look at events:nmea0183out.
Events are sort of like channels, so "channel" nmea0183out is where the n2k to nmea0183 converter sends the data, it's automatically send out on localhost tcp port 10110


Good luck, it works, there's just a setting wrong somewhere, likely that UDP port

[J.Hernandez]

Originally Posted by barcoMeCasa

Good luck, it works, there's just a setting wrong somewhere, likely that UDP port

Thank you. I have tried to send the NMEA0183 over TCP 10110 and I get the same result as when I send it via UDP 2000. I've been told UDP is better and faster and the recomended way to send NMEA0183 data. That's why I am using it.

I can clearly see "navigation.speedThroughWater" in the SignalK Data Browser and I have the check mark on the "Convert SignalK to N0183" plugin to convert that to the sentence VHM. I just look at the log from the "Convert SignalK to N0183" plugin. It is not there. I even check ALL the boxes in the plugin just in case and nothing. It's very frustrating.

[barcoMeCasa]

Originally Posted by J.Hernandez

Thank you. I have tried to send the NMEA0183 over TCP 10110 and I get the same result as when I send it via UDP 2000. I've been told UDP is better and faster and the recomended way to send NMEA0183 data. That's why I am using it.

I can clearly see "navigation.speedThroughWater" in the SignalK Data Browser and I have the check mark on the "Convert SignalK to N0183" plugin to convert that to the sentence VHM. I just look at the log from the "Convert SignalK to N0183" plugin. It is not there. I even check ALL the boxes in the plugin just in case and nothing. It's very frustrating.

UDP isn't actually the way it works, TCP is the default so probably better to stick with that. Remember this is just a sailing web forum, it might be better to ask the signalk guys themselves - https://discord.gg/T4YmSkhj

It sounds like no signalk sentences at all are being converted then? Odd, usually a good idea to restart the server each time as well.

So just to recap what I have working here, sample nmea2k data >



which gets converted by default to signalk data >



then just VHW tick in the sigk 0183 converter |



So after a restart you should see data coming in over in the dashboard?

[J.Hernandez]

Originally Posted by barcoMeCasa

So after a restart you should see data coming in over in the dashboard?

I have done EXACTLY as you described but the navigation.SpeedThroughWater does not get converted to VHW. I can see navigation.SpeedThroughWater in the Data Browser and it's being sent as SignalK data format to OpenCPN but not as NMEA0183.

[barcoMeCasa]

Originally Posted by J.Hernandez

I have done EXACTLY as you described but the navigation.SpeedThroughWater does not get converted to VHW. I can see navigation.SpeedThroughWater in the Data Browser and it's being sent as SignalK data format to OpenCPN but not as NMEA0183.

so with everything clicked in the sigk 0183 converter are other nmea0183 sentences getting converted?

[J.Hernandez]

Originally Posted by barcoMeCasa

so with everything clicked in the sigk 0183 converter are other nmea0183 sentences getting converted?

Yes. Here is a sample from the log:

Mar 09 17:20:25 2024-03-09T16:20:25.752Z @signalk/signalk-to-nmea0183 $IIMWV,265.45,R,3.96,M,A*32
Mar 09 17:20:25 2024-03-09T16:20:25.752Z @signalk/signalk-to-nmea0183 $IIVWR,94.55,L,7.70,N,3.96,M,14.26,K*57
Mar 09 17:20:25 2024-03-09T16:20:25.861Z @signalk/signalk-to-nmea0183 $IIMWV,265.45,R,3.96,M,A*32
Mar 09 17:20:25 2024-03-09T16:20:25.861Z @signalk/signalk-to-nmea0183 $IIVWR,94.55,L,7.70,N,3.96,M,14.26,K*57
Mar 09 17:20:25 2024-03-09T16:20:25.973Z @signalk/signalk-to-nmea0183 $IIDBT,18.9,f,5.75,M,3.1,F*14
Mar 09 17:20:25 2024-03-09T16:20:25.974Z @signalk/signalk-to-nmea0183 $IIMWV,265.45,R,3.96,M,A*32
Mar 09 17:20:25 2024-03-09T16:20:25.974Z @signalk/signalk-to-nmea0183 $IIVWR,94.55,L,7.70,N,3.96,M,14.26,K*57
Mar 09 17:20:25 2024-03-09T16:20:25.976Z @signalk/signalk-to-nmea0183 $IIMTW,15.0,C*17
Mar 09 17:20:26 2024-03-09T16:20:26.042Z @signalk/signalk-to-nmea0183 $GPRMC,162025,A,3933.9074,N,00238.0786,E,0.0,0.0,090324,,E*56
Mar 09 17:20:26 2024-03-09T16:20:26.043Z @signalk/signalk-to-nmea0183 $IIVTG,0.00,T,0.00,M,0.05,N,0.09,K,A*38
Mar 09 17:20:26 2024-03-09T16:20:26.043Z @signalk/signalk-to-nmea0183 $GPGGA,162025,3933.9074,N,00238.0786,E,1,12,0.7,4.6,M,0.0,M,,*76
Mar 09 17:20:26 2024-03-09T16:20:26.044Z @signalk/signalk-to-nmea0183 $GPGLL,3933.9074,N,00238.0786,E,172025.020,A*35
Mar 09 17:20:26 2024-03-09T16:20:26.046Z @signalk/signalk-to-nmea0183 $IIZDA,162026.020,09,03,2024,,*4C
Mar 09 17:20:26 2024-03-09T16:20:26.054Z @signalk/signalk-to-nmea0183 $IIMWV,265.45,R,3.96,M,A*32
Mar 09 17:20:26 2024-03-09T16:20:26.055Z @signalk/signalk-to-nmea0183 $IIVWR,94.55,L,7.70,N,3.96,M,14.26,K*57
Mar 09 17:20:26 2024-03-09T16:20:26.149Z @signalk/signalk-to-nmea0183 $IIMWV,265.45,R,3.96,M,A*32
Mar 09 17:20:26 2024-03-09T16:20:26.150Z @signalk/signalk-to-nmea0183 $IIVWR,94.55,L,7.70,N,3.96,M,14.26,K*57
Mar 09 17:20:26 2024-03-09T16:20:26.245Z @signalk/signalk-to-nmea0183 $IIMWV,261.95,R,3.96,M,A*3B
Mar 09 17:20:26 2024-03-09T16:20:26.246Z @signalk/signalk-to-nmea0183 $IIVWR,98.05,L,7.70,N,3.96,M,14.26,K*5E
Mar 09 17:20:26 2024-03-09T16:20:26.357Z @signalk/signalk-to-nmea0183 $IIMWV,261.95,R,3.96,M,A*3B

[barcoMeCasa]

Great, getting somewhere!! So opencpn should see those as well if it is connected to tcp port 10110.

Bit out of my depth here but the code to create the VHW sentence has magnetic variation & heading as well, not sure but they might be needed??

keys: [
      'navigation.headingTrue',
      'navigation.magneticVariation',
      'navigation.speedThroughWater'

Do you have navigation.headingTrue & navigation.magneticVariation in the data browser as well?

Might be a red herring though....