Elimation from?
EVS93xx-EK V8.1, EVS93xx-CK V8.1
Behavior of the new version?
When operating the function block PHINT5 in the mode 'rotary cutter' (C1186 = 2) there will be no endless correction after a touch probe synchronization.
What happens?
The drive controller does not follow the master value. The PHINT5 function block indicates a velocity which superimposes the master value velocity (PHINT5-DFIN) at the PHINT5-DFOUT output although the touch probe correction should have been completed long ago (TP endless correction).
When does the problem occur?
The endless correction occurs as soon as the first touch probe signal is detected at terminal E5 and the following zero crossing (PHINT5-X0) has been executed. The behaviour occurs when the 'rotary knife' operating mode is used (internal PHINT5 code: C1186 = 2).
Possible diagnostics?
The problem can be diagnosed if the PHINT5-DFIN velocity input is compared with the PHINT5-DFOUT velocity output. Both signals must indicate identical values. The problem has occurred if the master value input differs continuously from the master value output.
Note: The resulting stretching/compression factor for the PHINT5-DFIN master value input must be 1 while the diagnostics is executed (PHINT5-NUM = PHINT5-DENOM).
Short-term measures/recommendations?
Use the touch probe correction of the CDATA function block instead of the touch probe correction via the PHINT5 function block.
Evaluation:
The PHINT5 function block has been implemented as new function block in firmware version 9300EK V7.1. This means that the function could not have been used anyhow before.
