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 1 on Raspberrry Pi 5 working
#1
Information 
Thanks to Adrian (Wegmatt) who did some excellent coding work, we now have Seatalk 1 up and running on Raspberry Pi 5.

To use it on OpenPlotter v4.x.x, make sure you have at least these versions installed:
  • Signal K sever 2.11.0
  • openplotter-signalk-installer 4.2.0
  • openplotter-gpio 4.2.10

The Seatalk 1 connector on the MacArthur HAT should now also work fine on the Raspberry Pi 5: https://macarthur-hat-documentation.read...atalk.html

Post here any issue please.
Reply
#2
(2024-09-01, 05:08 PM)Sailoog Wrote: Thanks to Adrian (Wegmatt) who did some excellent coding work, we now have Seatalk 1 up and running on Raspberry Pi 5.

To use it on OpenPlotter v4.x.x, make sure you have at least these versions installed:
  • Signal K sever 2.10.0
  • openplotter-signalk-installer 4.2.0
  • openplotter-gpio 4.2.8

The Seatalk 1 connector on the MacArthur HAT should now also work fine on the Raspberry Pi 5: https://macarthur-hat-documentation.read...atalk.html

Post here any issue please.

Awesome Job Guys!!

I was so happy to hear this, I went and installed my RPi5 on the boat:

Reply
#3
ATTENTION an update to the latest kernel broke Seatalk1 on Raspberry Pi 5: https://github.com/SignalK/signalk-server/issues/1788

It has an easy fix but it has to be applied to new versions of the Signal K server and the openplotter-gpio app. We will publish here when it is solved.
Reply
#4
Updating to SK 2.11 fixed the issue.
Thank you
- SV Haimana
Reply
#5
Also updated openplotter-gpio to fix the same issue in digital and pulses features.

Make sure you have these apps updated:
  • Signal K sever 2.11.0
  • openplotter-signalk-installer 4.2.0
  • openplotter-gpio 4.2.10
Reply
#6
(2024-09-13, 04:55 PM)Sailoog Wrote: Also updated openplotter-gpio to fix the same issue in digital and pulses features.

Make sure you have these apps updated:
  • Signal K sever 2.11.0
  • openplotter-signalk-installer 4.2.0
  • openplotter-gpio 4.2.10

New user, sorry to bother you but, in my case, the Seatalk 1 to Signal K connection is not working doing a fresh installation on a Raspberry Pi 5 with:

Signal K Server version 2.12.0
Signal K Installer version 4.2.0
OpenPlotter GPIO 4-2-10

I believe I have done everything by the book, in fact if I use a small python script I am able to see a nice stream of Seatalk messages coming through my pin 4

In the Signal K Dashboard I can see this error message:

Traceback (most recent call last) File "<string>", line 299, in <module> ValueError: invalid literal for int()with base 10:


Any idea?

Thanks in advance.
Reply
#7
Are you using Raspberry OS or an OpenPlotter image?

Useful: https://demo.signalk.org/documentation/s...atalk.html
Reply
#8
(2024-12-18, 07:49 PM)Sailoog Wrote: Are you using Raspberry OS or an OpenPlotter image?

Useful: https://demo.signalk.org/documentation/s...atalk.html

I got the latest OpenPlotter image from the Open marine website and did a fresh installation.
Reply
#9
To be absolutely sure about my setup I downloaded an Openplotter V3 image and installed it on a Raspberry Pi 3.

With the same optocoupler wiring I was able to connect my seatalk instruments to the Signal K server at first try.

So I suppose the problem must be something related to the combination Openplotter V4 + Raspberry 5.

Thanks for your interest.
Reply
#10
After checking with the developers in their Discord channel it seems that there is a bug: the default value of the GPIO pin in the Data Connection setup interface is 4. If you dont change it there is a problem in the configuration and you get errors.

You must change to a different GPIO pin number, for example 5, save the change and restart Signal K.

Then change again to pin 4, save and restart, and voilá!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)