Hello,
In my CNC project, I move the axes with the "ControlAxisByPos" blocks at the output of the Interpolator block. But the "ControlAxisByPos" block falls into the "bStopIpo" state and starts doing the "AvoidGap" gestures. I couldn't get past this. How is it resolved?
This happens when I Jump in G-code.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if you have bAvoidGaps = TRUE, then this happens if the velocity of the fSetPosition is greater than the maximum velocity configured for the axis. See the axis configuration, tab "General", group "Dynamic Limits".
I've seen this solution on the codesys help pages. Currently, my speed, acceleration and deceleration limit values are high and I do not reach a value exceeding the limit. However, it falls into bStopIpo status.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know the jump happened. This happens in some movements, I wanted to prevent it. Also, do you know about the G75? G75 looks like an important code I need at this point but I couldn't figure it out!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
G75 synchronizes the path processing (in German "Satzvorlauf") with the interpolator. It makes sure that the next G-Code line is processed only after the interpolation has reached the line with G75.
All path processing buffers are emtpied before the next line is interpreted.
Hope this helps,
Georg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
In my CNC project, I move the axes with the "ControlAxisByPos" blocks at the output of the Interpolator block. But the "ControlAxisByPos" block falls into the "bStopIpo" state and starts doing the "AvoidGap" gestures. I couldn't get past this. How is it resolved?
This happens when I Jump in G-code.
Any ideas?
Hi ByCNC,
if you have bAvoidGaps = TRUE, then this happens if the velocity of the fSetPosition is greater than the maximum velocity configured for the axis. See the axis configuration, tab "General", group "Dynamic Limits".
https://content.helpme-codesys.com/en/CODESYS%20SoftMotion/_sm_edt_drive_general.html
Most likely, if you increase the velocity there, the problem disappears.
Best regards,
Georg
Hi George,
I've seen this solution on the codesys help pages. Currently, my speed, acceleration and deceleration limit values are high and I do not reach a value exceeding the limit. However, it falls into bStopIpo status.
Thanks.
I would recommend to trace the fSetPosition input of SMC_ControlAxisByPos. Most likely there is a jump in this position for some reason.
Hey George,
I know the jump happened. This happens in some movements, I wanted to prevent it. Also, do you know about the G75? G75 looks like an important code I need at this point but I couldn't figure it out!
Hi ByCNC,
G75 synchronizes the path processing (in German "Satzvorlauf") with the interpolator. It makes sure that the next G-Code line is processed only after the interpolation has reached the line with G75.
All path processing buffers are emtpied before the next line is interpreted.
Hope this helps,
Georg
Thanks Georg