Procedure
You must carry out the following actions to access a new PLC via the network:
Step |
Action |
---|---|
1 |
Activate the menu command, which displays the Set address dialogue. |
2 |
In the PLC Address field, enter the address of the new PLC. |
3 |
In the PLC Media field, select the type of communication you wish to use. For Ethway drivers, refer to the following note. |
4 |
If you wish, modify:
|
5 |
To carry out a connection test click on the Test Connection button. |
6 |
When you are finished, confirm with the OK button. |
Description of Set Address Parameters
The following table describes the Set Address dialogue:
Group box |
Parameter |
Description |
---|---|---|
PLC |
Address |
PLC address (by default, the address of the PCL physically wired to the terminal). The drop-down menu lists any previous addresses entered. Clicking on the trashcan clears the drop-down list |
Media |
This drop-down selects the type of communication with the network for the PCL. |
|
Communication Parameters |
By clicking this button you access the PLC communication parameters. |
|
Simulator |
Address |
Simulator address The drop-down menu lists any previous addresses entered. Clicking on the trashcan clears the drop-down list |
Media |
This drop-down selects the type of communication with the network for the simulator. |
|
Communication Parameters |
By clicking this button you access the simulator communication parameters. |
|
Bandwidth |
Click this button to display the Online Mode Services Bandwidth dialogue. |
|
Test Connection |
Click this button to execute a connection test without closing the Set Address dialogue. |
|
Speed rate auto-adaptation at the end of download |
Choose this mode for applications which do not require a specific speed rate (e.g., Modems). |
Network Address Syntax
The network address syntax is documented in the Architecture and Communication Services manual.
The following table describes the various authorized addresses according to the platforms and media supports.
Platform |
Support |
Address syntax |
|
---|---|---|---|
Premium |
Uni-Telway |
SCP01 |
X-Way |
Uni-Telway |
UNTLW01 |
X-Way Example: UNTLW01 0.2.1.4 access to the Uni-Telway slave at address 4 which is connected to rack 0, module 2, channel 1 of the local PLC. |
|
Fipway |
FIP01, FIP02, FPP2001 (driver for the TSX FPP20 card) |
X-Way |
|
Fipio |
FIP01, FIP02, FPP2001 |
X-Way Example: FIP02 \2.55\SYS to access to FIPIO connection point 55 through the privileged terminal Fipio (address 63 for Premium) Example: FIP01 SYS to access to Fipio Master through the privileged terminal Fipio (address 63 for Premium). |
|
PCIway |
PCIWAY01, PCIWAY02 |
X-Way |
|
Ethway |
ETHWAY01, ETHWAY02 |
X-Way |
|
XIP |
XIP01 to XIP05 |
X-Way Example: XIP01 {3.5}\2.55\SYS to access a FIPIO connection point 55, through the network 3 and station 5 PLC. Example: XIP02 {3.5}0.2.0.4 access to a Uni-Telway slave connection at address 4 which is connected on the rack 0 module 2 channel 0 of the network 3 and station 5 PLC. |
|
Ethernet IP |
TCP/IP |
IP address |
|
Ethernet IP |
TCP/IP** |
IP address;Index or "DNS machine name;Index" |
|
USB |
USB |
implicit; no address is necessary as the connection is point to point. However, it is possible to enter an X-Way address when the PLC is acting as an X-Way router |
|
Modbus Plus |
MBPLUS01 to MBPLUS04 |
Modbus Plus Address Example: MBPLUS01 2.1 access to Modbus Plus node address 1 which is connected after the Modus Bridge address 2. |
|
Quantum |
Serial Modbus |
MODBUS01 to MODBUS04 |
Modbus Slave Number |
Modbus Plus |
MBPLUS01 to MBPLUS04 |
Modbus Plus Address |
|
Ethernet |
TCP/IP |
IP Address Example: TCPIP 84.0.127.6 access to an Ethernet TCP/IP station. |
|
Ethernet IP |
TCP/IP*** |
IP address;Index or "DNS machine name;Index" |
|
USB |
USB |
implicit; no address is necessary as the connection is point to point |
|
Modicon M340 |
Serial Modbus |
MODBUS01 to MODBUS04 |
Direct Address: Modbus slave number Remote address: Link_address.Modbus Slave number Link_address = r.m.c. of Modbus link Direct address example: 66 Bridging example:
|
Ethernet |
TCP/IP |
Direct address: IP Address Remote address: Netlink {IP address} Netlink address = r.m.c. of Ethernet link Direct address example: 84.0.127.6 Bridging example:
|
|
Ethernet IP |
TCP/IP** |
IP address;Index or "DNS machine name;Index" |
|
USB |
USB |
SYS or empty Bridging example: SYS\\0.0.0.66 for USB to Modbus slave 66. |
|
Modicon M580 |
Ethernet |
TCP/IP |
Direct address: IP Address Remote address: Netlink {IP address} Netlink address = r.m.c. of Ethernet link Direct address example: 84.0.127.6 Bridging example:
|
Ethernet IP |
TCP/IP** |
IP address;Index or "DNS machine name;Index" |
|
USB |
USB |
SYS or empty Bridging example: SYS\\0.4.0.66 for USB to Modbus slave 66 of channel 0 of a BMX NOM 0200 on slot 4. |
|
Simulator |
Ethernet |
TCP/IP |
IP address;Index ** "localhost" "DNS machine name;Index" ** |
Legend |
**: "Index" is the Modbus Plus or Modbus index stipulated in the bridge you want to cross. This access only works in display mode: it cannot be used to modify the program or force values. ***: "Index" is the Modbus Plus or Modbus index stipulated in the bridge you want to cross. Note: You must use quotation marks when the address includes characters other than figures, full stops or semi colons. These are used to avoid this address being analyzed syntactically. |
Accessing PLCs Behind a Router
When you need to communicate to several PLCs behind routers, configure a network address translation table in Control Expert to handle different ports. You supply the router address and different ports to reach PLCs behind the routers.
Example:
Suppose the router address is 139.160.39.12. The PLC addresses below are local:
PLC Number |
PLC Address |
---|---|
1 |
192.168.0.1:502 |
2 |
192.168.0.2:502 |
3 |
192.168.0.3:502 |
This example shows PLCs with different addresses, but the same port. |
Network Address Translation Table
The network address translation table would look something like this:
Port |
Destination |
---|---|
TCP/IP 3501 |
192.168.0.1:502 |
TCP/IP 3502 |
192.168.0.2:502 |
TCP/IP 3503 |
192.168.0.3:502 |
This example shows the same router address with different ports, each port corresponding to a PLC address. |
Notes:
Control Expert can communicate with PLC 2 using the router address followed by port 3502.
In the
dialog, type 139.160.39.12:3502.The router sends the message to the address 192.168.0.2:502 (configured in the router in the network address translation table).
To communicate with other PLCs, use the same router address, but change the port number.