EURO 404 - Motion Problem at SERVO_PERIOD 250
A motion problem could occur when running MC403, MC405, Euro404 or Euro408 at 250 usec servo period. The moves would stop (buffers frozen) and an uncommanded movment could occur on one axis in an XY pair. The issue occured very infrequently and was fixed in V2.0303 firmware.
Using 2.0303 and later is recommended when running at either 125 usecs or 250 usecs SERVO_PERIOD.
This issue does not affect EtherCAT or RTEX capable Motion Coordinators, or the MC508.
Related Articles
What does SERVO_OFFSET do?
SERVO_OFFSET is a system parameter that is usually set by the operating system. The value depends on the SERVO_PERIOD, the modules fitted (to a MC664X) and the model of Motion Coordinator. It should not be necessary to set this in a system. Only ...
Kollmorgen drive with SERVO_PERIOD issue
EtherCAT network goes in operational state only with SERVO_PERIOD=250 µsec setting when Kollmorgen drives are in use. The network stays in safe-operational state with any other servo period setting. The following needs to be done; * MC_CONFIG to be ...
Motion Perfect problem when SCOPE command is used
When running the SCOPE command in a program, I think Motion Perfect doesn't like the SCOPE command being issued over and over when I run it. It seems more stable when I comment the SCOPE command out after it's ran once. ...
Error display Exx - what do they mean?
Error Display Codes Unn Unit error on slot nn - see SYSTEM_ERROR Ann Axis error on axis nn - see AXISSTATUS Cnn Configuration error on unit nn ie: too many axes - see SYSTEM_ERROR Exx processor / memory event - see SYSTEM_ERROR and FLASH_LOG E00 - ...
What is the range of Servo update rates on P834 EURO408?
The Euro404 and Euro408 both support the following servo update rates set by SERVO_PERIOD. At the fast rates, the number of axes is reduced. 125 microseconds (4 axes max) 250 microseconds 500 microseconds 1 milliseconds 2 milliseconds