STOBER 8 | Commissioning
02/2020 | ID 442516.07
25
4. Device control tab:
Device control: Select CiA 402.
Process data Rx, Process data Tx: Select EtherCAT Rx and EtherCAT Tx for transmitting the EtherCAT process data.
Projecting the axis
1. Click on Axis 1.
2. Properties tab:
Establish the connection between your circuit diagram and the axis to be projected in DriveControlSuite.
Reference: Specify the reference code (equipment code) of the axis.
Designation: Give the axis a unique name.
Version: Version your project configuration.
Description: If necessary, specify additional supporting information, such as the change history of the project
configuration.
3. Application tab:
Select the desired application.
If you are working with the MC6 motion controller and the AS6 development environment, we recommend
CiA 402 HiRes Motion (version with user-defined units of measure).
If you are working with hardware and software products from Beckhoff, we recommend CiA 402 (incremental
version).
4. Motor tab:
Select the type of motor operated using this axis. If you are working with motors from third-party suppliers, enter the
accompanying motor data at a later time.
5. Confirm with OK.
8.1.1.2 Configuring safety technology
If the drive controller is part of a safety circuit, you have to configure the safety technology in accordance with the
commissioning steps outlined in the corresponding manual in the next step.
8.1.2 Parameterizing general EtherCAT settings
ü
You have projected a device control with the EtherCAT Rx and EtherCAT Tx process data as part of drive controller and
axis projecting.
1. Highlight the relevant drive controller in the project tree and click on the first projected axis in the project menu >
Wizard area.
2. Select the EtherCAT wizard.
3. A213 Fieldbus scaling:
Leave the default setting at 1: raw value (values are passed unchanged).
4. A258 EtherCAT PDO-Timeout:
In order to be able to detect a communication failure, monitor the arrival of cyclical process data by defining a PDO
timeout.
Permitted value range: 0 – 65535ms.
Please note:
0 and 65535 = Monitoring is inactive
1 to 65531 = Monitoring is active
65532 = Monitoring is active but the loss of an individual data packet is ignored
65533 = Monitoring is active but the loss of 3 data packets in a row is ignored