Required Ports

The table below lists the ports used by the following:

Use this information to decide whether you or your network administrator needs to open network ports and to understand the traffic that a sensor system will produce over a network.

Ports used by GoPxL
Port Data Packet Protocol Description

80

TCP

GoPxL web port for GoPxL GUI.

Sensors and GoMax NX: All devices use this port.

For GoPxL running on a PC: Use port 8100; for more information, see below.

502

TCP

Used by the GoPxL Modbus protocol as the listener port.

2222

 UDP

Used by the EtherNet/IP protocol for implicit messaging.

3192

TCP

FireSync physical sensor upgrade port.

3194

TCP

FireSync physical sensor health port.

3320

 UDP

GoPxL discovery protocol server listener port

3500

 UDP

GoPxL Remote Procedure Call port.

3600 TCP

GoPxL control port.

Physical sensors and GoMax NX: All devices use this port.

GoPxL running on a PC: By default, the first PC instance starts at this port number, and subsequent instances are offset (for example, 3600, 3620, and so on). You can set custom values in GoPxL Manager. For more information, see Running GoPxL on a Windows PC.
3601 TCP

Gocator Data Protocol (GDP) port.

Physical sensors and GoMax NX: All devices use this port.

GoPxL running on a PC: This port is offset from the control port by +1 (for example, 3601, 3621, and so on).

8080

TCP

Default accelerated sensor web server port number.
8100  

GoPxL web port for GoPxL GUI for PC instances of GoPxL. (Sensors and GoMax NX units use port 80.)

By default, the first PC instance starts at this port number, and subsequent instances are offset (for example, 8100, 8120, and so on). You can set custom values in GoPxL Manager. For more information, see Running GoPxL on a Windows PC.

8190

TCP

Used by GoPxL Ethernet for default ASCII control, data, and health port. Actual ports can be configured by the user.

44818

TCP and UDP

Used by the GoPxL EtherNet/IP protocol as a UDP and TCP listener port for explicit messaging.