Skip to content

Commit

Permalink
Document multiple UDP ports
Browse files Browse the repository at this point in the history
  • Loading branch information
@carlesfernandez
carlesfernandez committed Sep 12, 2024
1 parent adc54e8 commit dbfe351
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions _sp-blocks/12-pvt.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar:
nav: "sp-block"
toc: true
toc_sticky: true
last_modified_at: 2023-10-05T07:54:02+02:00
last_modified_at: 2024-09-12T07:54:02+02:00
---

The _PVT_ block is the last one in the GNSS-SDR flow graph. Hence, it acts as a
Expand Down Expand Up @@ -1165,7 +1165,7 @@ standard and precise positioning. It accepts the following parameters:
| `dump_mat` | [`true`, `false`]. If `dump=true`, when the receiver exits it can convert the ".dat" file stored by this block into a ".mat" file directly readable from Matlab and Octave. If the receiver has processed more than a few minutes of signal, this conversion can take a long time. In systems with limited resources, you can turn off this conversion by setting this parameter to `false`. It defaults to `true`, so the ".mat" file is generated by default if `dump=true`. | Optional |
| `enable_monitor` | [`true`, `false`]: If set to `true`, the PVT real-time monitoring port is activated. This feature allows streaming the internal parameters and outputs of the PVT block to local or remote clients over UDP. The streamed data members (28 in total) are the same ones that are included in the binary dump. It defaults to `false`. | Optional |
| `monitor_client_addresses` | Destination IP address(es) of the real-time monitoring port. To specify multiple clients, use an underscore delimiter character ( `_` ) between addresses. As many addresses can be added as deemed necessary. Duplicate addresses are ignored. It defaults to `127.0.0.1` (localhost). | Optional |
| `monitor_udp_port` | Destination UDP port number of the real-time monitoring port. Must be within the range from `0` to `65535`. Ports outside this range are treated as `0`. The port number is the same for all the clients. It defaults to `1234`. | Optional |
| `monitor_udp_port` | Destination UDP port number of the real-time monitoring port. Must be within the range from `0` to `65535`. Ports outside this range are treated as `0`. The port number is the same for all the clients. It defaults to `1234`. To specify multiple ports, use an underscore delimiter character ( `_` ) between ports. <span style="color: orange">The multi-port feature is only present in the `next` branch of the upstream repository, and will be present in the next stable release.</span> | Optional |
| `enable_monitor_ephemeris` | [`true`, `false`]: If set to `true`, the PVT real-time monitoring port streams ephemeris data to local or remote clients over UDP. It defaults to `false`. | Optional |
| `monitor_ephemeris_client_addresses` | Destination IP address(es) of the real-time monitoring port for ephemeris data. To specify multiple clients, use an underscore delimiter character ( `_` ) between addresses. As many addresses can be added as deemed necessary. Duplicate addresses are ignored. It defaults to `127.0.0.1` (localhost). | Optional |
| `monitor_ephemeris_udp_port` | Destination UDP port number of the real-time monitoring port for ephemeris data. Must be within the range from `0` to `65535`. Ports outside this range are treated as `0`. The port number is the same for all the clients. It defaults to `1234`. | Optional |
Expand Down

0 comments on commit dbfe351

Please sign in to comment.