BECKHOFF CP-Link3 - Manual (Page 62)

Page 62
2. Access via "Virtual USB interface (Remote)"
In this case, the CPx8xx Bus Coupler is used on the client as a local USB device. The CP-Link 3 USB device server on
the client is configured accordingly via a "Use Local List" (also see Using USB devices locally on the client ). The access
from host PC to the I/O channels of the Bus Coupler does not then run over the CP-Link 3 Virtual USB Hub but rather
over ADS directly with the Bus Coupler driver on the client. The advantage here is that less data packets have to be sent
over the network connection in each cycle. For this reason using standard Ethernet for communication, the timeout of
100 ms is practically never exceeded with this method. Here again, however, it is not possible in theory to exclude the
possibility that the time required to send the data packets will become too long. If communication takes place via RT
Ethernet the data exchange is carried out deterministically and the outputs cannot drop out.
Note
TwinCAT v2.11 Build 1542 is required
The "Virtual USB Interface (Remote)" device is supported from TwinCAT 2.11 Build
1542.
2.a "Virtual USB Interface (Remote)" via standard Ethernet
In the TwinCAT System Manager a "Virtual USB Interface (Remote)" device can be inserted into the "I/O Devices" node
in the configuration by the selection of "Append Device" in the context menu. The "Virtual USB Interface (Remote)"
device can be found underneath the "USB" node in the list of available devices.