QTPlasmaC with fourth axis - rotary

Thanks for that, I have got a bit done on it today. I could possibly push a preliminary test branch tomorrow sometime.

Torch On, Arc OK, and Pierce Delay are still controlled by plasmac.
THC is disabled.
Height Override is still available during the cut.

I also made some changes to the G-code parser so it was happy with not using the material parameters for the feed rate. The only material parameter used is Pierce Delay.

Changes to the G-code were:
add the magic comment #<keep-z-motion>=1
change all M03 to M03 $3 S1
change all M05 to M05 $3
remove all G04 P0.5

A couple of things I am unsure about:
This G-code has no probing so I haven't done anything with probing yet.
The G92 offsets on the Z and A axes grow a bit on each run, Z eventually fails due to the increased height. I have never really used G92 offsets so I am not sure of the purpose for it here or whether it should be reset at the end/beginning of each run.

It currently uses the following spindles:
0 = Torch - normal cut
1 = Scribe
2 = Torch - spotting

I am intending to use 3 for Torch - tube cut

As SheetCam is controlling all of the other cutting parameters I think it would make sense for it to control the pierce delay as well.

I wasn't sure which way to go here, by getting plasmac to do it then it is able to ensure the arc is valid before proceeding rather than just relying on a G-code delay. This also allows multiple arc start attempts depending on the arc fail parameters.
 

The different spindles are so the plasmac component knows what type of job to perform. So for a tube cut the component won't do any probing nor move to pierce height, puddle jump height or pierce cut height.

Using a scribe requires a M6 tool change and a G43 as well as the spindle number difference.
linuxcnc.org/docs/devel/html/plasma/qtpl...c.html#plasma:scribe


 

As SheetCam is controlling all of the other cutting parameters I think it would make sense for it to control the pierce delay as well.

This is not correct.

SheetCAM is capable of providing the material parameters via "magic comments" and a temporary material number is assignment, but ultimately QtPlasmaC handles and uses these values internally.

Among probably many things, this allows the user to have a SheetCAM controlled material set, or a QtPlasmaC controlled material set. Some people use the former, some people (me) use the latter.

To be clear the difference is:
SheetCAM controlled - Material parameters are fed to QtPlasmaC via magic comment and get a temporary material number. Changes to material parameter settings are done in SheetCAM and re-post processed.

QtPlasmaC controlled - Material number is selected in SheetCAM and provided to QtPlasmaC. Material parameters are stored in QtPlasmac, and therefore changes to these settings are instantly applied and saved for future cuts (dont need to remember to update these settings in SheetCAM).