General RestrictionsΒΆ

Restrictions for the available Function Blocks

  • As buffered mode, MC_Aborting is realized as a default. This does NOT mean that the axis stops when another movement is started while an ongoing movement is still active. It means instead that the new movement will take control immediately and change the velocity to its own velocity by using its own acceleration or deceleration.
  • The buffered mode MC_Buffered could be reached with using the axis state StandStill as enable signal for the Execute of the next block.
  • From the Extended Inputs and Outputs at the Function Blocks, the following are not realized:
    • BufferedMode: The realization just supports the MC_Aborting mode.
    • The following Outputs at ReadStatus are not supported: ConstantVelocity, Accelerating and Decelerating.
    • TorqueLimit for Homing-Function Blocks.
../_images/f451fa7d2c043ce00a33139001bbd417
../_images/41ef871f2c0442330a33139000ff7b3c

MC_Aborting Mode

The diagram shows the behavior with BufferMode MC_Aborting, which is the only available BufferMode. When the 2. Block is activated, it will take control and will continue on its own velocity. The velocity is changed by using the acceleration value from the 2. Function Block. The movement will not be stopped in between. The first Function Block shows CommandAborted when the 2. Function Block is activated.

MC_Buffered

A behavior according to BufferMode MC_Buffered could be reached by using the Done-output from the first Function Block to enable the Execute of the 2. Function Block.