L_MC4P Conveyor tracking: Access to the Cartesian setpoints for the integration of an average filter (from V03.22.00)

Function extension:
FB 'MC_TrackConveyorBelt' or TM 'L_TT1P_TrackPickAndPlace':
In conveyor tracking, the setpoint for the picker axis is formed from two superimposed components:
  1. Setpoint component: Interpolated movement of the picker axis (FB MC_Move).
  2. Tracking component: Movement of the conveyor belt 
(so far) L_MC4P up to V03.21.00:
  • Variables Axis_X/Y/Z.lrSetPosition / -Velocity / -Acceleration contain the sum of both components.
    Depending on when the variable is accessed, it initially contains only the interpolated setpoint component and at the end both components.
    202100235-Signalflow-Before.jpg
(new) signal flow L_MC4P from V03.22.00 :
Additional variables for the "Effective" values have been added, which take over the function of the previously existing variables and are to be used in their place. 

For compatibility reasons, the previously used variables are still present, but with a different function:
  • Variables Axis_X/Y/Z.lrSetPosition / -Velocity / -Acceleration now only contain the set values of the interpolator WITHOUT a superimposed tracking component.
  • Variables Axis_X/Y/Z.lrSetPositionEffective / -VelocityEffective / -AccelerationEffective now always contain the setpoints WITH superimposed tracking component.
    202100235-Signalflow-New.jpg
The variables can be read via the axis group:  
<AxesGroup>.pAxis_X/Y/Z^.lrSetPositionEffective / -VelocityEffective / -AccelerationEffective.

Via the signal flow diagrams it is evident that in the implementation up to V03.21.00, the setpoint filters on Cartesian WCS axes had no effect on the actual movement performed.

Contained in which products?
Library: L_MC4P_RoboticHandling (FAST Motion) as of V03.22.00.157
             (Update via Package Manager)

Application:
ConveyorTracking with FB MC_TrackConveyorBelt or technology module L_TT1P_TrackPickAndPlace.

Note:
When using the new versions from V03.22.00, the "Effective" variables must be used:
<AxesGroup>.pAxis_X/Y/Z^.lrSetPositionEffective / -VelocityEffective / -AccelerationEffective.
In case of an update of the libraries in an existing project, corresponding adjustments of the above mentioned variables are necessary.

Automatic Translation

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