Sylphase SDGPS
The software-defined GPS(/GNSS) toolkit
connect-INTERFACE-tcp

For each of the Interfaces there is a listen-INTERFACE-tcp node that creates a TCP server to send out a packet stream, and there is a connect-INTERFACE-tcp node that connects to a TCP server and receives the packets.

The connect-INTERFACE-tcp nodes are sources of that particular interface. The host and port can be supplied as a positional argument (in that order), so the --host and --port is not necessary.

Help

Usage:

connect-cooked-tcp [OPTION]... HOST PORT

Allowed options:

Option Description
--help produce help message
--host HOST make connection to IP address or hostname HOST
--port PORT make connection to TCP port number PORT

connect-cooked-tcp

Type signature: (->cooked)

Example

sdgps connect-cooked-tcp --host 127.0.0.1 --port 1234 ! tracker ! decoder

In this example, by connecting to the 1234 port on the localhost we can stream cooked packets for local processing. As mentioned in other places in the documentation, we cannot terminate this node chain on this node since the cooked interface has desired correlator configurations being sent backwards to the cooked source.

connect-cooked2-tcp

Type signature: (->cooked2)

Example

sdgps connect-cooked2-tcp 127.0.0.1 1234 ! decoder

By connecting to the 1234 port on the localhost we can stream cooked2 packets. Unlike the previous example, --host and --port have been left out because --host and --port are positional arguments.

connect-observables-tcp

Type signature: (->observables)

Example

sdgps connect-observables-tcp 127.0.0.1 1234 ! kf2

Here, we process the observables packets on port 1234 to get a solution using the kf2 node.

connect-raw-tcp

Type signature: (->raw)

Example

sdgps connect-raw-tcp 127.0.0.1 1234 ! write-raw-file foo.raw

Here we write the raw packets being streamed on port 1234 to a file called foo.raw

connect-solution-tcp

Type signature: (->solution)

Example

sdgps connect-solution-tcp 127.0.0.1 1234 ! write-solution-file --filename foo.sol

Here we write the solution packets being streamed on port 1234 to a file called foo.sol