Commissioning
EL37x2
136
Version: 3.5
Fig. 177: 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 [
}
122]
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.
Summary of Contents for EL3702
Page 2: ......
Page 6: ...Table of contents EL37x2 6 Version 3 5...
Page 83: ...Commissioning EL37x2 83 Version 3 5 Fig 92 Incorrect driver settings for the Ethernet port...
Page 142: ...Commissioning EL37x2 142 Version 3 5 Fig 184 Process data tab SM0 EL37x2...
Page 143: ...Commissioning EL37x2 143 Version 3 5 Fig 185 Process data tab SM1 EL37x2...
