OpenMarine
SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - Printable Version

+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: How I did it (https://forum.openmarine.net/forumdisplay.php?fid=6)
+--- Thread: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi (/showthread.php?tid=2820)

Pages: 1 2 3


SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - MatsA - 2020-08-05

Just a heads up that Seatalk 1, as input, to a Pasberry Pi GPIO now is a standard connection in SignalK.

Documentation is found here https://github.com/SignalK/signalk-server-node/blob/master/Seatalk(GPIO).md

A co-operation with original Python code/idea from @glowntiger, SignalK implementation by @tkurki and documentation, tests, and minor Python changes by me.


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - Sailoog - 2020-08-05

Good work. We will also add this feature to the openplotter-gpio app and it will contain dependencies (pigpio) and port conflict management


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - MatsA - 2020-08-06

(2020-08-05, 07:52 PM)Sailoog Wrote: Good work. We will also add this feature to the openplotter-gpio app and it will contain dependencies (pigpio) and port conflict management

Thanks ! OK, then it will be even easier .....


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - abarrow - 2020-08-06

(2020-08-05, 07:48 PM)MatsA Wrote: Just a heads up that Seatalk 1, as input, to a Pasberry Pi GPIO now is a standard connection in SignalK.

Documentation is found here https://github.com/SignalK/signalk-server-node/blob/master/Seatalk(GPIO).md

A co-operation with original Python code/idea from @glowntiger, SignalK implementation by @tkurki and documentation, tests, and minor Python changes by me.

I was looking at the code on this, and it appears that it is just taking the incoming SeaTalk and converting it to $STALK strings. Is it doing other interpretation of the incoming SeaTalk stream?


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - PaddyB - 2020-08-07

(2020-08-06, 09:45 PM)abarrow Wrote:
(2020-08-05, 07:48 PM)MatsA Wrote: Just a heads up that Seatalk 1, as input, to a Pasberry Pi GPIO now is a standard connection in SignalK.

Documentation is found here https://github.com/SignalK/signalk-server-node/blob/master/Seatalk(GPIO).md

A co-operation with original Python code/idea from @glowntiger, SignalK implementation by @tkurki and documentation, tests, and minor Python changes by me.

I was looking at the code on this, and it appears that it is just taking the incoming SeaTalk and converting it to $STALK strings. Is it doing other interpretation of the incoming SeaTalk stream?

Signalk server creates siganlk data from $STALK sentences. 
https://github.com/SignalK/signalk-parser-nmea0183/tree/master/hooks/seatalk


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - Sailoog - 2020-08-07

We are working in a simple board with a waterproof case to convert Seatalk1 using this method but we have a big problem, we have not any Seatalk1 device Smile
If someone is in Catalonia or surroundings and has a Seatalk1 device I can send a set to try.
-----------------------------------------------------------------------------------------------------------------------------------------------
Estem treballant en una senzilla placa amb una petita caixa estanca per convertir Seatalk1 mitjançant aquest mètode, però tenim un gran problema, no tenim cap dispositiu Seatalk1 Smile
Si algú es troba a Catalunya o voltants i té un dispositiu Seatalk1, hi puc enviar un conjunt per provar-ho.


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - abarrow - 2020-08-07

(2020-08-07, 08:45 AM)PaddyB Wrote: Signalk server creates siganlk data from $STALK sentences. 
https://github.com/SignalK/signalk-parser-nmea0183/tree/master/hooks/seatalk

Ahhh, now I see it! Clever file naming ;-) Thanks for the pointer.


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - MatsA - 2020-08-19

Signal K version 1.33 is now released with, among other things, 2 bug fixes for the ST1 pgm. Thanks to @glowntiger and @Sailoog.


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - abarrow - 2020-08-19

Is there a way for this program to use input other than GPIO? My SeaTalk to NMEA 0183 converter sends out NMEA strings, but is also sends $STALK strings. Can SignalK use those?

Sorry to ask the same question twice, I'm just not seeing the evidence that this is happening. Is the talker ID "ST" for these keys?


RE: SeaTalk 1 to NMEA0183/2000 with Raspberry Pi - PaddyB - 2020-08-20

(2020-08-19, 09:16 PM)abarrow Wrote: Is there a way for this program to use input other than GPIO? My SeaTalk to NMEA 0183 converter sends out NMEA strings, but is also sends $STALK strings. Can SignalK use those?

Sorry to ask the same question twice, I'm just not seeing the evidence that this is happening. Is the talker ID "ST" for these keys?

Signalk should decode STALK messages, just tried a few examples from here though depth units looked odd>
https://github.com/SignalK/signalk-parser-nmea0183/blob/master/test/ALK.js

Send as UDP from node-red to a signalk UDP connection.

Tye depth & STW I tried showed up in opencpn dashboard via signalk, though the logbook seems to still need NMEA