Network Ports & Protocols¶
This document lists all network ports and protocols used by GateKeeper Conveyor hardware and services. Use this information to verify firewall rules and troubleshoot connectivity issues.
Important: IP addresses and ports vary by site. The values shown here are defaults or examples. Always verify the actual values in the site's
appsettings.json.
Port Summary¶
Hardware Communication Ports¶
| Hardware Type | Protocol | Default Port | Direction | Purpose | Notes |
|---|---|---|---|---|---|
| Cognex DataMan Camera | TCP (Telnet) | 23 | Outbound | Camera command/control | GateKeeper connects TO the camera |
| Cognex DataMan Camera (Push) | TCP | 3000 | Inbound | Barcode data from camera | Camera connects TO GateKeeper listener; port is configurable |
| Cognex Insight Camera | TCP | 8890 | Inbound | Barcode + image data from camera | Camera connects TO GateKeeper; port is configurable |
| Zebra FX9600 RFID Reader | TCP | 5084 | Outbound | RFID tag data | GateKeeper connects TO the reader |
| Arduino Portenta H7 | TCP (Modbus) | 502 | Outbound | I/O control (stack lights, reject, stop) | GateKeeper connects TO the controller |
| LattePanda Arduino | Serial USB | COM4:115200 | Local | I/O control (stack lights) | USB connection, no network port |
| Zebra DS9908R Scanner | USB (SNAPI) | N/A | Local | Barcode + RFID data | USB connection via CoreScanner SDK |
| Zebra FS40 Scanner | TCP | Verify in production | Inbound | Barcode data from scanner | Scanner connects TO GateKeeper |
Application Service Ports¶
| Service | Protocol | Default Port | Direction | Purpose | Notes |
|---|---|---|---|---|---|
| Matthews Interface | TCP | 60251 | Inbound | Production data import | Plant system connects TO GateKeeper |
| ZFL Importer | TCP | 6101 | Inbound | ZPL data for Zebra Futures Lab | External system connects TO GateKeeper |
| Camera Data Listener | TCP | 3000 | Inbound | Cognex DataMan Push mode | Configurable via CameraListenerPort |
| BarTender Print Server | HTTP | 5154 or 5159 | Outbound | Label printing commands | GateKeeper connects TO BarTender server |
Export Service Endpoints¶
| Service | Protocol | Port | Direction | Purpose | Notes |
|---|---|---|---|---|---|
| AIS Export | HTTP/HTTPS | 80/443 or 8085 | Outbound | Validation result export | URL configured per site |
| Mojix Export | HTTPS | 443 | Outbound | EPCIS event submission | chipotle.mojixretail.io |
| MWE Export | HTTP | 80 | Outbound | MotionWorks submission | Site-specific IP |
Firewall Rules Required¶
Inbound Rules (traffic coming INTO the GateKeeper PC)¶
These rules must be created in Windows Firewall on the GateKeeper PC:
| Rule Name | Port | Protocol | When Needed |
|---|---|---|---|
| GateKeeper Camera Listener | 3000 (or configured port) | TCP | Cognex DataMan Push mode |
| GateKeeper Insight Camera | 8890 (or configured port) | TCP | Cognex Insight camera |
| GateKeeper Matthews | 60251 (or configured port) | TCP | Chipotle or CargillRfid mode |
| GateKeeper ZFL Importer | 6101 | TCP | Zfl mode only |
Outbound Rules (traffic going FROM the GateKeeper PC)¶
Outbound rules are usually allowed by default. If outbound filtering is enabled, these must be allowed:
| Rule Name | Port | Protocol | When Needed |
|---|---|---|---|
| Cognex Camera Control | 23 | TCP | All Cognex DataMan sites |
| RFID Reader | 5084 | TCP | CargillRfid, Chipotle modes |
| Arduino Controller | 502 | TCP | Sites with Portenta H7 |
| AIS Export | 80, 443, or 8085 | TCP | AIS export enabled |
| Mojix Export | 443 | TCP | Mojix export enabled |
| MWE Export | 80 | TCP | MWE export enabled |
| BarTender Printing | 5154 or 5159 | TCP | Teasdale mode |
Port Details by Hardware Type¶
Cognex DataMan Cameras (Port 23 + Listener Port)¶
Used at: Hormel (Austin, Beloit, Barron), Cargill (St. Clair, Sidney, Gainesville, Fullerton)
The application connects TO the camera on port 23 for commands. In Push mode, the camera also connects back to a listener on the GateKeeper PC.
| Connection | Default | Configurable | Setting |
|---|---|---|---|
| Camera command port | 23 | Yes (in ConnectionString) | HardwareSettings[].ConnectionString |
| Push mode listener IP | 0.0.0.0 | Yes | CameraListenerIpAddress |
| Push mode listener port | 3000 | Yes | CameraListenerPort |
Troubleshooting:
- If the camera connects but no barcode data arrives in Push mode, check that the camera's Network Client is configured to send data to the GateKeeper listener IP and port.
- The CameraListenerIpAddress must be an IP address on the GateKeeper PC (not the camera's IP). Use 0.0.0.0 to listen on all interfaces.
Cognex Insight Camera (Port 8890)¶
Used at: Cargill Hersey
The camera connects TO the GateKeeper application. GateKeeper acts as a TCP server.
| Connection | Default | Configurable | Setting |
|---|---|---|---|
| Server listen address | 0.0.0.0 | Yes (in ConnectionString) | HardwareSettings[].ConnectionString |
| Server listen port | 8890 | Yes (in ConnectionString) | HardwareSettings[].ConnectionString |
Troubleshooting: - The ConnectionString must be the GateKeeper PC's IP address (or 0.0.0.0), NOT the camera's IP. - If you see "SocketException 10049", the IP address in the ConnectionString does not exist on the GateKeeper PC.
Zebra FX9600 RFID Reader (Port 5084)¶
Used at: Cargill (St. Clair, Sidney, Gainesville, Fullerton)
The application connects TO the RFID reader on port 5084.
| Connection | Default | Configurable | Setting |
|---|---|---|---|
| RFID reader port | 5084 | Yes (in ConnectionString) | HardwareSettings[].ConnectionString |
Troubleshooting:
- Verify the reader's IP address with ping.
- Port 5084 is the standard Zebra FX9600 LLRP port.
- If connection fails, check that no other application is already connected to the reader (only one connection allowed).
Arduino Portenta H7 (Port 502)¶
Used at: Cargill (St. Clair, Sidney, Gainesville, Fullerton), Hormel (Austin, Beloit)
The application connects TO the Arduino controller on port 502 (Modbus protocol).
| Connection | Default | Configurable | Setting |
|---|---|---|---|
| Controller port | 502 | Yes (in ConnectionString) | HardwareSettings[].ConnectionString |
Troubleshooting:
- Verify the controller's IP address with ping.
- If stack lights or reject mechanism do not respond, check the pin mapping in the Arduino's Configuration JSON.
Matthews Interface (Port 60251)¶
Used at: Cargill (St. Clair, Sidney, Gainesville, Fullerton)
External production system connects TO GateKeeper on this port to send production data.
| Connection | Default | Configurable | Setting |
|---|---|---|---|
| Listen port | 60251 | Yes | MatthewsPort |
| IP filter | All allowed | Yes | MatthewsAllowedIp |
Troubleshooting:
- If validation shows "No production data available", the Matthews system is not connecting.
- Check that the Matthews system is configured to send to the GateKeeper PC's IP on port 60251.
- If network security scans are triggering false validation starts, set MatthewsAllowedIp to the Matthews server's IP.
Quick Connectivity Test¶
To verify connectivity to hardware devices from the GateKeeper PC, open a command prompt and run:
If ping succeeds, the device is reachable on the network. If it fails, check: 1. Is the device powered on? 2. Are both devices on the same network/subnet? 3. Is there a firewall blocking ICMP (ping)?
Note: Some devices may block ping but still accept TCP connections. If ping fails but the device appears in the GateKeeper diagnostics panel as "Connected", the device is working correctly.