pppalain / blendercam Goto Github PK

ballcone used to ask for
layout.prop(ao,'ball_radius')
layout.prop(ao,'Cutter_diameter')
layout.label(text='Cutter diameter = shank diameter')
layout.prop(ao,'ball_cone_flute')

the angle was calculated from those values.

we would like the UI to have a radio button to select either angle or cutter length and do the appropriate calculation for angle if it is not given

special cases causes .geoms to not work.

inverse milling has no effect on the outcome

pocket fails with inside angles smaller than 90 degrees

In newer (pip installable) versions of opencamlib the python module is called opencamlib not ocl.

It's a pretty straightforward change to make it import opencamlib as ocl if import ocl fails, and at least waterline seems to work. Haven't tried anything else.

A user requested:

Is it possible, to cut like in two directions, like go z-3, cut to the end of path, in the end go to z-6 and cut i reverse directions - without going back in air and cutting from the starting point?

Please check the following Blender file, which has three operations:
https://www6.zippyshare.com/v/7zs1O3JS/file.html

• Op_Cutout is a simple cutout operation. Layer depth is 1mm, Depth start is at 0, Depth End is at -1 cm, and the generated operation displays the expected behaviour.
• Op_Curve_To_Path is a curve to path operation. Layer depth is 1mm, Depth start is at 0, Depth End is at -1 cm. The generated operation is wrong: the cut would happen above the z plan.
• Op_Curve_To_Path_Fixed is a curve to path operation. Layer depth is 1mm, Depth start is at -0.5 cm, Depth End is at -1.5 cm. With those parameters, the generated cut would stay below the z plane.

So there is a problem with those depth calculations: in order to have a normal cut below the z axis, one should only need to set the depth start at 0, and the depth end at -1 cm.

missing implementation for autocutting bridges

probably in ops, the source object should be made visible

If e.g. you select a text object and forget to convert to curve, or select a curve for something expecting a mesh or vice-versa, bad things happen, ranging from blender crash, to python errors.

The python errors I'm more cool with I guess, but the blender crashes are not so good.

when my project upgraded to version 1.0.1, the cam path like this :

after upgraded to version 1.0.2 or laters, like these:

How can i fix properties in cam setting, let cam path like ver 1.0.1 ?

Blender 4.1.1
BlenderCam Ver 1.0.1 to 1.0.2 ... 1.0.19

main cam operation setup :
3 axis, Profile(Cutout), Outside.

cam optimisation : use default setting. (without custom setting)

cam operation area :
selected "Use Layers", 0.1 mm
free movement height 5mm
Set max depth from "Material"

cam cutter :
Cutter : "End", diameter 0.6 mm, flutes 2.

medial operation throws an error if add pocket operation is checked. Operation does not get created.

error thrown:
TopologyException: unable to assign free hole to a shell at 0.077445618808269501 0.14669127762317657 0

some reports of waterline not working well

Steps to reproduce:

• create a curve
• set operation to Profile
• set Cut to Outside
• generate the path

The following error is generated:

Error: Python: Traceback (most recent call last):
File "/usr/local/blender_addons/blendercam/scripts/addons/cam/ops.py", line 214, in execute
gcodepath.getPath(context, o)
File "/usr/local/blender_addons/blendercam/scripts/addons/cam/gcodepath.py", line 510, in getPath
getPath3axis(context, operation)
File "/usr/local/blender_addons/blendercam/scripts/addons/cam/gcodepath.py", line 577, in getPath3axis
strategy.cutout(o)
File "/usr/local/blender_addons/blendercam/scripts/addons/cam/strategy.py", line 100, in cutout
p = utils.getObjectOutline(c_offset, o, offset)
File "/usr/local/blender_addons/blendercam/scripts/addons/cam/utils.py", line 1319, in getObjectOutline
for p1 in polygons: # sort by size before this???
TypeError: 'MultiPolygon' object is not iterable

The problem also exists with Cut: Inside, but Cut: On line works perfectly.

Perhaps related to Shapely 2.0.

curve to path seems to be limited below 0

If I scale a model up or down, blendercam will try to generate an operation based on the original size of the model. Right now, the solution is to apply all scale changes before generating the operation. There should be a way to take into account the scaling .