Yes, that’s pretty much it — we’ll have to see how things sort out.

Vee endmills are pretty straight-forward:

gcp endmill v.zip (1.1 KB)

hmm maybe but wouldn’t you want it not a pure V but more the path of a V… so more or less
2 V cylinders (begin and end) and then some triangle-bar shape between them?

It’s of course possible to just do a lot of these little cones in small steps from eachother to emulate a path… it is not always a bad idea to do things that way.

OpenSCAD has a Hull operation which allows combining two instances of an endmill for most sorts — that rather naturally brings us to the next sort of endmill, one which Camotics does not handle, cove radius endmills — it’s not workable to merely hull two instances, they have to be handled as a series of stacked angled cylinders.

So, we need to define a module which includes the coordinates for the beginning and end of the cut, as well as an input for how detailed it will be modeled as, in addition to the actual characteristics of the endmill itself.

Worked up a module for the radius cut in OpenSCAD previously, so no real need to do it in BlockSCAD:

``````//!OpenSCAD

Endmill_Diameter = 6.35;

Detail = 100;

\$fn = Detail * 1;

feedrate = 600;
plungerate = 150;
safeheight = 8;

module radiuscut(bx, by, bz, ex, ey, ez) {
n = Detail;
step = 360/n;

hull(){
translate([bx,by,bz])
translate([ex,ey,ez])
}

hull(){
``````

``````translate([ex,ey,ez+tool_radius_width])
``````

}

``````for (i=[0:step:90]) {
angle = i;
dh = dz-dzz;
hull(){
translate([bx,by,bz+dz])
translate([ex,ey,ez+dz])
}
}
}

radiuscut(0, 0, 0, 20, 20, 0);
``````

We put the commands for cutting into a .scad file and import it as a library and we can then have a LiveCode (or other) program which writes out the two sorts of files:

We then configure OpenSCAD for an external file and open the .scad file in it:

It’s then just a matter of creating the code to create the codes:

if you want any help converting the gcode into something else let me know be happy to help

(I have a pretty complete gcode parsing code base at this point, including one that deals with G2/G3 arcs correctly)

Neat! Thanks!

I’m hoping to just code the OpenSCAD end of things so that it’s orthogonal to G-Code — that’s not quite doable, since G-Code implements a given command based on current machine state, but I will hopefully manage something reasonably close.

the gcode parsing I normally do ends up converting gcode into a series of do_something(X1,Y1,Z1,X2,Y2,Z2) which seems to match the building blocks you’ve been building.
(even G2/G3 gets made into a series of small linear segments)

Some gcode (like Carbide Create) can also tell you the size of the stock and some properties of the tool (like diameter and ball radius)

1 Like

Yeah, I’ll be writing out suitable comments and so forth, once I get that far along w/ things.

Next up is encapsulating the G-code previews so that they will cut (will have to separate out the radius cut module since it’s not in BlockSCAD), which turns out to be quite simple:

but obviously it needs a module to select the correct module and parameters based on the tool # — if OpenSCAD had a facility for processing text we could import a .csv, but in the absence of that, we brute force it.

a tool that reads gcode and outputs this, can also do the CSV thing on that level

1 Like

Agreed… something like Convert to SVG [cnc-apps.com] ?

Once I’ve got the OpenSCAD end of things finalized, I’ll put it up on Github and anyone who find it of interest/use can make use of it — I’d love to see a tool which would accept G-Code and output a .scad file for this.

I’ll be happy to contribute that part of things…

do you have a preferred language, like javascript or python?
(this sort of thing is really not where C/C++ and co shine)

Python would be awesome, but JavaScript would probably be nicer in terms of providing access to folks.

In this case, brute-forcing is a series of If… end ifs:

For 90 degree arcs we seem to need a total of 8 different modules (CW/CCW and upper left, upper right, lower right, and lower left):

They’ll then be stitched into a single module which calculates which quadrant a given arc covers — working up a more general module which determines the arc angles as well will wait until that is needed for a project.

The garc modules are done — two versions, CW and CCW, though they’re a bad hack in that I just re-used existing arc modules, so directionality isn’t correct, and only 90 degree arcs are possible — addressing these failings will be done in a future update.