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
Seatalk detection fail pattern
I’m running the lastest version of openplotter 3 on a raspberry pi 4 under 64b
I have been noticing since months that sometimes my Seatalk instruments are nos being detected. This are connected via an optocoupler. No hat is used. 
After many months and reinstalls I have detected a pattern.

The times Seatalk instruments are not detected are when I start either signalk or Kip before letting the boot process end completely. In these cases the only solution I found is to reboot. 

But when I way a few minutes after booting, with Opencpn with auto run for example, if enough time has passed signalk will detect Seatalk no matter if it’s turn on before booting or even after starting signalk

Any thoughts?

Messages In This Thread
Seatalk detection fail pattern - by Pantera - 2024-05-11, 11:46 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)