L_MC4P_PathRefFromFile: Calling again leads to internal error (corrected from V03.23.00)
Corrected from: Library: L_MC4P_RoboticHandling (FAST Motion) from V03.23.00.173
(Update via Package-Manager)
Response of the new version:
Multiple triggering of FB MC_PathRefFromFile to read a path file via Execute edge is now handled as follows:
VPrevious assignment of FB L_MC4P_PathRefFromFile is still active: --> Execute edge(s) are ignored.
Previous assignment of FB L_MC4P_PathRefFromFile is completed (file completely read) and is currently being processed by an MC_MovePath: --> The (new) file read in by Execute edge is appended to the current assignment. --> The system behaves exactly as if the commands of the two files were contained in a single file.
Previous assignment of FB L_MC4P_PathRefFromFile is completely read in and also processed by MC_MovePath: --> The file is read in but not processed. An Execute edge is waited for at the MC_MovePath.
What happens?
L_MC4P_PathRefFromFile: An 'Internal error' occurs if FB 'L_MC4P_PathRefFromFile' is retasked with an execute edge before the movement is complete.
When does the behaviour occur?
The MC_MovePath associated with FB 'L_MC4P_PathRefFromFile' was assigned in BufferMode 'mcAborting'.
Which products are affected?
Library: L_MC4P_RoboticHandling (FAST Motion)
Short-term measues, Evaluation / Recommendations:
Apply movement MC_MovePath in BufferMode 'mcBuffered' and set the desired polishing mode in the G-code file.
