sheetcam.com

The linux standard for end of line is line feed, while Windows uses carriage return + line feed. The tool table code should be able to handle both.

The Linux and Windows versions are functionally virtually identical so files created on the Windows version will work on Linux and vice-versa. I have one set of source code that can be either compiled for Windows or for Linux.

From what I can see of that post, the 'Mach3 THC with scriber' post that is shipped with SheetCam should work. After selecting the post click on the 'Edit post' button. Near the start of the file are a bunch of configuration values. The only one you should need to change is 'switchOffset'. Put some ...

Use the overcut function. A negative overcut will stop before the end of the cut. A positive overcut will cut past the end.

Yes, that html would really confuse the compiler and give the error message you are seeing. Try deleting everything before function OnAbout().

That means your copy of SheetCam is unlicensed. If you have a license try reinstalling it. If not you will have to purchase one.

Give this version a try. Save the attachment to your computer then run SheetCam and go to Options->machine->post processor. Click on the 'Import post' button. Using the box that appears navigate to the post and open it.

In Mach3 go to Config->general config. Is the I,J mode set to incremental? If it is set to absolute you can get this error.

Are you sure you are using Mach3 plasma? That post doesn't use either G28.1 or G31.

What post processor are you using? Most plasma posts can be configured to use either g28.1 or g31. Go to Options->machine->post processor and click on the 'edit post' button. At the start of the file you will probably see a number of configuration options, one of which will be which probing method t...

The only other thing I can think of is possibly an issue with cutting rules do you use rules?

That makes a lot of sense but it is quite difficult to implement. The problem is that chaining is calculated after rules have been applied. I will see if I can find a workaround.

I am in the process of rewriting chunks of the tool table editor and attempting to add an operation table editor. I'll make sure I test the changes on Linux to make sure they work there as well.

Have you changed your post processor? If you look at the old g-code it will probably show the name of the post processor used in the first few lines. Is this the same as the new code?

Those drawings have lots of curves. Curves have to be broken into short line segments. Your drawing ends up with thousands of short line segments. Duplicate line detection gets very slow for drawings with thousands of segments. The easiest solution is to disable duplicate line detection. Go to Optio...