L_TT1P_FlexCAMState: xCalcCamBounds does not work (corrected from V3.13)

Corrected from:
L_TT1P_TechnologyModules_LM V3.13.0.7
 
Response of the new version:
The FlexCamState technology module also calculates the lrSlaveMaxPos, lrSlaveMinPos, lrSlaveMaxVel, lrSlaveMaxAcc extreme values of the slave drive.
 
 
What happens?
The lrSlaveMaxPos, lrSlaveMinPos, lrSlaveMaxVel, lrSlaveMaxAcc extreme values of the slave drive are not calculated.
 
When does this behaviour occur?
The behaviour occurs if xCalcCamBounds is set to TRUE.
 
Which products are affected?
L_TT1P_FlexCAMState function block from L_TT1P_TechnologyModules_LM library (V3.12.0.9 and higher)
 
Short-term measures:
Use the L_MC2P_BoundsCam FB and calculate the extreme values of the cam outside the TM.  
 
Evaluation/recommendations:
The extreme value evaluation function is used to get information about the present cam. If the above-described short-term measure is observed, the function can be implemented outside the TM in the application. The function restriction will be corrected in Release V3.13.

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