I’ve been using sheetcam for a few years now, recently upgraded to 4.0.4.
Tried to generate a cutpath yesterday for a couple parts I wanted, using a plasma torch. Sheetcam generated the entire cutpath fine, except for one circle. There, the only thing it will generate is the 1/4" leadin.
I’ve tried moving the start point, changing the tool, changing the offset, just trying to get it to generate the code in any manner. It will never generate more than the 1/4" cut.
DXF attached. Plasma torch isn’t accurate enough to cut the smaller holes, so the tick marks in the center of each are just to put a centerpoint for a drill guide. The large hole is the one sheetcam chokes on. The tick mark in the center of that is because the first drill guide it cuts on any particular part is blasted apart, so you have to put a waste one somewhere.
Are you using an older post converted from SheetCam standard? If so, give me a copy of the post and I’ll modify it to work with TNG.
By the way for punch marking, look at the drilling operation. Set the min hole size to be less than the size of the circles to be punched and the max hole size to be greater than the circle size. Any circles between these two sizes will have their centers marked. Note that they still have to be on a different layer to your main cuts.
Thank you for your time and effort in resolving this issue, I appreciate the excellent customer service.
Unfortunately, Mach3 does not understand the g-code generated by the new post file you made. (First error- line 11, G23 is unrecognized.) I just realized I did not mention that I was using Mach3 earlier and apologize for the lapse.
I’m thoroughly confused by this issue, as I’ve used the new version of sheetcam several times and haven’t had any trouble. Is there something about the location and size of this circle that’s throwing it off? Even if it’s the only shape in the cut file, it refuses to generate code for it.
In SheetCam go to Options->machine->post processor. Make dsure it is showing that your post is selected. it should be named something like MP1000-THC-piercecount(edited)
Tried another job with the new post processor. I have a code snippet in that job, and when I checked the tap file, the code snippet was the only thing there. Only thing the debug log says is
I deleted the post processor and reimported, and it worked the second time.
While doing so, I did notice that at import, it pretends it’s loading the one you just imported for a brief moment, before jumping to whichever one is at the top of the list. In the dropdown where you choose. This would explain my confusion yesterday about accidentally using the wrong processor. Dunno if that’s something that could be easily fixed in a future version, automatically selecting the one you just imported.
Thanks for your time, sorry for wasting some of it with my errors.