Closed GoogleCodeExporter closed 8 years ago
It's pretty finicky stuff. I spent a lot of time recently playing with libactp
and found that it's pretty sensitive to a lot of variables. Look at the python
script that HeeksCNC generates (post.py in this case) and notice
'actp.settoolcornerrad(0)' and 'actp.settoolflatrad(1.5)' I 'think' that
cornerrad is actually the radius across the flutes of the tool, not the shape
of a ball end mill or bull end mill. Reverse those two values first thing. I've
been meaning to get that reversed after I am sure about my hunch.
Another thing I figured out was that you can comment out a bunch of the setting
variables and still get a tool path that works. It makes you hang on to your
sanity a bit longer, if you can get something happening right away and refine
it later.
So try commenting out as many of the variables as you can and then go back,
uncomment them one at a time and see what it does.
If you comment out all the bounding box stuff, the tool will start in the lower
left hand corner of the part. Another thing that I found was that you can start
the tool -inside- the *stl file and get a tool path. Weird, but I think the
program just bounces the tool against stl triangles.
I am going to write something up on my blog soon (if my kids let me) with some
images.
Original comment by ddfalck2...@yahoo.com
on 5 Sep 2010 at 4:16
no feature requests here, just bug reports for HeeksCNC 1.0
Original comment by danhe...@gmail.com
on 24 Mar 2014 at 5:10
Original issue reported on code.google.com by
Chris.A....@gmail.com
on 4 Sep 2010 at 11:48Attachments: