https://forge.codesys.com/forge/talk/Engineering/thread/4c3b2a1abd/2026-10-27T16:35:07.197000ZRecent posts to SMC_Interpolator / CNC Abort – ControlAxisByPos Sometimes Remains Busy and Axis Continues Moving2026-10-27T16:35:07.197000Z2026-10-27T16:35:07.197000Zgseidelhttps://forge.codesys.com/u/gseidel/https://forge.codesys.com2169edb2a66cf062a10a9a65bbb039489f79ec71

<div class="markdown_content"><p>Hi kishan,</p> <p>I would recommend to first execute a stop (input bSlowStop or bQuickStop of the interpolator). Only when the interpolator has stopped you should abort the interpolator and preprocessing FBs. BTW., a new rising edge of the execute input should suffice.</p> <p>In case preprocessing is done in a different task: take care to write the abort signal to a local variable in the path and interpolation task and use this local copy. (Otherwise, some preprocessing FBs might see an abort and others not, in the same cycle of the task.)</p> <p>Best regards,</p> <p>Georg</p></div>

2026-09-25T09:19:48.408000Z2026-09-25T09:19:48.408000Zkishanhttps://forge.codesys.com/u/kishan/https://forge.codesys.come57fa8b9f12e4c8c9a8bcef95c023adef4214686

<div class="markdown_content"><p>Hello,</p> <p>I am working with CODESYS SoftMotion CNC using a preprocessing chain, SMC_Interpolator, and SMC_ControlAxisByPos for controlling the CNC axes.</p> <p>I have noticed an issue when aborting CNC execution.</p> <p>When I execute the Abort command, I abort both the CNC preprocessing blocks and SMC_Interpolator.</p> <p>Normally the CNC process stops correctly.</p> <p>However, occasionally after the abort:</p> <p>SMC_Interpolator has already been aborted.</p> <p>CNC preprocessing has also been aborted/reset.</p> <p>But SMC_ControlAxisByPos.bBusy remains TRUE.</p> <p>The corresponding physical axis can still continue moving for some distance.</p> <p>This does not happen every time.</p> <p>My basic sequence is similar to:</p> <p>G-code / CNC preprocessing<br/> ↓<br/> SMC_Interpolator<br/> ↓<br/> Transformation<br/> ↓<br/> SMC_ControlAxisByPos<br/> ↓<br/> SoftMotion Axis</p> <p>When the operator requests CNC Abort, I set the Abort inputs of the interpolator and preprocessing function blocks.</p> <p>My questions are:</p> <p>Does SMC_Interpolator.bAbort only stop/reset the interpolator, or should it also stop the motion currently being executed by SMC_ControlAxisByPos?</p> <p>Can SMC_ControlAxisByPos remain Busy after the interpolator has been aborted?</p> <p>If bAvoidGaps = TRUE, could SMC_ControlAxisByPos still be trying to reach the last fSetPosition using the fGapVelocity / fGapAcceleration / fGapDeceleration settings after the interpolator has stopped?</p> <p>What is the recommended sequence for safely aborting a running CNC program?</p> <p>For example, should the sequence be something like:</p> <ol> <li>Stop / Abort Interpolator</li> <li>Disable SMC_ControlAxisByPos</li> <li>Execute MC_Stop for all physical axes</li> <li>Wait until all axes reach standstill</li> <li>Abort/reset preprocessing blocks and CNC queues</li> <li>Reset CNC state</li> <li>Re-enable axis controllers</li> </ol> <p>Or is there a recommended CODESYS CNC method for performing a complete CNC Abort?</p> <p>I would especially like to understand why SMC_ControlAxisByPos.bBusy can occasionally remain TRUE and continue moving the axis even though the interpolator and preprocessing blocks have already been aborted.</p> <p>CODESYS SoftMotion CNC is being used with real EtherCAT servo axes.</p> <p>Any explanation about the correct abort/stop sequence would be appreciated.</p></div>