Beckhoff EL3773 Documentation page 120

Commissioning
Fig. 139: Illustration of a 10 x oversampling variable of the EL3751 by the Scope2
Within the image was marked subsequently that the oversampling variable originated by the PLC was just
added to the Y-axis (observe selection of the PLC-POU name "MAIN" within the "ROUTES" tree). Herewith
"Force Oversampling" was activated due to the oversampling variable is not provided by the terminal.
Proceeding with TwinCAT 2/ alternatively via ADS
In former TwinCAT 2 versions (or a lower revision as specified in the table [} 106] above) the oversampling
PDO of the respective oversampling able terminal can be made visible for the Scope2 by activation of the
ADS server.
So the creation of a PLC variable can be disclaimed as well. Therefore the ADS server of the EtherCAT
Device where the oversampling able terminal is connected with have to be activated.
120 Version: 2.5 EL3773