Out of process data exchanges are often data exchanges between control network and device network. For example, you may use a supervision software or a third-party configuration tool to communicate with a target on the device network.
The Industrial Ethernet network permits out of process data exchanges.
To enable out of process data exchanges:
oConfigure the gateway address in the devices.
oEnsure that the IP forwarding service is enabled.
oCheck the PC routing (see below).
NOTE:
Out of process data exchanges originating from any of the following sources may impact the performance of the controller:
oDTM, Web server, and Modbus TCP requests.
oNetwork communications (DTM, Web server communications when the PC is on the network).
oTCP UDP communications generated by the TcpUdpCommunications library.
When connecting a DTM to a device using the network, the DTM communicates in parallel with the running application. The overall performance of the system is impacted and may overload the network, and therefore have consequences for the coherency of data across devices under control.
|
|
|
UNINTENDED EQUIPMENT OPERATION |
|
Do not connect DTMs that communicate across the device network on a running application if the DTM causes deleterious effect on performance. |
|
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
The PC supporting the supervision software or configuration tool must be configured to communicate with the slave devices. The PC must be in the same subnet as one of the Ethernet ports of the controller.
|
If the slave device is configured... |
Then... |
|---|---|
|
As a predefined slave through FDT/DTM |
No specific PC parameterization is needed. NOTE: The PC configuration is not altered. |
|
Using another tool |
If the PC is not in the same subnet as the slave devices, you must update the routing table of the PC (see below). |
To update the routing table of the PC, stop every connection from the PC to the controller and/or other devices. Then, in a Windows command prompt, execute the command:
route ADD destination MASK subnet_mask gateway
Where:
|
Parameter |
Value |
|---|---|
|
destination |
IP address of the Industrial Ethernet network |
|
subnet_mask |
Subnet mask of the Industrial Ethernet network |
|
gateway |
IP address of the controller port connected to the control network |
For example, for a TM251MESE, if:
oIP address of the PC: 192.168.0.2
oSubnet mask of the PC: 255.255.0.0
oIP address of the Industrial Ethernet network: 10.10.0.0
oSubnet mask of the Industrial Ethernet network: 255.255.252.0
oIP address of the control network port “Ethernet_1”: 192.168.0.5
oSubnet mask of the control network port “Ethernet_1”: 255.255.0.0
The corresponding command would be:
route ADD 10.10.0.0 MASK 255.255.252.0 192.168.0.5
To verify the parameters, execute the command:
route PRINT
To remove the route from the PC, execute the command:
route DELETE destination
Where destination is the IP address of the Industrial Ethernet network entered previously.
