L_MC1P_BrakeGrindIn: Despite controller inhibit the motion axis remains in standstill status ( 0x500A.004=[3] ) (fixed from V03.24.00)

Corrected from:

Library: L_MC1P_MotionControlBasic (FAST Motion) from V03.24.00

(Update via Package Manager)

Response of the new version:

If the function Loop in brake cannot be executed due to the conditions mentioned below, the axis status is now correctly displayed with state 'disabled'.

What happens?

L_MC1P_BrakeGrindIn:

The Loop in brake function can only be started in the disabled state.

If the Loop in brake function cannot be executed due to the conditions mentioned below, the Loop in brake function will not be executed or it will be aborted, as expected.

After an abort, however, the 'Disabled' state is not displayed as the axis state, but the 'Standstill' state.

When does the behaviour occur?

When the Loop in brake function is activated, a Safe Stop 1 (SS1) or Quickstop application is requested.

Which products are affected?

Library: L_MC1P_MotionControlBasic (FAST Motion)

Short-term measures / Evaluation / recommendations:

Do not start the Loop in brake function until no request for SS1 or Quickstop application is pending.

The wrong status display is correct again after releasing the axis.

Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202100333/1/