WOW I missed a TON

My last update I did was a while ago and I come back to find somthing different with the plasmaC I run mothballed. It was hard enough for me to wrap my brain around getting it installed and running and that was years ago. Im
working my way through the documentation but are there any pitfalls I need to watch out for. Or is it best to write down all my numbers and just format the computer and start over?  

I agree with Tommy, but because you have all the motion parameters set, I don't bother with being exact with the axes settings and just cut and paste the known good data into the ini file (and some of the hal file stuff too)

I’m on 2.8 and generally happy with it. I’m considering updating to the newest flavor but until then is there a way for plasmaC to pull tool/material parameters from my Gcode. I have been putting off adding and editing my tool list as I have programs saved that still use the old tools I have saved in the machine. Is there a button I can click that will allow it to get the basic stuff that sheet can spits out? 

There is a script that exports the Sheetcam .tool file into plasmac format. Check the docs.
There is also a post now included in sheetcam by default that has a setting that uses the Sheetcam data and ignores the plasmac tools.
If the Linux version of SC does not have it, it's definitely in the Windows version and you can coy it across to Linux..

phillc54 wrote:

You could possibly use a temporary material from magic comments in the G-code.
 

This is how the Sheetcam post I mentioned does it.

phillc54 wrote:

Really?

Yeh, I sent some revisions back to Les via the Sheetcam forum... There are  couple of flags that change behaviour in the header.