
Pathfinder DVL Guide
April
2018
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Page 21
In this next example, the computer’s IP address is 192.168.1.2. Therefore, set the UDP IP address on the
web portal to be the same. You can now simply open a UDP stream to listen to that
PD0
feed simply by us-
ing the port number, here in our example 1034.
This example also includes a
PD6
stream over UDP on port 1037 that points to the computer’s IP address
192.168.1.2 – here is the snapshot from listening to this stream using TRDI Toolz:
UDP is a connection-less protocol. Therefore, UDP packets can be lost in an unreliable or
highly congested network.
The Ethernet portion of the DVL acts as a server on (potentially) several fronts:
1. Command/Control of the DVL happens via the TCP port on the command interface (default port
1033). The DVL acts as a server and will accept a connection from any IP on the subnet.
2. Configuration of the
PD
X
outputs and general IP config happens via the webpage (default IP
192.168.1.100, port 80) (acts as HTTP server).
3.
PD
X
output happens on one of several ports:
a.
Each
PD
X
(
PD0
,
PD4
,
PD5
,
PD6
, and
PD13
) can be configured to be output on a separate
port.
b.
Each can be configured to output via TCP or UDP.
c.
TCP connections can be made from any address – you will connect to the same IP address
as the webpage, and on the specified port. For example, by default only
PD0
is enabled.
One would connect a TCP client to 192.168.1.100 at port 1034. The DVL acts as a server
and will accept a connection from any IP.
d. UDP connections will be broadcast by the Ethernet module to the specified Address and
port. By default, these broadcast to 192.168.1.1 on ports 1034 through 1038. For example,
one could configure
PD4
to output on UDP, to IP 192.168.1.1 on port 1035, then one would
need a UDP client on a machine at address 192.168.1.1 listening to port 1035. One can