sheetcam.com

I can't see anything wrong. The moves between cuts are G0 rapid moves so Mach should move as quickly as it can.

This is a post processor problem. Tom knows about this and should be able to send you a replacement with the bug fixed.

motoguy wrote: I understand that multiple rule codes in the same ruleset can cause issues

You shouldn't have any issues with overlapping rules. If you have overlapping rules the one with the lowest feed rate wins.

Could you post the g-code and the job file (file->save job). I'll then run some tests and see if I can find what is going on.

The sequence is: OnRapid() Move to X,Y coordinates of cut OnRapid() Move down to pierce height OnPenDown() Reference, Turn torch on etc OnMove() Move down to cut height at plunge rate OnMove/OnArc... cut shape. OnPenDown occurs every time the torch moves down at the start of a cut. For a very minima...

SheetCam can't really do this. The motion is pretty simple so it would be easy to hand code.

Sorry, I missed this post. I can replicate the fault here so I will try to fix it for the next release.

1) I am using the toolset file from CandCNC. All of the tools seem to wok fine (at least the ones that I have tried), but whenever I go to the top of the screen Tools -> Tool Table, it crashes SheetCAM and closes. I have had a couple of reports of this issue in the Linux version. I will run some mo...

Have you set the correct switch offset in your post processor? If you have THC is it working correctly? Try disabling THC and see if the fault still occurs.

SheetCam does not know anything about the code in your code snippet. As far as it is concerned a code snippet is just text to be inserted into the g-code. If you want to turn off the spindle you will have to do that in your code snippet.

The report generator isn't currently set up for that information. I could look into adding it.

Having a slot that is exactly the same width of the cutter plus finish allowance can confuse SheetCam. You are right on the very edge of either cutting that slot or not cutting it. Floating point numbers are not perfectly accurate. For instance 5mm may actually be stored as 4.99999999999mm. Numbers ...

Yes, in the latest release the pierce time is everything including referencing and pierce delay. Do you really need a different pierce time for each tool?

This sounds like a different problem. Could you describe exactly what happens.

This is now fixed for the next development release.