Actual position is not updated in the fast cycle via the process data channel (tx_par1, tx_par2) (remedied from V1.3 onwards)
Remedied from:
ECSxP Posi&Shaft V1.3 onwards
Behaviour of the new version?
The two data words (tx_par1) and (tx_par2) are now updated equidistantly (same distances with regard to the time) every 6 ms.
Before the update inside a program part was executed with a considerably longer cycle time and this cycle time could vary very strongly (not equidistantly) dependent on the CPU time utilisation required for the functions currently in use.
If the default setting is selected the two data words (tx_par1) and (tx_par2) can be used to transmit the current actual position via the process data channel to a higher-level control. Therefore, the actual position transmitted is much more informative in case of fast and dynamical control processes (T < 50 ms).
Which products are affected?
ECSxP Posi&Shaft <=V1.2
What happens?
According to the default setting the two data words (tx_par1) and (tx_par2) can be used to transfer the current actual position via the process data channel to a higher-level control. However, inside the controller the actual position is not updated in the fast and equidistant (same distances with regard to the time) 6 ms cycle but inside a program part with a considerably longer cycle time. In addition this the cycle time may vary very strongly (not equidistant) dependent on the CPU time utilisation required for the functions currently in use.
When does the problem occur?
Continuously.
Possible diagnostics?
Evaluate the actual position transmitted.
Short-term measures/recommendations?
Observe the situation described with regard to the further use of the actual position values.
Evaluation:
If the further processing of the actual position values relates only to display purposes inside the higher-level control or other display units impacts will not be noticed. It will also be possible without problems to evaluate the actual position values of 'slow' control processes (T > 50 ms).
An influence resulting from the relatively slow update of the actual position values will mainly be noticed in case of fast and dynamical control processes (T < 50 ms).
Published with service message No. 2007/02 and 2007/03
