Charlie...
I've been using a free surfacing gcode generator. Is there a way to create a surfacing tool path ?
If not maybe as a create new layer ?
Thanks Joe...
CAM software developed by artists for artists to create unique and original works on a 3-axis CNC router or mill. · By
Hi Joe,
Are you talking about just surfacing a regular rectangular area flat? In that case you can just create a project and a Parallel Carving operation with the cutting direction set to Mixed (or if you specifically want Conventional/Climb you can do that too) and just let it generate a toolpath that fills the entire canvas. Then it's just a matter of designating the dimensions of the canvas. You also can set the Canvas Resolution pretty low too as there's no height information that it needs to worry about contouring.
- Charlie
Charlie...
I do log slices, I flatten them before carving. I can do your suggestion with a small canvas z . A lot of times I have to do multiple passes. Is there a way to pause gcode between z changes. Example: If I want a total depth of .4 with a .1 cut , so from . 1 to .2 to .3 it would pause between z changes so I can decide to continue or terminate.I never really know how much I have a to remove.
Thanks Joe
Hi Joe,
The first option that comes to my mind would be to make multiple separate 2D milling operations that cut at the different depths, and then using a custom modified G-code post specifically for the project file that includes a pause command block between operations. You would need to include the pause command in either the tool change block, one of the the spindle command blocks, or one of the coolant command blocks. It would basically be a bit of a hack where you're just including the pause command inside one of the command blocks that are issued on a per-operation basis. Then with separate operations each cutting a different level, and exporting the G-code using such a custom post as described - with operations combined, you would have the desired result where each cut level would include a stop to let you push a button and tell it to continue.
The second option would be creating each cut depth as a separate option and exporting them as separate G-code files, which would require opening each one to run it for each cut level.
That's the best I can come up with at the moment - but it does give me an idea to include some new functionality in the G-code post-processor format that allows for different commands to occur at different times, such as per-operation, per-toolchange, or every N operations, etc.. I'll have to think about that though and see what I come up with :]
- Charlie
Hi Joe,
The estimated run times are affected by the acceleration setting under CNC/CAM Settings which you will want to set to your machine's actual acceleration speed to make the run times more accurate :]
Unfortunately there's really no way to 100% accurately determine what the runtime will be for all possible machines in the world simultaneously, one can only hope to get close enough to be useful. It's at least nice to know if something is going to take 30 minutes vs 30 hours!
- Charlie
That's really interesting. There must be somewhere else in PixelCNC's code that is causing it to skip outputting the block if the coolant is set to None, even though the part that actually outputs the coolant block treats None/Off the same :P It will be fixed for the next public release! :]
- Charlie