Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No ocl functions in heekscad #23

Open
muetze opened this issue Oct 21, 2012 · 9 comments
Open

No ocl functions in heekscad #23

muetze opened this issue Oct 21, 2012 · 9 comments

Comments

@muetze
Copy link

muetze commented Oct 21, 2012

Zigzag and waterline icons don't show up in heekscad.

Opencamlib is installed on the system. Versions are all from github: heeks/heekscad heeks/heekscnc heeks/libarea aewallin/opencamlib. Heekscad heekscnc libarea and opencamlib compile fine.
All other cnc-functions in heekscad are present and do work.

Systems are debian stable/testing-i386 and debian stable-amd64.
Python version: 2.6.6.

@sliptonic
Copy link
Contributor

zigzag and waterline (and a lot of other stuff) were removed during the cleanup effort. The idea was to get back to a stable core and then gradually add back the operations and features that are used but do it in a methodical way.

There's a branch called extraops that is the beginning of an effort to restore zigzag and waterline. It doesn't work yet but it's close. It just needs a better programmer than me.

@42loop
Copy link

42loop commented Aug 14, 2013

is there any alternative function to perform adaptive roughing or zigzag operations ?
how can i mill a surface without ocl or actp functions ?

@sliptonic
Copy link
Contributor

You can't do adaptive roughing but you can still machine a surface. You use the attach operation in conjunction with a pocket.
Step 1) import your solid and create a rectangular sketch around it to serve as a machining boundary.
step 2) Select the solid and add an 'attach operation'
step 3) Select the sketch and add a pocket operation
step 4) add an unattach operation.

When you post process, the solid will be used to determine the bottom of the pocket. The pocket op properties still control the stepover and stepdown as well as feed rate, etc.

@42loop
Copy link

42loop commented Aug 14, 2013

thanks for your quick answer, but this doesnt work for me.
as soon as i add the attach op and post process, there is an error:

Traceback (most recent call last):
File "/tmp/post.py", line 66, in
area_funcs.pocket(a, tool_diameter/2, 0.2, rapid_safety_space, start_depth, final_depth, 1, step_down, clearance, 1, False, False, 0,False, None,'conventional')
File "/usr/lib/heekscnc/area_funcs.py", line 436, in pocket
cut_curvelist1(curve_list, rapid_safety_space, current_start_depth, depth, clearance_height, keep_tool_down_if_poss)
File "/usr/lib/heekscnc/area_funcs.py", line 95, in cut_curvelist1
rapid(z = clearance_height)
File "/usr/lib/heekscnc/nc/nc.py", line 534, in rapid
creator.rapid(x, y, z, a, b, c, u, v, w, machine_coordinates)
TypeError: rapid() takes at most 8 arguments (11 given)

@sliptonic
Copy link
Contributor

I just added support in the post processor for UVW axis moves last week. Obviously something wrong there. You can try a different post processor or pull the prior commit and rebuild. I'll take a look at this as soon as I can.

@sliptonic
Copy link
Contributor

patch to recreator.py just pushed to master branch should fix this now.

@42loop
Copy link

42loop commented Aug 19, 2013

thanks for the fix, at least it works 'somehow' in the latest version now.
however the pocket op properties do not control the stepdown of the modified pocket op.
i have attached a sccreenshot, on the left there is the solid with pocket, on the right there is a pocket only, parameters for both are the same
screenshot from 2013-08-19 12 05 07

@sliptonic
Copy link
Contributor

It looks like it's working correctly. Since I can't see the pocket operation parameters, I'm just guess but I think you just need to adjust your start depth, final depth, and stepdown. Assuming the bottom of the cube is at z=0, Set your start depth to the height of the cube and your final depth to zero.

Based on the picture, it looks like it's trying to start at z-0 and step down.

@42loop
Copy link

42loop commented Aug 19, 2013

you are right, it works like this.
sorry, I am pretty new to all this, have to rethink since i'm coming from the 3d printers corner.
thanx a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants