# Protocols

> The protocols the edge gateway runs, by vendor, with the default port and which ones support a connection test, browsing and discovery.

Source: https://proxus.io/docs/reference/protocols

This list is the set of protocols the edge gateway runs, the same set the device setup wizard offers. Protocol
names appear here as they do in the hub.

## What the columns mean

- **Port when empty**: the port the gateway uses when you leave **Port** empty. "Enter it" means the protocol has no
  usual port and the device's port must be typed in.
- **Test**: the wizard's **Test the connection** works for every protocol on this page. The gateway connects to
  the address, opens a protocol session and, if you added tags, reads them once.
- **Browse**: the protocol can list the device's values for you (**From the device** in the wizard's tag step).
- **Discovery**: the wizard can search the network for servers of this protocol (**Server discovery**).
- **Over TCP** in a name means a serial protocol carried over TCP, through a serial device server or a converter.
  Proxus does not open serial (COM) ports directly.

## Open standards

| Protocol | Port when empty | Browse | Discovery | Notes |
| --- | --- | --- | --- | --- |
| **OPC UA** | from the endpoint URL (`opc.tcp://server:4840`) | Yes, folder by folder | Yes | Discovery tries `opc.tcp` 4840 and 53530 and `opc.https` 53443 (`[Browse] OpcUaDiscoveryPorts`). Server certificates are trusted in the hub. See [OPC UA](https://proxus.io/docs/connect/devices/opc-ua). |
| **Modbus TCP** | 502 | No | No | Datasheet numbers such as `40001` are converted for you. |
| **Modbus RTU Over TCP** | 502 | No | No | |
| **Modbus ASCII Over TCP** | 502 | No | No | |
| **MTConnect** | enter it | Yes | Yes | An MTConnect agent over HTTP. Discovery tries ports 5000, 5001, 5005, 5006 and 7000 (`[Browse] MtConnectDiscoveryPorts`). See [MTConnect](https://proxus.io/docs/connect/devices/mtconnect). |
| **SNMP** | 161 (UDP) | Yes | No | |
| **Simulator** | none | No | No | Values generated on the gateway, for trying pipelines, dashboards and rules without a device. See [Simulator](https://proxus.io/docs/connect/devices/simulator). |

## Siemens

| Protocol | Port when empty | Browse | Discovery | Notes |
| --- | --- | --- | --- | --- |
| **Siemens S7-1500** | 102 | No | No | The wizard shows one **Siemens S7** card with a switch for the CPU family. The test also reads the CPU's order number. |
| **Siemens S7-1200** | 102 | No | No | |
| **Siemens S7-300** | 102 | No | No | |
| **Siemens S7-400** | 102 | No | No | |
| **Siemens S7-200 Smart** | 102 | No | No | |
| **Siemens S7-200** | 102 | No | No | |
| **Siemens PPI Over TCP** | enter it | No | No | |

## Rockwell Automation

| Protocol | Port when empty | Browse | Discovery | Notes |
| --- | --- | --- | --- | --- |
| **Allen Bradley** | 44818 | Yes | No | ControlLogix and CompactLogix (EtherNet/IP, CIP). Browsing lists the controller's tags. |
| **Allen Bradley MicroCip** | 44818 | No | No | |
| **Allen Bradley PCCC** | 44818 | No | No | |
| **Allen Bradley SLC** | 44818 | No | No | |

## Mitsubishi Electric

| Protocol | Port when empty | Browse | Discovery |
| --- | --- | --- | --- |
| **Mitsubishi Melsec MC** | enter it | No | No |
| **Mitsubishi Melsec MC ASCII** | enter it | No | No |
| **Mitsubishi Melsec MC R** | enter it | No | No |
| **Mitsubishi Melsec A1E** | enter it | No | No |
| **Mitsubishi Melsec A1E ASCII** | enter it | No | No |
| **Mitsubishi Melsec A3C Over TCP** | enter it | No | No |
| **Mitsubishi Melsec CIP** | 44818 | No | No |
| **Mitsubishi Melsec FX Links Over TCP** | 485 | No | No |
| **Mitsubishi Melsec FX Serial Over TCP** | enter it | No | No |

## Omron

| Protocol | Port when empty | Browse | Discovery |
| --- | --- | --- | --- |
| **Omron FINS** | 9600 | No | No |
| **Omron CIP** | 44818 | No | No |
| **Omron Host Link Over TCP** | enter it | No | No |
| **Omron Host Link C Mode Over TCP** | enter it | No | No |

## Other PLC vendors

| Protocol | Port when empty | Browse | Discovery |
| --- | --- | --- | --- |
| **Beckhoff ADS** | enter it: left empty, the gateway uses 851, which is not the ADS TCP port (usually 48898) | No | No |
| **Delta TCP** | 502 | No | No |
| **Delta Serial Over TCP** | 502 | No | No |
| **Delta Serial ASCII Over TCP** | 502 | No | No |
| **FATEK Program Over TCP** | enter it | No | No |
| **Fuji SPH** | 18245 | No | No |
| **Fuji SPB Over TCP** | enter it | No | No |
| **GE SRTP** | 18245 | No | No |
| **Inovance TCP** | 502 | No | No |
| **Inovance Serial Over TCP** | 502 | No | No |
| **Keyence MC** | enter it | No | No |
| **Keyence MC ASCII** | enter it | No | No |
| **Keyence Nano Serial Over TCP** | 8501 | No | No |
| **LSIS XGB Fast Ethernet** | 2004 | No | No |
| **LSIS XGB Cnet Over TCP** | 2004 | No | No |
| **LSIS XGK Fast Ethernet** | 2004 | No | No |
| **MegMeet TCP** | 502 | No | No |
| **MegMeet Serial Over TCP** | 502 | No | No |
| **Panasonic MC** | enter it | No | No |
| **Panasonic Mewtocol Over TCP** | enter it | No | No |
| **Toyo PUC** | enter it | No | No |
| **Vigor Serial Over TCP** | enter it | No | No |
| **XINJE TCP** | 502 | No | No |
| **XINJE Serial Over TCP** | 502 | No | No |
| **XINJE Internal** | 502 | No | No |
| **YASKAWA Memobus TCP** | 502 | No | No |
| **Yokogawa Link TCP** | enter it | No | No |
| **Freedom TCP** | enter it | No | No |

Since 2.0.0, **Mitsubishi Melsec A1E ASCII** devices use the A1E ASCII protocol (before, they could not connect),
and **XINJE TCP** and **XINJE Serial Over TCP** each use their own driver (before, the two were swapped). No setting
change is needed.

## CNC machines

| Protocol | Port when empty | Browse | Discovery |
| --- | --- | --- | --- |
| **Fanuc Series 0i** | 8193 | No | No |
| **Haas MDC** | 5051 | No | No |
| **Heidenhain LSV2** | 19000 | No | No |

MTConnect, in the first table, is the usual way to read other CNC controls through an agent.

## Robots and other devices

| Protocol | Port when empty | Browse | Discovery |
| --- | --- | --- | --- |
| **Fanuc Interface** | 60008 | No | No |
| **Kuka TCP** | 7000 | No | No |
| **YASKAWA YRC1000 TCP** | 10040 | No | No |
| **Estun TCP** | 502 | No | No |
| **ER7BC10** | 8080 | No | No |
| **Turck Reader** | enter it | No | No |

## Protocols that are not available

These protocols are not part of the gateway in this release, and are not offered when you add a device: IEC 104,
DLT 645/698, CJT 188, Atlas Copco Open Protocol, SECS/HSMS, the UDP variants of Modbus, Omron FINS, Melsec MC and
Memobus, and MQTT and HTTP as device protocols. If your equipment needs one of them,
[ask us about it](/contact?topic=equipment).

To bring in data from a device that speaks MQTT or HTTP, let it publish to the gateway's broker (see
[MQTT and the UNS topics](https://proxus.io/docs/develop/mqtt#publish-values-from-a-device)) or poll it with a
[function](https://proxus.io/docs/develop/functions-sdk).

## Related

- [Add a device](https://proxus.io/docs/connect/devices/add-a-device)
- [Device profiles](https://proxus.io/docs/connect/device-profiles)
- [Troubleshoot devices](https://proxus.io/docs/troubleshoot/devices)