Configuration Settings in the OPC server An ADS communication partner is always specified by two parameters: These are what is known as the "AdsAmsNetId" (e.g. 1.2.3.4.5.6) and the "PortId" (e.g. 801 for the first PLC run-time system). If ADS is to be used to exchange data with, for example, the first PLC run-time system on another PC, then the AdsAmsNetId of the target PC, and "801" as the PortId, must be entered in the OPC server under "Device settings". If possible, the option of using the "Network via client" protocol should be selected for performance reasons.
Also see about this 2 Network via client protocol [ } 32] 6.1.6.3 Network via DCOM If you wish (or need) to allow data exchange between an OPC client and the TwinCAT OPC server over a network via DCOM, this DCOM access type must be configured beforehand. The data flow is then as follows: The following steps describe the necessary settings for the PC on which the TwinCAT OPC server is installed. (Use step 1 for the PC on which the OPC client is installed.) Requirement It is assumed that all the PCs which are to participate via DCOM in an OPC client/server connection are already set up for network operation (i.e.
they have configured network cards running the TCP/IP protocol) 6.2 OPC XML-DA Server This chapter describes how to configure the OPC XML DA Server on BECKHOFF PC based systems. Summary : The OPC-XML DA server is configured with default xml-configuration file. Just activate once a checkbox in PLC-Control to download the symbol information to target device. With TwinCAT 2.10 Build 1240 (or higher) there is no manual configuration required. Please refer to section "Zero configuration" on this page. TS6120 34 Version: 1.2.0