swarfer / sketchucam Goto Github PK

Create a non-convex shape with a need for at least two distinct paths.

Pocket operation generates a paths for only a part of the face.

Original issue reported on code.google.com by [email protected] on 27 Feb 2014 at 4:43

Attachments:

• [Screen Shot 2014-02-26 at 8.42.03 PM.png](https://storage.googleapis.com/google-code-attachments/sketchucam/issue-1/comment-0/Screen Shot 2014-02-26 at 8.42.03 PM.png)

Hi all,
I only want to know if this project is still alive.
Thanks

sucam narrow slot issue.zip
If you create a slot via an outside cut that is wider than the cutting tool width by a very small amount suCAM will not generate GCode. In the example, I show a 3.175mm bit and 2 slots, one 3.2mm wide and another 3.225mm wide. The 3.225mm slot has GCode generated, the 3.2mm doesn't. So, a slot must be wider than the bit by somewhere between .025 and .050mm. The workaround is to either slightly widen the slot or separately use the centerline tool for end mill width slots. SUCAM shows the cut in the slot.

By the way, you don't need to actually generate GCode to see if the problem exists. If you use the SUCAM eraser tool, it leaves the cut outline in the slot that won't get GCode generated. It's a useful quick check to see if there is a problem.

I'm pretty sure this is a sketchup problem as it generally makes a mess of anything with small dimensions. I think SUCAM should recognize this situation and refuse to show the line in the slot that is too narrow.

all settings are still defualt as I just reloaded moments ago. To create the crash, draw a circle smaller than your tool. Try to use the outside cut tool. Sketchup (2017) will lock up immediately even upon hovering over the circle, force close is the only escape I have found

Small part. Using a 1/8"(3.175mm) end mill, I wanted to bore 2 4.1mm and 1 6.6mm holes. It appears to be correctly boring the 6.6mm hole but the two 4.1 holes are being doubled with the extra holes 1/2 diameter to the outside of the correct location. It appears that the finishing pass (if that's what it is supposed to be) is being mispositioned. At first I thought the GCode Plotter was misreporting but, nope. it generate 2 holes - see the photo of the part I cut.

SketchUcam V1.4d-80c0152
Included in the zip file: sku model, cnc code, photo and saved .tpi file.
Let me know if you need anything else.

hole boring problem.zip

Not necessarily a problem. I posted some of this on OpenBuilds but thought it might be better here.

Layers work but it would be really cool with one change. Currently it appears that all layers are used to generate GCode, even ones with "Visible" unchecked. This is a bit of a departure from Sketchup - you can't select things on non visible layers. If only visible layers were used to generate GCode, then we could use this to separate out pieces of a design for different treatment. I'm probably naive to think that it's as simple as a check to see if visible when generating code for a given object.

This could make for some interesting enhancements:

• attach different parameters to a give layer
• tool change. put all the cuts with given tool on a different layer

What steps will reproduce the problem?
1. Make something that has an X pattern that closes at the same distance as 
your bit diameter.
2. Only one side will make it to gcode as the other is left out. Almost like 
the gcode is written to go to the intersection and turn around back to finish 
the loop without ever crossing over to the other side.
3. Think of two triangles connected together at their point and at the 
intersection is the same size As the bit and will only cut out one triangle

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 13 May 2014 at 8:35

In the latest SKUC, a G53 G00 Z0.0 is output in the GCode preamble and postamble. I want to turn that off. I've hacked GCodeUtil and PhlatMill to remove G53 line generation. In a future release, it would be good to make that an option.

And, it would be good to have a way to configure more of the preamble/postamble code but I suspect that's not very likely to happen.

Thanks
Phil

Found this issue on non-convex shape, but there's a good chance it happens on 
convex shapes as well.

Original issue reported on code.google.com by [email protected] on 27 Feb 2014 at 4:48

Attachments:

• [Screen Shot 2014-02-26 at 8.47.25 PM.png](https://storage.googleapis.com/google-code-attachments/sketchucam/issue-2/comment-0/Screen Shot 2014-02-26 at 8.47.25 PM.png)

Hey, i've been using sketchucam for years now, theres some stuff that i always change by hand after i generate my gcode, one of the things i always do is run a first pass at Z0, since my machine is not perfect, i kind of have my pass depth at its limit, so i need to do it once at 0, otherwise i can have problems at points where it might be cutting too much material, my machine can vary up to 1mm in Z height if its in the middle in both X and Y, so i usually copy Pass 2, rename it to 1, and then rename pass 1 to 0 and put Z at 0, i copy pass 2 because i found sometimes copying pass 1 didnt work.

So, an option to do an extra pass at Z0 would be nice.

I would absolutely try to do it myself, but i have 0 knowledge of Ruby, anyways, appreciate it either way.

1. Create a pocket operation
2. Use erase tool to remove operation.
3. Erase tool removes a cut path but doesn't remove geometries added to a model.

Original issue reported on code.google.com by [email protected] on 27 Feb 2014 at 4:53

Attachments:

• [Screen Shot 2014-02-26 at 8.49.34 PM.png](https://storage.googleapis.com/google-code-attachments/sketchucam/issue-3/comment-0/Screen Shot 2014-02-26 at 8.49.34 PM.png)

I have a relatively simple rectangle (made up 8 segments that when I pocket it, the normal pocket path gets drawn and then a 4200+ mm path gets added well outside the rectangle and safe area.

In addition, if you generate gcode from this mutant pocket, it generates gcode outside the safe area.

I tried constructing a similar rectangle with 8 segments but it doesn't demonstrate the problem.

SketchUcam V1.4d-80c0152 (which I believe is the latest)

pocket bug.zip