L_TT1P_Winder: Material length counter based on LREAL velocity is not subject to remainder handling (corrected from V3.15.0)

 

Corrected from:
L_TT1P_TechnologyModules_LM (V3.15.0.32)
 
Response of the new version: 
If the encoder is connected at the MaterialCounterAxis TM input, the material length is determined via the number of revolutions. The material length is displayed via the feed constant of the reference axis (modulo axis) at the lrMaterialCounter output. The counter content is persistently saved.
 

What happens?
Material length counting is imprecise.

When does this behaviour occur?
The behaviour occurs when using the velocity values from an encoder axis.
 
Which products are affected?
L_TT1P_Winder function block from L_TT1P_TechnologyModules_LM library (V3.10.0.8 and higher)
 
Short-term measures:
Simulate the material speed from an encoder axis via the position difference.
 
Example:
lrPosDiff :=LM_ExtEncoder.lrActPosition - lrPosDiffOld;                              // Calculate actual position difference
lrModuloDiff := L_MC1P_HlpModuloDiff(lrDiff:= lrPosDiff, lrLen:= 360); // Correct modulo overflow with help function
lrPos := lrPos + lrModuloDiff;                                                                            // Add calculated modulo position
lrPosDiffOld := LM_ExtEncoder.lrActPosition;                                               // Save actual position for next calculation
 
Evaluation/recommendations:
If the above-described short-term measure is observed, the material counting error will be minimised.

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201500758/1/
Kontaktformular