forum.cncdrive.com

Are there any plans to add G85? It's a boring cycle with feed on retract.

Thanks
Derek

Thanks Terry but If I have to step outside CAM I may as well hand code it in. It's what I'm doing now.

You can hand code a macro just like a gcode.
And macros can have parameters also just like gcodes.

cncdrive wrote:You can hand code a macro just like a gcode.
And macros can have parameters also just like gcodes.

What if I want to have 2 different hole depths with a single macro?

Here is how it works:
CAM writes G85, Derek forgets UCCNC doesn't do G85, run code,skips boring cycle, stop production hand write code.

Derek wrote:

cncdrive wrote:You can hand code a macro just like a gcode.
And macros can have parameters also just like gcodes.

What if I want to have 2 different hole depths with a single macro?

Here is how it works:
CAM writes G85, Derek forgets UCCNC doesn't do G85, run code,skips boring cycle, stop production hand write code.

Why not write a g85 macro with a textQuestion() at the start of it which reminds you of the variable changes required and halts until you click OK and you've edited the macro?

Derek wrote:

cncdrive wrote:You can hand code a macro just like a gcode.
And macros can have parameters also just like gcodes.

What if I want to have 2 different hole depths with a single macro?

Here is how it works:
CAM writes G85, Derek forgets UCCNC doesn't do G85, run code,skips boring cycle, stop production hand write code.

A macro can have parameters just like g-codes. A parameter can mean the hole depth for example for the macro and then you can program any hole depth for the macro programing that parameter.

There is the option to stop code execution if there are unknown g-codes in the program, you know if you set that then you can't forget that G85 is unknown, because then the code will not run or will give you a warning...

On the other hand I think we can probably add G85, but first I will have to study the G85, because I'm yet not familiar with that canned cycle type.