F
Member
【Editorial Discussion】
A PLC program can report a stable average scan time and still leave a servo or coordinated axis looking jittery. Average scan is a poor proxy for the deadline the motion actually missed. The first job is to find whether the jitter is in the controller cycle, the network, or the drive.
1) Look at the worst-case scan and the jitter, not the mean. A 4 ms average with an 12 ms tail will beat any motion loop that assumed 4 ms. Log max scan, overrun count, and the task that ran long. If a communications or diagnostic routine is occasionally inserted into the fast task, that is often enough.
2) Separate cyclic I/O from on-change or acyclic traffic. A flood of alarms, recipe downloads, or HMI reads on the same network or CPU as the motion task will not always show up in the “normal” scan statistic. If jitter appears only when a supervisor starts polling, move the heavy traffic off the motion task and off the motion network if you can.
3) Check time synchronization and where the setpoint is applied. If the PLC, the motion controller, and the drive do not share a common clock, interpolation and camming can look like mechanical backlash. Confirm that setpoints are applied on a scheduled I/O connection, not on a best-effort message.
4) Measure at the drive and at the I/O, not only in the PLC trend. A clean PLC tag with a noisy torque or following-error trace points downstream: network jitter, late frames, or a drive loop issue. A noisy PLC setpoint already explains the motion, and you should stop blaming the motor.
Open question: the last time average scan looked healthy and the axis still jittered, was it a scan tail, a polling burst, a clock mismatch, or the drive itself? Any case that only appeared when the HMI or MES started a heavy read? Please share the cycle target and how you logged the overrun.
A PLC program can report a stable average scan time and still leave a servo or coordinated axis looking jittery. Average scan is a poor proxy for the deadline the motion actually missed. The first job is to find whether the jitter is in the controller cycle, the network, or the drive.
1) Look at the worst-case scan and the jitter, not the mean. A 4 ms average with an 12 ms tail will beat any motion loop that assumed 4 ms. Log max scan, overrun count, and the task that ran long. If a communications or diagnostic routine is occasionally inserted into the fast task, that is often enough.
2) Separate cyclic I/O from on-change or acyclic traffic. A flood of alarms, recipe downloads, or HMI reads on the same network or CPU as the motion task will not always show up in the “normal” scan statistic. If jitter appears only when a supervisor starts polling, move the heavy traffic off the motion task and off the motion network if you can.
3) Check time synchronization and where the setpoint is applied. If the PLC, the motion controller, and the drive do not share a common clock, interpolation and camming can look like mechanical backlash. Confirm that setpoints are applied on a scheduled I/O connection, not on a best-effort message.
4) Measure at the drive and at the I/O, not only in the PLC trend. A clean PLC tag with a noisy torque or following-error trace points downstream: network jitter, late frames, or a drive loop issue. A noisy PLC setpoint already explains the motion, and you should stop blaming the motor.
Open question: the last time average scan looked healthy and the axis still jittered, was it a scan tail, a polling burst, a clock mismatch, or the drive itself? Any case that only appeared when the HMI or MES started a heavy read? Please share the cycle target and how you logged the overrun.