#92 it said to send you this

[Daryl Spitfire]

Same as before only I set stepdowns to .25, 0.2 and 0.1875 and tried for 3 passes (rough, semi, finish). It chugged for 15 minutes then bombed out. I spent several hours with no success. I'm just a hobbyist (also retired engineer with cnc experience) but this is looking like too half baked / unstable / passe. But I'll give up for now until I see some replies. It would bw nice if there were some reasonably complete documentation, especially for we who are new to PyCAM.

---

An unexpected exception occoured: please send the text below to the developers of PyCAM. Thanks a lot!
Traceback (most recent call last):
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Gui.Project", line 4041, in generate_toolpath
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Toolpath.Generator", line 62, in generate_toolpath_from_settings
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Toolpath.Generator", line 372, in generate_toolpath
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.PathGenerators.ContourFollow", line 258, in GenerateToolPath
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.PathGenerators.ContourFollow", line 276, in GenerateToolPathSlice
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.PathGenerators.ContourFollow", line 222, in _get_free_paths
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.PathGenerators", line 83, in get_free_paths_triangles
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Cutters.SphericalCutter", line 226, in intersect
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Cutters.SphericalCutter", line 196, in intersect_sphere_edge
File "pyinstaller\build\pyi.win32\pycam\outPYZ5.pyz/pycam.Cutters.SphericalCutter", line 190, in intersect_sphere_line
AttributeError: 'NoneType' object has no attribute 'sub'

[Lars]

I am sorry for your bad experience.
Indeed there was quite a good amount of documentation for the program usage including nice charts in a mediawiki on sourceforge. But somehow it disappeared - what a pity.

Since pycam is not maintained anymore (as far as I know), you should probably look for an alternative.

[Daryl Spitfire]

Lars, thanks for your reply. I wish there had been a notice of some sort
on the website, wiki or sourceforge saying PyCAM was no longer
maintained. I did eventually find some tutorials. Or, perhaps there was
more and I didn't see it. Too bad because from my playing with PyCAM for
an afternoon it looked like a very good start as a CAM tool. While there
are numerous commercial CAM applications (for a high price) there are no
3D CAM software tools that I know of that are in my price range as a
non-commercial hobbyist (my range is close to zero). I do use a few 2D
and 2.5D open source programs but none looked as promising as PyCAM.

Can you recommend any [free or low cost] software with any 3D toolpath
generation capabilities ?

Thanks,
Daryl

On 01/19/2016 06:34 PM, Lars wrote:

I am sorry for your bad experience.
Indeed there was quite a good amount of documentation for the program
usage including nice charts in a mediawiki on sourceforge. But somehow
it disappeared - what a pity.

Since pycam is not maintained anymore (as far as I know), you should
probably look for an alternative.

---

[bugs:#92] http://sourceforge.net/p/pycam/bugs/92/ it said to send
you this

Status: open
Group: git_-_master
Labels: error
Created: Tue Jan 19, 2016 05:43 PM UTC by Daryl Spitfire
Last Updated: Tue Jan 19, 2016 05:43 PM UTC
Owner: nobody

Same as before only I set stepdowns to .25, 0.2 and 0.1875 and tried
for 3 passes (rough, semi, finish). It chugged for 15 minutes then
bombed out. I spent several hours with no success. I'm just a hobbyist
(also retired engineer with cnc experience) but this is looking like too

[Lars]

No, sadly I cannot recommend any other toolpath generating software. It is a true pity.

[Jvin248]

I'm pushing ahead with pycam. I've had more success with version 0.5.1 than starting with 0.6 SVN that is in CAELinux package (I need to find where the collision model is identified problem is in 0.6).

For 0.5.1 version I made some notes the other day for what I found successful (pypy is faster than standard python interpreter). Which is based on a 'fast-pycam-on-mac-using-homebrew' from pepijndevos.nl blog.