SeaTalk 1 to NMEA0183/2000 with Raspberry Pi

[MatsA]

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-serve...k(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.

[Sailoog]

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

[MatsA]

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 .....

[abarrow]

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-serve...k(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?

[PaddyB]

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-serve...k(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-parse...ks/seatalk

[Sailoog]

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
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
Si algú es troba a Catalunya o voltants i té un dispositiu Seatalk1, hi puc enviar un conjunt per provar-ho.

[abarrow]

Signalk server creates siganlk data from $STALK sentences. 
https://github.com/SignalK/signalk-parse...ks/seatalk

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

[MatsA]

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

[abarrow]

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?

[PaddyB]

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-parse...est/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