L_MC1P: MC_ReadParameter sporadically returns wrong read result despite status xValid=True, with parallel execution in different tasks (corrected from V03.26.00)

Corrected from:
Library: L_MC1P_MotionControlBasic (FAST Motion) from V03.26.00
             (Update via Package Manager)
 
Response of the new version:
When executing different instances of L_DCO_ReadDriveParameter from different tasks in parallel, the correct values are now always displayed.

 
What happens?
L_DCO_ReadDriveParameter, or MC_ReadParameter: 
During parallel execution, it can happen that incorrect values are read and displayed, despite a read job being reported as successful (xValid=True).

When does the behaviour occur?
  • FB L_DCO_ReadDriveParameter, or MC_ReadParameter,
  • Read requests for parameters are executed in parallel from different tasks with different task runtimes.
Which products are affected?
Library:  L_MC1P_MotionControlBasic  (FAST Motion)
 
Short-term measures / evaluation / recommendations:
Execute parallel, temporally overlapping read requests for parameters from one task only.
Or, alternatively, provide a lock in the application to prevent overlapping read requests.


Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/202200099/1/
Meta data
Taxonomy: Lib L_MC1P_MotionControlBasic
AKB-ID: 202200099
Last update: 2023/09/09
Category: Version Informations

Lenze reserves the right to change information on this page at any time. Any liability for the accuracy of the information is excluded.
Contact form