|
Type |
EF |
|
Devices supporting the parameter |
Encoder network (Synchronization encoder output) |
|
Traceable |
Yes |
There is a great deal of variation in how susceptible different applications are to errors while receiving encoder data. For this reason, you can use the parameter DataCycleErrorLimit to define how many consecutive cycles may have telegram errors before the diagnostic message 8333 "EncNet receiving data not possible" is issued.
The corresponding warning, 8334 "EncNet receiving data dist. detected", will always be issued as soon as the first receiving error occurs.
You can use the parameter DataValid to check whether correct data are available for the current cycle or whether a receiving error occurred.
NOTE: If an error occurs while receiving encoder data, the system continues to work using the last valid velocity signal. As a result, this is not relevant in many applications that have a constant velocity signal via the Encoder network and (for example) a simple error receiving encoder data.
