See discussion on google group:
https://groups.google.com/forum/embed/?place=forum%2Fblender-cam-forum&theme=softgray&hideforumtitle=true&showsearch=false&showpopout=true&showtabs=true&parenturl=http%3A%2F%2Fblendercam.blogspot.ca%2Fp%2Fblog-page.html&afterlogin=&pli=1#!category-topic/blender-cam-forum/development/hQCkP0E5-g8

The A axis should be used for 4th axis indexing? I have built my own 4th axis along with controller and I have that 4th axis as A based on the literature I have read on the Internet. It should not matter if the 4th axis is orientated x,y, or z. The g-code that Blendercam generates uses B axis for rotated indexing when the 4th axis is X. If I switch the return values in rotTo2axes() in utils.py then A axis gets used properly.

Things get stranger when the 4th axis is selected to Y or Z but I will expand on that later.

when curve is shorter than actual length of bridge, or close to it, second 
bridge goes completely out of path. 

Original issue reported on code.google.com by [email protected] on 8 Feb 2014 at 6:10

Attachments:

• uhmw-sample.blend

Hi i found a strange bug using blender 2.77 in tool path generation ( i know 2.77 not supported yet)
better a pic

thx!

The tool path is not linear

test.blend.zip

Missin informations what librariers should be installed first, at least on windows.
And what blender version is the best to use.

Thus we can easily navigate through the many toolpathes, and won't be confused. Also we can synchronise life of that object with toolpath in that "CAM operations" panel: If we delete toolpath, then toolpath mesh also must be deleted.

I think there might still be an issue with the ray cast. See my comments on the ray cast commit:
e16f252

Can we bump the version number of the addon? Maybe to "0.8.1" or "0.9.0" since there have been a lot of changes, bugfixes, and improvements. Would make it easier to differentiate who is using Blendercam Github version or another one when discussing problems on the forum.

By milling some oak I broked many carbide mills (R0.5 carbide each for 2-3$).

So I've beign thinking how to reduce breakage 'flow' of my instruments. And I want to know your opinion on that.

Idea of "smart" :) tool speed adjustor.

Well. This algorithm should 'know' how much material tool is cutting in any node its toolpath. Suppose we will measure this parameter in percentage of tool cutting surface (tool cutting load)
For example (for cross strategy.):
100% (cutting load) - tool is plunging into the cutting material

As I know plunge speed adjustion is already implemnted in blendercam.

100% (cutting load) - tool is cutting the first furrow (or line. If it's a correct translation)

It seems tool speed here should be equal to plunge speed.

50-70% (cutting load)
1st half of a Cross toolpath.

The second half of a Cross toolpath has the minimum cutting load (10-20%)

Here we can cut the material at a full speed

I think cutting point percentage can be found based on detecting of intersection of tool object and generated simulation mesh.
Here is a sketch of an idea. I know that's not easy to implement, but I just wanted to share the idea for future development. Thanks.

I've encountered an error when trying to generate cutout operation.
I've attached files.
In zip file there is blend file and svg file which was imported.

ornament.svg.zip

ornamentlog.txt

This feature may already exist, but I can't find it. When doing profile cutout, what is the chance of being able to cut into the inside corners to avoid leaving a radius such as described here:

http://blog.inventables.com/2014/06/learn-about-milling-inside-corner.html

It would be nice if the Wikis feature for this project was enabled. I would like to start contributing to a user manual of some sort and the Wikis would be a good place to start.

Hi. Is it possible to calculate path around the mesh including its surface modifiers?

If Blendercam will work with modifiers we'll get many good things:
1. Higher frames per second in 3D view (because we can make modifier invisible)
2. Total size of .blend file will be much more lesser. For now I'm working with 300Mb blend file. I'm syncing it over cloud storage.
3. Less copy-paste user operations. (I forced to duplicate my object with modifiers, apply modifiers for it. So for one object I must have at least one copy)

Bridges also could be generated from 1 curve object with attached modifiers to it.

Use case:
Very often, I'm creating bridges using one curve with attached array and mirror modifiers to it. Thus I have one quickly managed object which represents all bridges. Then, I'm converting it to mesh (modifiers automatically are applying), than again converting it back to curve. At last I have my bridges, but they are in a single object. So I forced to create a group based on that single object, and only then I proceed with bridge generation.

So It would be very good if we would have a bridge generation based on one curve object with an attached modifiers to it.

When you try to put to put the packages listed as dependencies OpenCAMLib I get a message saying that the package libomp-dev is missing in the repository.
Here is my /etc/apt/sources.list
`deb http://ftp.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie main contrib non-free

deb http://mirror.yandex.ru/debian/ jessie main contrib non-free

deb-src http://mirror.yandex.ru/debian/ jessie main contrib non-free

deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-backports main contrib non-free

deb http://mirror.yandex.ru/debian/ jessie-backports main contrib non-free

deb-src http://mirror.yandex.ru/debian/ jessie-backports main contrib non-free

deb http://ftp.debian.org/debian/ jessie-backports-sloppy main contrib non-free

deb-src http://ftp.debian.org/debian/ jessie-backports-sloppy main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

jessie-updates, previously known as volatile

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://mirror.yandex.ru/debian/ jessie-updates main contrib non-free

deb-src http://mirror.yandex.ru/debian/ jessie-updates main contrib non-free

deb http://ftp.debian.org/debian/ jessie-proposed-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-proposed-updates main contrib non-free

deb http://ftp.debian.org/debian/ testing main contrib non-free

deb-src http://ftp.debian.org/debian/ testing main contrib non-free

deb http://ftp.debian.org/debian/ testing-updates main contrib non-free

deb-src http://ftp.debian.org/debian/ testing-updates main contrib non-free

deb http://ftp.debian.org/debian/ testing-proposed-updates main contrib non-free

deb-src http://ftp.debian.org/debian/ testing-proposed-updates main contrib non-free

deb http://ftp.debian.org/debian/ unstable main contrib non-free

deb-src http://ftp.debian.org/debian/ unstable main contrib non-free

`

Hi, blender CAM 0.90, ubuntu, the CAM toolbar not displayed when started with blender-softwaregl (it wont start with blender in remote desktop connection).
Here what I see after downloading blender CAM:
https://plik.ovh/file/9tHLlLnp8GGHocir/KCqPDsOfofIsKk6n/Screenshot%20from%202016-05-30%2017:53:39.png

Hi, folks.
I would like to propose use Edge Data "Crease" parameter to manually set the speed machine on "hard" places of toolpath.
This feature will be very useful on the beginning of every toolpath with deep plunge. A tool should mill the groove by cutting the material with all of its cutting surface, it's the most dangerouse circumstance of tool brokening. The next step will be much more easier for tool and we can increase the feedrate.
For example.
Suppose I have a toolpath which begins from deep plunge line, and supplose that the plunge depth and default feedrate are too tough for my tool. Ofcourse somehow we can implement an algorithm which will automatically detect such "hard" path regions and it will appropriatelly set the feedrate. But it's more easily give to the user ability to decide where he can slower/faster the feedrate.

I can quickly change 'Crease' parameter by pressing shift+e and moving the mouse. This data would be interpretted by postprocessor to change the feedrate
There is a problem. Crease parameter has range from 0.00 to 1.00. So we should think about formula how to set the feedrate slower/faster using such a range.

What are your suggestions about this enhancement?

Not a whole lot to say otherwise. I don't have root on that machine right now so my options are limited.

Thanks for this software though, I have another 64 bit computer I can generate files with.

first of all, thank you so much for this wonderful work you are doing with blendercam!

after using the latest commit, it gets stuck in sorting paths (parallel strategy) - I am using blender 2.70 (under ubuntu 15.10). any ideas where this comes from?

all the best and thank you again for providing what is probably the best CAM option for linux so far!

Friday works.
Today not work!

Traceback (most recent call last):
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/ops.py", line 218, in execute
    utils.getPath(context,o)
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 3324, in getPath
    getPath3axis(context,operation)
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 2890, in getPath3axis
    chunks.extend(sampleChunks(o,pathSamples,layers))
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 332, in sampleChunks
    oclSample(o, pathSamples)
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/opencamlib/opencamlib.py", line 106, in oclSample
    exportModelsToSTL(operation)
  File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/opencamlib/opencamlib.py", line 88, in exportModelsToSTL
    bpy.ops.export_mesh.stl(check_existing=True, filepath=file_name, filter_glob="*.stl", use_selection=True, ascii=False, use_mesh_modifiers=True, axis_forward='Y', axis_up='Z', global_scale=1.0)
  File "/home/kylotron/Scaricati/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/modules/bpy/ops.py", line 189, in __call__
    ret = op_call(self.idname_py(), None, kw)
TypeError: Converting py args to operator properties: : keyword "use_selection" unrecognized

location: <unknown location>:-1

bpy.context.space_data.recent_folders_active = 2

Hi i'm trying to install blendercam in a windows 10 machine

but when i load the addon in user preferences it drops the following error

found bundled python: C:\PortableApps\Blender-2.77a\2.77\python
Traceback (most recent call last):
  File "C:\PortableApps\Blender-2.77a\2.77\scripts\modules\addon_utils.py", line 330, in enable
    mod = __import__(module_name)
  File "C:\PortableApps\BlenderCam\scripts\addons\cam\__init__.py", line 34, in <module>
    from cam import ui, ops, utils, simple, polygon_utils_cam#, post_processors
  File "C:\PortableApps\BlenderCam\scripts\addons\cam\ops.py", line 26, in <module>
    from cam import utils, pack,polygon_utils_cam,chunk,simple
  File "C:\PortableApps\BlenderCam\scripts\addons\cam\utils.py", line 41, in <module>
    from cam import chunk
  File "C:\PortableApps\BlenderCam\scripts\addons\cam\chunk.py", line 24, in <module>
    from shapely.geometry import polygon as spolygon
  File "C:\PortableApps\Blender-2.77a\2.77\python\lib\shapely\geometry\__init__.py", line 4, in <module>
    from .base import CAP_STYLE, JOIN_STYLE
  File "C:\PortableApps\Blender-2.77a\2.77\python\lib\shapely\geometry\base.py", line 9, in <module>
    from shapely.coords import CoordinateSequence
  File "C:\PortableApps\Blender-2.77a\2.77\python\lib\shapely\coords.py", line 8, in <module>
    from shapely.geos import lgeos
  File "C:\PortableApps\Blender-2.77a\2.77\python\lib\shapely\geos.py", line 114, in <module>
    _lgeos = CDLL("geos_c.dll")
  File "C:\PortableApps\Blender-2.77a\2.77\python\lib\ctypes\__init__.py", line 347, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: [WinError 126] No se puede encontrar el módulo especificado

<!> event has invalid window

any ideas?

is this a blendercam issue or is a shapely issue ??

thx

3020_cnc_end_switch_x_axis_plate.stl.zip

Here's a part, that has two pockets (that are open on the edges). In the right pocket the middle wall got processed correctly - it has waterlines. The other two walls miss the waterlines for some reasons.
Also area filling in the right pocket did not work exactly right - the rightmost toolpath went up. The same toolpath in the left pocket is at the correct level.
stl file is in the attached zip.

blendercam commit e16f252
blender version 2.76 i686
shapely 1.5.13
Ubuntu Linux 15.04 (Vivid Vervet) i686

P.S. In general I wonder, which strategy would be able to give best results for this part, so that walls of the pockets would be flat.

I have set up an Edge branch (leading edge stuff) which will be for new features that will eventually be the next new release. Since its leading edge it can be unstable at times ie crashes and things not working like they should.

https://github.com/vilemnovak/blendercam/tree/edge

I see the master branch as being the stable branch of the most recent release. Commits to the master branch would be mainly bug fixes until the next release.

So what is in the edge branch right now? Here is a list of things that have been added since 0.9 release:

• pocket operation now supports "first down". This means that if first down is enabled then each pocket will be completed (including all layers) before moving on to the next pocket.
• A gcode header and trailer can be enabled for each operation allowing you to put in your own gcode commands. The validity of the commands is not checked so be careful.
• Block numbering can be turned on or off for most post processors. You can also define the starting number and how much it increments by.
• Tool change commands can be enabled/disabled along with using G43.
• Medial axis operation (v-carve) now supports layers and first down. If first down and layers are enabled then the carve stroke is completed to full depth before proceeding to the next stroke.

The following is all I get in the error report. The directory is there and the file is also. I can open the file in Krita and it looks fine. What have I done wrong? Didn't have th eproblem in previous version.
Also when trying to enable the addon received errors about not having msvcp140.dll and vcruntime140.dll on my system. Had to download them. Should they be included in the BlenderCam download?
progress{building paths from chunks}
3051
3051
3051
3051
0.2200002670288086
0.020000219345092773
progress{exporting gcode file}
10889
1
2.020002603530884
progress{total time 2.759%}
numpy to image _Operation_1_sim.exr
569 569

time 0.37000036239624023
Traceback (most recent call last):
File "C:\Users\Paul\BlenderCAM\blender-2.76\2.76\scripts\addons\cam\ops.py", line 338, in execute
utils.doSimulation(operation.name,[operation])
File "C:\Users\Paul\BlenderCAM\blender-2.76\2.76\scripts\addons\cam\utils.py", line 870, in doSimulation
i=bpy.data.images.load(iname)
RuntimeError: Error: Cannot read 'temp_cam_Operation_1_sim.exr': No such file or directory

location: :-1

location: :-1

Is pocket operation working correctly? When i have a rectangle for example, and change pocket start position for example from outside to inside and export file, i have the same files. How works middle option? File seems to be the same.

What do you think about zigzag pocketing? It looks much better on plexi for example, when ther are only straight lines and one around the shape - on contour.

Hi...

i have compiled opencamlib... but not working on blendercam!

Help me! please!

bpy.ops.object.select_all(action='DESELECT')
bpy.ops.object.duplicate(linked=False)
bpy.ops.object.transform_apply(location=True, rotation=True, scale=True)
bpy.ops.transform.resize(value=(1000, 1000, 1000), constraint_axis=(False, False, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1, snap=False, snap_target='CLOSEST', snap_point=(0, 0, 0), snap_align=False, snap_normal=(0, 0, 0), texture_space=False, release_confirm=False)
bpy.ops.object.transform_apply(location=True, rotation=True, scale=True)
bpy.ops.object.delete()
Traceback (most recent call last):
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/ops.py", line 218, in execute
utils.getPath(context,o)
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/utils.py", line 3236, in getPath
getPath3axis(context,operation)
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/utils.py", line 2614, in getPath3axis
oclGetWaterline(o, chunks)
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/opencamlib/opencamlib.py", line 166, in oclGetWaterline
if os.path.isdir(bpy.utils.script_path_pref()+"/addons/cam/opencamlib"):
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

location: :-1

Sorry, but I don't know English, this will simply leave the link to the video:
https://youtu.be/MNBpCfhOeGo

Meaning: when you change the way the tasks workspace the patch is shifted relative to the model.
Blendercam installed from github.

Original text ( Russian ) -----------------------------------------------------
Извините, но я не знаю английский, по этому просто оставлю ссылку на видео:
https://youtu.be/MNBpCfhOeGo

Смысл: при изменений способа задачи рабочей области патч смещается относительно модели.
Blendercam установлен с github.

curves-on-sheet.blend.zip

Blender file attached.
I've used blender 2.69

Here is the output from console:

Traceback (most recent call last):
File "/home/narvf/Pulpit/blendercam-master/scripts/addons/cam/ops.py", line 253, in execute
pack.packCurves()
File "/home/narvf/Pulpit/blendercam-master/scripts/addons/cam/pack.py", line 119, in packCurves
if allpoly.disjoint(ptrans):
AttributeError: 'PreparedGeometry' object has no attribute 'disjoint'

location: :-1

Is it possible to add an overcut option in corners? I have no experience in programming.
This is useful for example in plywood when i have two or more elements to put on inside another.

Like here for example
http://www.cambam.info/doc/plus/images/overcut.png

The alternative algorithm that uses numpy which is now the default, does not have code to support parallel stepback. Will this be added or would a patch be a good idea?

Same file used yesterday ... parallel strategy applied to the plate with the limit set on a curve ...
And I do not understand why!
I have not updated anything.

validity
validity
validity
progress{building path pattern}
progress{0.6538865566253662}
convertViewVec: called in an invalid context
Traceback (most recent call last):
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/ops.py", line 218, in execute
utils.getPath(context,o)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 3284, in getPath
getPath3axis(context,operation)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 2854, in getPath3axis
chunks.extend(sampleChunks(o,pathSamples,layers))
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 324, in sampleChunks
getAmbient(o)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 1775, in getAmbient
polys = curveToShapely(limit_curve)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/utils.py", line 1364, in curveToShapely
chunks=curveToChunks(cob)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/chunk.py", line 813, in curveToChunks
co = meshFromCurve(o)
File "/home/kylotron/Scaricati/blendercam/scripts/addons/cam/chunk.py", line 793, in meshFromCurve
co.data.dimensions='3D'
AttributeError: 'Mesh' object has no attribute 'dimensions'
location: :-1
location: :-1

For multiple-layer Parallel operation sortChunks function makes path calculation very slow.
Included paralllel operation computes in 7 second with single layer and 830 seconds with 3 layers. For more complex operations it takes even longer.

According to cProfile Python built-in profiler, 99% of calculation time for 3-layer operation is spent in getNextClosest function called from sortChunks( in total 15740 calls, 0.049s each):

ncalls  tottime  percall  cumtime  percall filename:lineno(function)
    1    0.000    0.000  829.630  829.630 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/ops.py:195(execute)
    1    0.006    0.006  829.630  829.630 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/utils.py:3181(getPath)
    1    0.003    0.003  826.420  826.420 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/utils.py:2323(getPath3axis)
    1    0.032    0.032  821.230  821.230 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/utils.py:1470(sortChunks)
15740  765.601    0.049  821.094    0.052 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/chunk.py:132(getNextClosest)

For single layer there are only 68 calls, each less than 1 millisecond:
68 0.000 0.000 0.000 0.000 /home/ksuprynowicz/blender_cam_SE_mk3/blendercam/scripts/addons/cam/chunk.py:132(getNextClosest)

In earlier versions(probably pre-2015) there was no such problem.

Link to the test file with single and multilayer operation used for profiling:
https://drive.google.com/file/d/0B0C06H4DvveCX2dXbUEwVEExRGc/view?usp=sharing

Hi all,
is possible to translate blendercam at other languages?

utils.py has 2 places that say 'INCH'. They need to be changed to 'IMPERIAL' to produce the expected output.

Thanks

Blendercam generates code
T1 M06 G43

I don't have an automatic tool change system. I'm changing tool in semi-automatic way by manually changing tool and probing it and calculating and applying offset difference using g code program. So for my machine

T1 M06 G43 is a bad command, because it applies offset for tool 1 from tool offsets table.

How about to add an option to disable tool management or better to give to user choice add a code snippet for auto tool changing sequence?

Tried to auto generate bridges when doing a profile cutout of a simple circle curve and an exception occurs in Shapely. I haven't investigated any further but someone else also ran into the problem so figure its worth looking into now.

Only occurs with github master.

https://groups.google.com/forum/#!category-topic/blender-cam-forum/8Ec7X12qNn8

The traceback that I get:

Traceback (most recent call last):
  File "/home/nfz/SoftwareDevelopment/blendercam1/scripts/addons/cam/ops.py", line 690, in execute
    utils.addAutoBridges(o)
  File "/home/nfz/SoftwareDevelopment/blendercam1/scripts/addons/cam/utils.py", line 1961, in addAutoBridges
    d1 = c.project(sgeometry.Point(maxx+1000, (maxy+miny)/2.0))
  File "/home/nfz/SoftwareDevelopment/blender-git/build/bin/2.76/python/lib/python3.5/site-packages/shapely/impl.py", line 30, in wrapper
    return func(*args, **kwargs)
  File "/home/nfz/SoftwareDevelopment/blender-git/build/bin/2.76/python/lib/python3.5/site-packages/shapely/geometry/base.py", line 665, in project
    return op(self, other)
  File "/home/nfz/SoftwareDevelopment/blender-git/build/bin/2.76/python/lib/python3.5/site-packages/shapely/linref.py", line 17, in __call__
    self._validate_line(this)
  File "/home/nfz/SoftwareDevelopment/blender-git/build/bin/2.76/python/lib/python3.5/site-packages/shapely/linref.py", line 13, in _validate_line
    raise TypeError("Only linear types support this operation")
TypeError: Only linear types support this operation

Branch name: Latest

Purpose of code changes on this branch:
Adding a new Preprocessor to BlenderCam


When reviewing my code changes, please focus on:


After the review, I'll merge this branch into:
/trunk

Regards
Juan-Carlos

Original issue reported on code.google.com by [email protected] on 9 Apr 2014 at 10:53

Attachments:

• winpc.py
• init.py
• utils.py

i can't run
blender-2.76b-linux-glibc211-x86_64_CAM_0.9.tar.gz
nor
blender-2.76b-linux-glibc211-i686_CAM_0.9.tar.gz
on my Ubuntu 15.11...
blenderCAM is not available and throws exceptions to the console...

in the console, blender tells:

Read new prefs: /home/me/bin/blenderCAM-release/2.76/config/userpref.blend
found bundled python: /home/me/bin/blenderCAM-release/2.76/python
addon not found: 'space_view3d_screencast_keys'
addon not found: 'io_import_scene_dxf'
Traceback (most recent call last):
  File "/home/me/bin/blenderCAM-release/2.76/scripts/modules/addon_utils.py", line 324, in enable
    mod = __import__(module_name)
  File "/home/me/bin/blenderCAM-release/2.76/scripts/addons/basrelief.py", line 2, in <module>
    import numpy
  File "/home/me/.local/lib/python3.4/site-packages/numpy/__init__.py", line 201, in <module>
    from . import random
  File "/home/me/.local/lib/python3.4/site-packages/numpy/random/__init__.py", line 99, in <module>
    from .mtrand import *
ImportError: /home/me/.local/lib/python3.4/site-packages/numpy/random/mtrand.cpython-34m.so: undefined symbol: PyFPE_jbuf
addon not found: 'export_svg'
addon not found: 'curve_tools'
Traceback (most recent call last):
  File "/home/me/bin/blenderCAM-release/2.76/scripts/modules/addon_utils.py", line 324, in enable
    mod = __import__(module_name)
  File "/home/me/bin/blenderCAM-release/2.76/scripts/addons/cam/__init__.py", line 34, in <module>
    from cam import ui, ops, utils, simple, polygon_utils_cam#, post_processors
  File "/home/me/bin/blenderCAM-release/2.76/scripts/addons/cam/ops.py", line 26, in <module>
    from cam import utils, pack,polygon_utils_cam,chunk,simple
  File "/home/me/bin/blenderCAM-release/2.76/scripts/addons/cam/utils.py", line 37, in <module>
    import numpy
  File "/home/me/.local/lib/python3.4/site-packages/numpy/__init__.py", line 180, in <module>
    from . import add_newdocs
ImportError: cannot import name 'add_newdocs'
addon not found: 'add_mesh_pipe_joint'
addon not found: 'delaunay_voronoi'
addon not found: 'space_view3d_precise_align12'
addon not found: 'macros'

i can run blender-2.70a-linux-glibc211-x86_64_CAM_0.8.0.tar.gz is on that system successfully

Hello. I noticed that all kinds of generated toolpathes begin from the same fast movements.

1. It is a rapid traverse to the X0 Y0 Z0 location of current fixture:
   G00 X0 Y0 Z0
2. Straight linear movement to the first point of current toolpath
   

IMHO these are unsafe movements. You can damage your spindle on the 1 and 2 movements. I propose to split start position to three movements:

1. Go to the highest available Z coordinate of your machine.
   For example the highest available Z movement on my machine is
   G53 G0 Z0
2. Go to the X0 Y0 of current fixture.
   G54 G0 X0 Y0
3. Go to the first point of current toolpath.

Thus we can be sure that our tool won't be cracked.

Could you please me help how to implement such feature. Just point me were to dig the code in the project. Thanks.

Asked me on one forum "Blender CAM as far as I understand a free product? As the Blender?"
At first I answered "Yes, all right."
And then I decided, and I will look what is written in the repository.
And there is nothing written, no license, and therefore to hold the product for use in the work.
Please add the license code, it would be better of course copyleft, the bourgeoisie was bad.
Original text:
Спросили меня на одном форуме "Blender CAM насколько я понимаю бесплатный продукт? Так же как и сам Блендер?"
Сначала я ответил "Да, правильно понимаете."
А потом решил, а посмотрю я, что написано в репозитории.
А там ничего не написано, лицензии нету, а значит и брать продукт для использования в работе нельзя.
Добавьте пожалуйста лицензию на код, лучше бы конечно копилефт, чтобы буржуям плохо было.

When i was trying to add preset for operation which i was using frequently i got an error

See the attached blend file and the cutter starting below surface (-6mm) for 
the "trous_retournement" operation.

Same for the "trou_pos" operation, starting at +7mm instead of +10mm

Original issue reported on code.google.com by [email protected] on 11 Mar 2015 at 10:27

Attachments:

• big_error_latest_svn.blend

Don't close this issue. It is used for uploading images for the Wikis.
See http://solutionoptimist.com/2013/12/28/awesome-github-tricks/

Hello, I want to offer you in the section "CAM Material size and Position" button instead of the "Position Object" to make two buttons:
1)the First button "Zero of material surface" will configure BlenderCAM for creating NC programs for engraving,
the object will be positioned at the top of the lower region Z<0, and the quick movements will be above zero.

2)the Second button "of the Worktable Zero" button to set BlenderCAM to create NC programs for 3D milling reliefs.
The zero pack is placed on the surface of the desktop, and the whole process is conducted in the positive part Z>0

I certainly poorly explained, to understand the character of the query show the text and illustrations attached to the milling professional and he will explain what it is.

Original text(Russian):
Здравствуйте, хочу предложить вам в секции "CAM Material size and Position" вместо кнопки "Position Object" сделать две кнопки:
1)Первая кнопка "Zero of material surface" будет настраивать BlenderCAM для создания УП для гравировки,
при этом объект будет позиционироваться в верху нижней области Z<0, а область быстрых перемещений будет выше нуля.
2)Вторая кнопка "Zero of Worktable" кнопка будет настраивать BlenderCAM на создание УП для 3D фрезерования рельефов.
При этом ноль УП распологается на поверхности рабочего стола, а весь процесс ведётся в положительной части Z>0

Я конечно плохо изложил, чтобы понять сущность запроса покажите этот текст и приложенные иллюстрации профессиональному фрезеровщику и он вам объяснит в чём дело.

Hello to the great development Team behind Blendercam.

I was wondering if there would be a way to speed and simplify the gcode generated. Here is an example using block-all:

N2100 G01 Y22.5
N2110 G01 Y27.5
N2120 G01 Y32.5
N2130 G01 Y32.999
N2140 G01 X22
N2150 G01 X27
N2160 G01 X32
N2170 G01 X32.999
N2180 G01 Y28
N2190 G01 Y23
N2200 G01 Y18
N2210 G01 Y17
N2220 G01 X28
N2230 G01 X24.333

It could best be generated as:

N2100 G01 Y22.5
N2130 G01 Y32.999
N2140 G01 X22
N2170 G01 X32.999
N2180 G01 Y28
N2210 G01 Y17
N2220 G01 X28
N2230 G01 X24.333

Am I missing something in the settings perhaps?

Many thanks and please keep on carrying such a good work (btw, sorting is working well now, still very slow on complex models but that's an issue with python I guess...).

Cheers

I was investigating an issue with dwell gcode being generated by iso.py and have discovered it was fixed in Heekscnc many years ago (Sep 2013). We should look at updating NC library since it looks like several other bugs were fixed in the last 3 years.

Some discussion of the issue is here:
http://blendercam.blogspot.fi/p/blog-page.html?place=msg%2Fblender-cam-forum%2F9xZe9V8S4iQ%2FgXKwWQjTAAAJ

Hello Team,

I am trying to use the autobridge function of the profile/cut operation, and get the following error:

read blend: /home/ecl/wifiwater/wifiwater_esp8266_pic18/trunk/esp8266/CAD/enclosure_100/profiling.blend
Traceback (most recent call last):
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/ops.py", line 687, in execute
utils.addAutoBridges(o)
File "/opt/blender-2.76b-linux-glibc211-x86_64/2.76/scripts/addons/cam/utils.py", line 1958, in addAutoBridges
o.warnings.append('not curves')
AttributeError: 'str' object has no attribute 'append'

location: :-1

location: :-1

Could you please kindly explain the process to correctly use the bridge function (auto or manual)?

Many thanks.

What strategy should I use to implement the attachment piece pockets 1,2,3,4 and 5?

The "piastra 2" operation is perfect!
The "piastra 1" operation, however, I can not calculate it ...

pezzo.blend.zip