Q: What TCP or UDP ports are used by NaviPac/Helmsman' Display and NaviScan? We want to get an overview of the load we are putting on the network and plan the port allocations.


A: NaviPac and NaviScan are using a lot of TCP/IP and UDP/IP ports on the the internal address (127.0.0.1).

The ports can all be changed in NAVIPAC.INI if required.

Basically it is recommended to stick to ports above 10.000 if possible.


NaviPac
Processes with the internal port they use: 


Port
NaviPac Remote HMD connection
(from client: HMD ((RemAcc), XYZCal, etc)
HELMSMAN_SOCKETPORT=4884
TCP: 4884
NaviPac LogData (LocalAccess) connection
LOGDATA_SOCKETPORT=4885
TCP: 4885

DIO2RADA_SOCKET=4886

NaviPac Scene Server connection
SERVER_DATA_SOCKETPORT=4887
TCP: 4887, 7913
NaviPac kernel connection
(from RemAcc, USBLfix, etc.)
KERNEL_SOCKETPORT=4888
TCP: 4888
NaviPac RemAcc connection
(from Kernel)
KERN2RA_SOCKET2=4889

For 3D display the communication between the SceneServer (NaviPac) and the 3D SW uses two ports: 3D

UDP: 9800
3D Display via SceneServer

TCP: 12345
ASCII display of depth in HD

TCP: 2200
HMD Services
(EivaMaster.exe EivaRemote.exe)

HTTP, TCP: 31231
UDP interfaces between sensors/TimeBox and NaviPac/NaviScan.


These ports are configured by the operator.




NaviScan
Processes with the internal port they use:


NaviScan 

2000
NaviScan center depth
ASCII display of depth in HD
UDP: 5999
NaviScan DTM (reduced MBE)
Real-time DTM (from NaviScan to HD)
UDP: 2300
NaviScan NED exporter

.TCP/UDP:  2301
NaviScan SS DTM

TCP/UDP:  2302
NaviScan PanGeo scan writer

TCP/UDP:  2303
NaviScan NaviModel scan writer

TCP/UDP: 2304
NaviScan HMD
TCP: 2305
Real-time DTM (From NaviScan to Helmsman's Display)

Either TCP: 2100 or UDP: 2300