-
I am using a LTE CAT-M modem to receive GPS NMEA data. $GLGSV,2,1,08,74,66,078,27,66,16,334,14,73,22,109,40,75,46,313,26,171 How can I "pipe" this terminal output into Signal-K? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
There's something called "execute provider" that spawns a command and uses its stdout as the input to a SK Server "piped provider", a sequence of processing steps. You'll need to configure it by manually editing your
Naturally use your command instead of the echo example and no need for the ...but the actual data that you included is not valid, for one thing only the last sentence has checksum. You may get away with it by configuring the sk connection to ignore checksums. |
Beta Was this translation helpful? Give feedback.
-
"qmicli -p -d /dev/cdc-wdm0 --loc-follow-nmea --client-cid=1 > /dev/udp/127.0.0.1/2947 &" will stream via udp to port 2947. I have setup a new data connection in Signal-K: Unfortunately this setup does not generate any Connection activity on the dashboard. The Signal-K log output on "signalk-server:events:NO_EMITTER_ID:serverevent" shows: Any hints how to move forward? |
Beta Was this translation helpful? Give feedback.
Got it. I missed (to mention) the point that my Signal-K is running in docker.
After forwarding the port (Port: 2947:2947/udp) to the container, I can now receive the NMEA 0183 sentences.