...
Lines of categories TCP/IP-TCP and TCP/IP-TCP Redundant were designed for the needs of communication protocols that are built directly on TCP/IP. Both IPv4 and IPv6 protocols are supported. TCP/IP-TCP Redundant enables the implementation of redundant communication (redundant network lines, redundant network interfaces) and configuration of two or more IP addresses of a communication partner, and creation of two parallel TCP connections.
The following protocols are supported at the present time:
Line TCP/IP-TCP
- Allen-Bradley CSP/PCC
- Datalogger ESC8816
- DLMS/COSEM
- DNP3
- Ethernet/IP
- General Electric SRTP
- Generic User Protocol
- HART
- IEC 60870-5-104
- IEC 60870-5-104 Server
- IEC 60870-5-104 Sinaut
- IEC 60870-6 ICCP/TASE.2
- IEC 61850
- IoT over LoRaWAN/Sigfox
- Johnson Controls N2-Bus
- KMZ Lite protocol
- KMZ protocol
- KNX protocol
- L&G TOCCATA
- MODBUS Client
- MODBUS Server
- MQTT Client (Message Queue Telemetry Transport)
- Omron FINS
- Orange GDEP
- SAE RTU
- Siemens SAPHIR
- Siemens SIMATIC S7 ISO on TCP
- Telegyr 809 Server
- Teltonika Codec14
...
Note: It is possible to use symbolic addresses * or ALL (for IPv4 protocol) or [*] or [ALL] (for IPv6 protocol) - in this case, the KOM process listens on a chosen TCP port on all network interfaces which are available.
If the configured protocol is not a server protocol, the IP address of the communication partner to which the KOM process connects should be configured.
Note: If the configured protocol is not a server protocol, for selected protocols, multiple IP addresses or names can be configured (separated by commas or semicolons). The KOM process will cyclically try all configured IP addresses/names when connecting to a communication partner.
...