Configuring the access path
The following table shows the available access paths together with their possible settings. In the section Access path details, select the access path that applies to your specific application.
Access via the INAT H1 ISO protocol
|
Access via the INAT H1 ISO protocol and then a KOR-MUX/TELE-Switch interface switch
|
Access via the INAT ISO protocol and then an Echolink serial Ethernet converter
The Echolink device can reach up to 5 CPUs via the AS511 protocol. |
Access via the INAT H1 ISO protocol, an Echolink serial Ethernet converter and then a KOR-MUX/TELE-Switch interface switch
|
Access via the INAT H1 ISO protocol, an Echochange Ethernet converter and then H1/TCP/IP
|
Access via the INAT H1 ISO protocol, Echochange Ethernet converter and then a KOR-MUX/TELE-Switch interface switch
|
Access via the AS511 protocol
|
Access via TCP/IP
|
Access via TCP/IP and then a KOR-MUX/TELE-Switch interface switch
|
Access via TCP/IP and then an Echolink serial Ethernet converter
The Echolink device can reach up to 5 CPUs via the AS511 protocol. |
Access via TCP/IP, an Echolink serial Ethernet converter and then a KOR-MUX/TELE-Switch interface switch
|
Access via TCP/IP, an Echochange Ethernet converter and then H1/TCP/IP
|
Access via TCP/IP, an Echochange Ethernet converter and then a KOR-MUX/TELE-Switch interface switch
|
Access via the INAT H1 ISO protocol, a communication processor (CP) and then the L2 protocol
|
Access via the INAT H1 ISO protocol, a communication processor (CP) a KOR-MUX/TELE-Switch interface switch and then the L2 protocol
|
Access via the INAT H1 ISO protocol, an Echolink serial Ethernet converter, a communication processor and then the L2 protocol
|
Access via the INAT H1 ISO protocol, an Echolink serial Ethernet converter, a KOR-MUX/TELE-Switch interface switch, a communication processor (CP) and then the L2 protocol
|
Access via the INAT H1 ISO protocol, an Echochange Ethernet converter, a communication processor (CP) and then the L2 protocol
|
Access via the INAT H1 ISO protocol, an Ecochange Ethernet converter, a KOR-MUX/TELE-Switch interface switch, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, a KOR-MUX/Tele-Switch interface switch, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, an Echolink serial Ethernet converter, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, an Echolink serial Ethernet converter, a KOR-MUX/TELE-Switch interface switch, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, an Echochange Ethernet converter, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP, an Echochange Ethernet converter, a KOR-MUX/TELE-Switch interface switch, a communication processor (CP) and then the L2 protocol
|
Access via TCP/IP and an S5 LAN++ module
|
Please note:
-
For connections via the H1 protocol, the INAT H1 driver is required. The driver is included with octoplant and can be used up to and including Windows Server 2008. If the octoplant server is installed on a computer on which the driver does not work, then either
- a different H1 driver must be installed that works on the server's operating system, or
- the upload must be carried out using an agent via a computer on which the driver is installed
-
When using the H1 protocol, it is advisable to deactivate the QoS Packet Scheduler on the appropriate network card
-
When using the H1 protocol, H1 protocols from other manufacturers must be deactivated on the appropriate network card
- Please note that the TSAPs must have a length of at least 2 bytes and at most 16 bytes. In order to establish the connection, the TSAPs must match up when viewed crosswise! This means the local TSAP of one system must be the same as the remote TSAP of the other system.
-
A valid installation of the program PLC-VCOM.EXE by Process-Informatik, version 2.79 or newer, is required.
- The program must be removed from all autostart processes (startup, Task Scheduler etc.).
Related topics |
---|