Another plasma component...

Thanks, I'm really interested in how it goes.

It would also be best for the tool you are using for piercing only to have the Cut Height set the same as the Pierce Height.

If it works out ok you could probably use end of life consumables for the piercing only then change to newer consumables for cutting only.

I have pushed an update:

GCODE parser:
fix orphan G0 bug
fix M190 with comments bug
better error handling for materials
add 0 as defaults for non essential material variables (kerf width, THC, puddle jump, cut amps, cut volts)
add experimental pierce-only option (undocumented)

phillc54 wrote: If it works out ok you could probably use end of life consumables for the piercing only then change to newer consumables for cutting only.

That is a REALLY good idea, I have a bucket I keep my used consumables in and I have a fair amount that would be suitable for piercing only.

Stefan

The code you posted here doesn't look quite right to me.

There are a 294 F#<_hal[plasmac.cut-feed-rate]> codes when you only need 1 for the job.

There are a 289 M67 E3 Q60 (reduce feed rate) codes appearing before G0 codes and then having an effect on following G1 codes.

There are only 128 M67 E3 Q60 codes, I would think that there should be the same number of 60's and 100's.

There are 200 M62 P2 (DTHC OFF) (On small circles) codes. These probably should be where the M67 E3 Q60 (reduce feed rate) codes are used as the speed rduction will inhibit THC as well. (providing the VAD Threshold is above 60%)

There are 94 M63 P2 (DTHC ON) (On lead in) codes and 94 M62 P2 (DTHC OFF) (Before end) 94 codes which seems to make sense.

Phill,

I dont really understand G-code, I use Sheetcam for all of my G-code generation,

I have been using Rod's post processor and code snippets for my g-code,

Hopefully we can get PlasmaC to a stage where Les from sheetcam can write us a new post processor.

I still have not gotten around to testing the pierce only function , I will test it out on a piece of scrap tomorrow if I get time.

I don't have all of the answers but I think the multispindle features would support most of this.
If plasmac always recognised spindle.0 as being the plasma cutter, a user might define spindle.1 to be an engraver and perhaps spindle.2 as a drill and so on.

Then you just need to select the tool with the toolchanger commands to set the offsets correctly.

So the pin spindle1.on would turn on the engraver and spindle2.on the drill etc.

EDIT: then plasmac does not really need to support any extra features, it would be up to the user.