Run from line / set next statement

Moderators: TomKerekes, dynomotion

Post Reply
Chevvron
Posts: 39
Joined: Mon Apr 22, 2019 9:26 pm

Run from line / set next statement

Post by Chevvron » Mon Apr 13, 2026 10:51 am

Tom,
Our special purpose 8 axis machine sets a temporary datum after probing for each bearer set of operations in G code.
At the end of each bearer a G52 Y0 clears the temporary Datum back to the absolute position to move to for the next bearer where the probing routine and G code operations are repeated again, all 40 to 50 times down the 52 metre Y axis.
If there is a need to stop the process mid bearer then you need to MDI G52 Y0 before using the set next statement so the Y axis knows tge absolute position to repeat that particular bearer.

Is there a way to edit or script the run from line so that the G52 Y 0 can be performed automatically rather than the operator having to remember to do MDI G52 Y0 ?

Also the scan to find the parameters for set next statement set the Z axis safe move feedrate too high.
It is scary to see the Z axis retract at 6 metres a minute when 1 metre a minute is preferred.
I know this can be manually edited but it is another operator intervention rather than default.

It would be good to have the set next statement overall scriptable / configurable.

Any suggestions ?

Tim

User avatar
TomKerekes
Posts: 2915
Joined: Mon Dec 04, 2017 1:49 am

Re: Run from line / set next statement

Post by TomKerekes » Tue Apr 14, 2026 6:43 pm

Hi Tim,

I'm not sure I understand, but isn't there a way to write the GCode so G52 is not used for the absolute moves and therefore doesn't need to be set/cleared. For example set a fixture offset to run the local GCode. And one "zero" fixture offset for the absolute moves. Or use G53 to make the absolute moves?

Is there a way to edit or script the run from line so that the G52 Y 0 can be performed automatically rather than the operator having to remember to do MDI G52 Y0 ?
Wouldn't the GCode contain the "G52 Y0" so the operator would set the line to that? Or is the code being set to the middle of some operations?

Also the scan to find the parameters for set next statement set the Z axis safe move feedrate too high.
It is scary to see the Z axis retract at 6 metres a minute when 1 metre a minute is preferred.
I know this can be manually edited but it is another operator intervention rather than default.
The move to safez is a rapid move rather than a feed move. The rapid velocities are set in KFLOP/Kogna. See here. Do you need to perform rapids in Z at high rates for other purposes? If not, you might reduce the Z Rapid rate.
Regards,

Tom Kerekes
Dynomotion, Inc.

Post Reply