Multiple network cards

A TCP/UDP RT object is assigned to an RT Ethernet adapter by instantiating it under the objects, for example. A TCP/UDP RT object therefore always addresses precisely one network port of the controller via the RT Ethernet adapter.

If several network ports are to be used, a TCP/UDP RT object is created for each RT Ethernet adapter:

The TCP/UDP RT objects relate to the higher-level RT Ethernet adapter, if no other configuration was specified manually:

These objects have different object IDs:

This object ID is used for referencing, as described above:

PLC:

Or for a C++ module:

The use is highly dependent on the application. Some sample scenarios are provided below:

• A C++ module can be instantiated more than once. Each module can then communicate via a particular network card, based on the configuration with the corresponding object ID.
• Different PLC programs can be assigned separate TCP/UDP RT objects and thus act independently.
• A PLC or C++ program can address several TCP/UDP RT objects (and therefore several network cards), based on corresponding symbols (C++ is used as an example here):
  Object management must be implemented to suit the application. For example, the CheckReceived() calls must be applied to all objects. This also applies to calls for SendData() / RegisterReceiver() etc.