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
OpenCPN crashes, because of a problem with a data connection in Signal K
#1
OpenCpn crashes only when underway and not when at anchor or moored.

I think I have the issue narrowed down to the following connection error in SignalK: qa207
2026-05-11T06:50:10.938Z: Error: No such file or directory, cannot open /dev/ttyOP_qa207

However after that the connection is ok and my Kip dashboard runs fine.

the strange thing is that I have not changed anything in the hardware or in the connections. I have updated all the software to the latest versions. last season everything ran fine during 7 months of full time use.

System:
Raspberry Pi 4 with an SSD
Quark-Elec A207 (provides GPS, AIS and Seatalk data via USB)
SignalK 2.27
OpenCPN 5.14.0


attached shots of the connection settings           Attached SignalK server log


Attached Files
.txt   serial connection error.txt (Size: 5.25 KB / Downloads: 20)
Reply
#2
(2026-05-15, 08:17 AM)Windhoos Wrote: OpenCpn crashes only when underway and not when at anchor or moored.

I think I have the issue narrowed down to the following connection error in SignalK: qa207
2026-05-11T06:50:10.938Z: Error: No such file or directory, cannot open /dev/ttyOP_qa207

However after that the connection is ok and my Kip dashboard runs fine.

the strange thing is that I have not changed anything in the hardware or in the connections. I have updated all the software to the latest versions. last season everything ran fine during 7 months of full time use.

System:
Raspberry Pi 4 with an SSD
Quark-Elec A207 (provides GPS, AIS and Seatalk data via USB)
SignalK 2.27
OpenCPN 5.14.0


attached shots of the connection settings Attached SignalK server log
A couple of points - unless I am mistaken this appears to be a problem with OpenCPN and not OpenPlotter so you may get a better response on the OpenCPN forum. Secondly, does enabling logging on that connection reveal any more useful information?
Edit - I see you have already posted this on the OpenCPN forum.
Reply
#3
(2026-05-15, 08:17 AM)Windhoos Wrote: OpenCpn crashes only when underway and not when at anchor or moored.

I think I have the issue narrowed down to the following connection error in SignalK: qa207
2026-05-11T06:50:10.938Z: Error: No such file or directory, cannot open /dev/ttyOP_qa207

However after that the connection is ok and my Kip dashboard runs fine.

the strange thing is that I have not changed anything in the hardware or in the connections. I have updated all the software to the latest versions. last season everything ran fine during 7 months of full time use.

System:
Raspberry Pi 4 with an SSD
Quark-Elec A207 (provides GPS, AIS and Seatalk data via USB)
SignalK 2.27
OpenCPN 5.14.0


attached shots of the connection settings Attached SignalK server log

That error suggests the server can't see that connection? 

Some things to try >
First it would be worth checking what is in the openplotter serial app, that's what creates the /dev/ttyOP_qa207
In a terminal try 
ls /dev
you should see /dev/ttyOP_qa207 and probably something like /dev/ttyUSB0
If it's there try
cat /dev/ttyOP_qa207
That should show the data coming in from the quark. 
cat /dev/ttyUSB0 (or whatever it is, you can turn it off, have a look then turn it on again & see what is new in ls /dev)

That would be a start anyway, if there are messages coming in you can copy one and paste it into signalk server/data fiddler
http://10.42.0.1:3000/admin/#/serverConf...atafiddler
See what it makes of it. 

Another thing to try, add a connection in opencpn to tcp localhost 10110
Atm looks like all that is going into opencpn is signalk messages, with default settings all nmea0183 going into the server gets sent straight back out again on port 10110 so have a listen on there as well in opencpn, see what is coming in. Press keyboard key 'e' should show everything coming in.

Good luck! Big Grin
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)