fellesverkstedet / bark-beetle-parametric-toolpaths Goto Github PK

I've had it a few times that I'm putting an angled edge on a wooden piece and then with the roughing or finishing it starts milling in the bottom so it cuts through the material. This causes more vibration on the working piece or when all sides are angled, makes the piece come loose.

Sometimes I link geometry to bark beetle by selecting by layer and then it happens that it takes geometry outside of the machine area(causing the machine to hit the limit switch). I think it could be useful to have a component that check whether or not the geometry linked with bark beetle is on the working area.

I might give a go on this soon. Shouldn't be too hard.

Bug copied from file - explanation?

Copied from file - Explanation?

See example below: Area with X should create a pocket as well. But in current logic it defines it as an area inside an area and therefore skipping it.

I came across this solution for making curves go the same direction. Seems to speed up things a lot (x 100 in example below) since there's no need for offset.

Enhancement copied from file

Bug copied from file

As discussed in previous issues here and here

I've just quickly tried it out I think and I believe the boundary surface component tends to take more time to calculate than the approach we're using now. I can't remember how much the difference was but it if it is sufficient it might come down to choosing between endless curves in curves or speed, unless we find an even better approach.

Missing image files

Just a note that Barkbeetle is working on OSX, however, CNC cut is not being registered so no cut data is going through the system.

This is most likely because of a silly difference between OSX and windows...

Maybe we can look at it in person.

Note, Drill, Pocket, engrave and 3D are all working. Tabs can't be tested due to CNC cut not working.

Bug copied from file

Bug copied from file

Bug copied from file

Enhancement copied from file

Enhancement copied from file

Bug copied from file

Bug copied from file

I'm thinking about how to clean up the components for easier debugging. And was wondering if it makes sense to use the system they use for organizing electric cables. One main bundle of wires going through the whole definition and the necessary input branching out and into the bundle again where needed. See below:

This leads me to the next question. In Grasshopper 1 (Rhino6) there are so-called "relays" which make it easier to implement this system. You double click on a wire and you get a relay. So then the question is, do we make the switch to Rhino6 or not yet? I tried opening a file with relays in Rhino 5 but it gives me a warning saying it does not recognize the relay component and then deletes it. I guess we could work for now with the standard geometry components to do the same, it might just be more work.

Positive: Can increase milling dramastically in some cases (up to 40 percent faster)


Negative: Decreases calculation speed of grasshopper

Bug copied from file

Bug copied from file

But strangely enough this doesn't happen when opening the "Bark beetle cnc milling" document. Does the latter one contain a different version? Which one is up to date?

Question copied from file

Bug copied from file

Bug copied from file

Bug copied from file

Proof of concept:

Bug copied from file

Bug copied from file

Bug copied from file

Bug copied from file

It would be nice if we can somehow see which direction it's going to cut. Maybe a small triangle at the start and end point of the toolpath?

There's a difference in color for when the bit plunges down and up, but I don't know which color is up and which is down. This is also related to the issue on seeing the cutting direction I guess.

Enhancement copied from file

It would be awesome if pockets that touch the edge would overlap, to make sure there's no rounded corner because of the geometry of the bit. I guess this would require the extra input of bit diameter.

Bug copied from file

Bug copied from file

Enhancement copied from file

In postprocessor inch conversion slows down the definition - Remove this feature?
Link to component

Autotabbing currenty only works for square pieces, putting tabs in the corner. This component could use some improvements.

Bug copied from file

Enhancement copied from file

Bug copied from file

Question from file