TwinCAT 2 procedure

System requirements A TwinCAT Scope2 must be installed on the system. An oversampling-able terminal must be present in the configuration.

The data type of the variables is also conveyed to the TwinCAT Scope2 via the ADS data. Therefore, the array variable must be created

• in the PLC, see step 1a
• or directly in the System Manager if only one free task is present, see step 1b

The same settings are to be made in the Scope2 for both cases, see step 2

Step 1a: TwinCAT 2 PLC

Since the channel data are to be used in the PLC, a linkable ARRAY variable must be created there, as shown in the following example:

This then appears in the list in the System Manager; as a rule it can also be reached via ADS without further measures since PLC variables are always created as ADS symbols in the background.

Note: The Scope2 can only "see" such variables in the variable browser if TwinCAT and the PLC are in RUN mode.

Step 1b: TwinCAT 2 - free task

The array variable required for Scope2 can alternatively be defined and created manually in the System Manager.

As before in the program (POU "Main"), an ARRAY variable of the same type as from the oversampling PDO of the respective terminal/box must be created. In this example an array of 0..9 of the type INT, i.e. with 10 fields.

If this variable is known to the System Manager, an instance of it can be assigned to an additional task with a right-click. It appears in the overview, sorted according to bit size.

In this example the variable Var152 is created. It can now be linked with the PDO-Array of the respective channel of the terminal/box.

If MatchingSize is activated in the dialog, the individual channels are offered directly.

So that the variables can also be found via ADS in the Scope2, the ADS symbols must be activated as well as the Enable Auto-Start, otherwise the task will not run automatically. ADS symbol tables are then created for all variables that have this task in their process data images.

Step 2: Configuration in the Scope2

So that the linking works, an array variable with the channel data of the respective terminal/box must be present in the system manager; i.e. each oversampling data package must be present in an array. This array variable must be defined and created manually; see above.

You can now browse to the variable concerned in the Scope2.

The array is then not to be opened; instead the array symbol is to be selected by right-clicking on AddSymbol.

ForceOversampling and DataType INT16 must be set in the channel which has now been created. If necessary SymbolBased must be temporarily deactivated in addition.

In order to check that individual oversampling values are really being logged, the Marks can be activated in the Scope2. Please observe the interrelationships between task cycle time, sampling time of the Scope2 channel and oversampling factor.

An additional example illustrates the following image by representation of an oversampling – variable from the EL3751 with 10 x oversampling:

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/box.

Proceeding with TwinCAT 2/ alternatively via ADS

In former TwinCAT 2 versions (or a lower revision as specified in the table above) the oversampling PDO of the respective oversampling able terminal/box 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/box is connected with have to be activated.

The activation of the ADS server have to be carried out by selection of the “Device – Image” on the left sided configuration tree:
„I/O – Configuration → I/O Devices → Device .. (EtherCAT) → Device .. – Image“.

Next the register card “ADS” have to be selected to activate each checkbox „Enable ADS Server“ and „Create symbols“ then (the port entry is done automatically).

Thus, with the Scope2 process data can be accessed via the target browser without an embedded POU and without a variable reference respectively.

Also see Beckhoff Information System infosys.beckhoff.com → TwinCAT 2 → TwinCAT Supplement → Category Measurement TS3xxx → TS3300 | TwinCAT Scope 2 → Annex → Oversampling record:

Beckhoff TwinCAT supports the Scope2 with some oversampling devices in a special way by automatically calculating a special ADS array symbol in the background, which appears in the Scope2 in the variable browser. This can be then linked as a variable and automatically brings along the array information.

Summary: an array variable has to be provided which is reachable via ADS. This can be a PLC variable of a POU or a defined array variable by the system manager or alternatively the ADS server of the device of the terminal or box is just activated. This is then detected by Scope2.