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 to NMEA0183/2000 with Raspberry Pi
#1
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.
________________________________________

Blog; https://pysselilivet.blogspot.com/
Reply
#2
Good work. We will also add this feature to the openplotter-gpio app and it will contain dependencies (pigpio) and port conflict management
Reply
#3
(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 .....
________________________________________

Blog; https://pysselilivet.blogspot.com/
Reply
#4
(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-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?
Reply
#5
(Yesterday, 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-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
Reply
#6
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.
Reply
#7
(8 hours ago)PaddyB Wrote: 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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)