Sylphase SDGPS
The software-defined GPS(/GNSS) toolkit
|
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.
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 |
Type signature: (->cooked)
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.
Type signature: (->cooked2)
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.
Type signature: (->observables)
Here, we process the observables packets on port 1234 to get a solution using the kf2 node.
Type signature: (->raw)
Here we write the raw packets being streamed on port 1234 to a file called foo.raw
Type signature: (->solution)
Here we write the solution packets being streamed on port 1234 to a file called foo.sol