Contact for Raymarine regarding SeaTalk¹ licensing terms
Hi all! I have recently written a Linux Kernel driver for SeaTalk¹ so that I can send and receive on my SeaTalk¹ bus from SignalK. I want to attempt to get this into mainline Linux, but before I do that, I need to be sure that Raymarine won't stand in the way of me doing so. In order to do so, I want to talk to someone at Raymarine to confirm this.
2 Replies
a commendable effort!
how does it work hardware wise, i seem to remember st1 being 9 bits or something like that, a bit uncommon
It works almost exactly like https://github.com/jamesroscoe/seatalk, but uses the new Linux platform driver api so that this works on the Pi 5 too. I've also completely ripped out the decoding of the datagrams and the userspace API and use genetlink now. On my test set-up, I have a userspace daemon that converts the raw ST1 datagrams to/from ST1-over-nmea0183 and exposes a TCP-socket for nmea0183 data. That is then what SignalK connects to.
But I think I want to move to exposing a chrdev to userspace. That's easier to deal with from Signalk directly.
But now the sailing season has started, I now have some more time to work on it, and make it available for download. I guess that with the lack of response, I'll probably end-up not mainlining it, but just downstream-packaging a module for various distributions like OpenPlotter.