ship clock $GPZDA for Local Time and GPS NMEA each to it's own TCP port?

27 views
Skip to first unread message

RayfM

unread,
Jun 4, 2024, 5:09:44 AM6/4/24
to kplex
I have a GPS NMEA to USB converter into KPLEX/Pi and then output to a TCP port on LAN. Works perfect for several years.  I want to set the local time on 30 local Pi based Media Players using $GPZDA from the ships clock.  I see I can add another converter using USB to input the ships clock NMEA feed to KPLEX and then use filters to drop the GPS $GPZDA sentence and add in the ships clock $GPZDA and have that all output to the one TCP port.  Or I could keep the two NMEA feeds separated and output them to two different ports?  Is that correct and is either one a better idea?

Drifting slightly off the KPLEX topic, I hope to use software on the same Pi as the KPLEX to send the local time to each local Media Player using something like   "ssh ro...@192.168.x.x date --set..."    whenever local time changes and live with the fact it could lag behind a couple seconds.  If I have to I'll use a second Pi on the LAN to handle getting it's data from the NMEA TCP port connection.

I've searched a lot but if you've seen anyone doing something similar please point me in that direction.  

Grateful for any input.  --Ray
Reply all
Reply to author
Forward
0 new messages