L-force Motion: L_SMC_TouchProbe_FASTIO: Incorrect position value after executing 'MC_SetPosition' with an external encoder (no correction planned)

Corrected from:
Library:  L_SM3_DriveUtil   (L-force Motion)  (no correction planned)
                     (contained in the PLC Designer)
 
Response of the new version: 
For L-force Motion as predecessor product of FAST Motion there is no correction planned.
 

What happens?
L-force Motion: After triggering the touch-probe event, incorrect position values are displayed as 'RecordedPosition' at the L_SMC_TouchProbeFastIO function block.
Values other than 0 of the external encoder in the AxisRef data structure (structural elements Device.Application.L_ExtEncoder.fOffsetPosition) lead to an incorrect measuring result.
 
When does this behaviour occur?
The offset value for the external encoder (connected to an EPM-S600/-S602 I/O module at the backplane bus) selected via the 'MC_SetPosition' FB is not offset correctly.

Which products are affected?
Library:  L_SM3_DriveUtil   (L-force Motion)
                     (contained in the PLC Designer)
EPM-S600 (I/O system 1000 1 counter 32 bits, 24V DC)
EPM-S602 (I/O system 1000 1 counter 32 bits, 5V DC)

Short-term measures/recommendations: 
Do not use the 'MC_SetPosition' FB if external encoders are used.
Offset the position shift required in the application against the measuring values provided by the external encoder.
As an alternative, you can switch to the new Lenze software product FAST Motion.
        
Evaluation:
As an alternative, you can switch to FAST Motion.

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