OpenMarine

I have OpenPlotter running on a Pi 5 with a McArthur HAT.  When I output OpenCPN course data to my SignalK server over UDP, the data browser page crashes.  A few data lines will start to load when the page is opened but then it will say "Something went wrong."

OpenCPN Version: 5.12.4
SignalK Version: 2.19.0

The OpenCPN connection options are: 
Network
UDP
NMEA 0183
host: localhost
port: 10111
description: OpenCPNNavOut
Output on this port
APB bearing precision x.x
Transmit sentences: APB,RMB,XTE

If I remove the OpenCPN connection and restart the SignalK server, the data browser loads fine.  There is some bit of OpenCPN data that is making the data browser have a fit.

Joshua

Same problem here but with avnav. Data browser works just fine when you select raw data I suppose.

This seems to be a signalk issue and is being discussed on the signalk discord server

My culprit are these two lines 
[attachment=3631]

(2026-01-05, 09:53 PM)tobias.e Wrote: [ -> ]Same problem here but with avnav. Data browser works just fine when you select raw data I suppose.

This seems to be a signalk issue and is being discussed on the signalk discord server

My culprit are these two lines 

Thanks, Tobias.  I never saw that "Raw Values" slider and that has allowed me to at least load the data.  I have those two notifications as well.  It seems as though everything works apart from that glitch so the system is still useable.

Joshua

I found a similar issue that only started a few months ago and what was happening was that I had setup a connection to receive data from Signal K and a connection to send data from OCPN to Signalk (same as you state above), same sentences as you. what I found was that SignalK was sending the APB, RMB and XTE sentences back to OCPN and creating a loop. After a few mins everything would crash. You could see the issue if you go to the dashboard page and look at "Total server Signal K throughput (deltas/second)" I was seeing thousands on deltas/second.

the fix is to exclude the same 3 sentences on the SignalK to OpenCPN side.

2.19.1 may have a solution for this?

Yes,  no more problems after the update 
[attachment=3632]

Working here as well.