2024-05-11, 11:46 PM
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?
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?