I’ve noticed when I’m doing V-carves and it gets to doing the fine details with the V-cutter, such as part of the lettering, the Z goes up maybe 1.5" and slowly moves closer and then makes a tiny cut.
I was wondering what setting I could change to lessen how much it goes up above the work piece (should be ok to go .5" above or .75" above and approach it faster)
anyone know what I can change to improve this?
Click Here
Check your retract height.
Ty, I’ll check when I get home, that’s probably right
Just seems my cuts would be twice as fast
I use .2" as my retract height. You may need to increase depending on how your workholding is set up. I mostly use side clamps for work holding. Nothing is above my stock unless it’s over to the side of the piece.
As @SDGuy suggested make your retract the minimum you can. However the lifting and plunging will not go away. But it will take less time to retract and plunge.
Ive been using plastic clamps that came with the machine and purchased some extras and 3d printed a few in custom lengths. I see what you did with clamping that work piece to scrap wood, that looks like a great way to assist holding
that sign looks awesome!
yeah I know it wont go away, but I was watching a carve the other day and was thinking “wow, it almost spends more time doing that motion than it does actually cutting” – why i thought I’d ask to see if anybody knew how to get it down
I’ve shared your frustration, while noticing that no matter how emphatically you tell your machine to fix (G1 feed rate) plunges and retracts it never listens. There’s a tool posted here to optimize retracts and plunges. I use an open source program, GCodeClean, that does a number of optimizations including intelligently converting plunges and retracts to G0 where appropriate. It worked well on older versions of Carbide Create. It also does traveling salesman optimizations by breaking gcode into blocks separated by travel moves and reordering them with a TSP algorithm. That’s currently somewhat cumbersome to use but did cut run times noticeably on the longer jobs I tested it with.
From reading the descriptions of both Fenrus’s utility may be doing a better G1 to G0 up/down optimization since it keeps track of where layers start, so you might want to try that first.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
