Another plasma component...

rodw wrote:
So in summary, I would like to use auto or always on THC settings and be able to disable THC when I want to override the system

Would a halpin that does the equivalent of the THC Off button in the about to be released version do the job for you?

islander261 wrote:
Please make the skip IHS type so it works correctly with the selected THC function, I do it externally now with my hacked version of your branch

So:
when in THC enabled mode IHS skip if within distance of last cut
when in THC disabled mode IHS skip if distance within last successful probe

islander261 wrote:
Your method does potentially make the tool table grow large, maybe even doubling the number of entries if you need a THC enable/disable set of cut parameters for each material and cut current

Yes I do realise this, I got that idea from your sheetcam tool file. I hope it is not too much of a problem.
BTW tool 41 in the file you posted has a huge pierce height, I randomly (thankfully) used that tool and that was what showed up the deficiencies in remapping.

Dee436 wrote:
I then tried the auto volts but this had the torch pogoing up and down again, I am wondering if it read a higher voltage at pierce and tried to use that for the cut voltage
rodw wrote:
I suspect you have your THC on delay set to too short a time period

Oops, I forgot to put one of them in...



Guys,
Before I finish cleaning up this tool handling and push the changes Rod suggested that we revert back to calling it a material file rather than tool table.
I tend to agree as it should cause less confusion with the LinuxCNC tool table. I think I will rename it [EMC]MACHINE_material.cfg to distinguish it from the earlier version.

Cheers, Phill.

Sorry guys, been busy lately.
It is amazing what can be done with Linuxcnc and how there can always be more than one way to do something in it or with it. That being said, I do not agree with the idea of "let's cram everything in one place" as that makes it impossible to maintain and troubleshoot and ultimately drives users away from using it, especially newcomers. There are already several things that can be done/controlled/invoked in several ways in this config and most of them i can not find any reason for as they do not serve as a redundancy, but separate functions for the same result. Also there is no tool table on earth that can have all the combinations of "material_type/material_thickness/plasma_cutter(amperage)/nozzle_and_electrode/air_dryer/air_moisture/mains_voltage_fluctuations/ambient_temperature".
Also a decision should have been made regarding CAM, not chasing back and forth the CAM and post processor issues. <<< whoever thinks this is not OK, please read the entire thread before posting about this.

This is magnificent work done by Phill and other members of this forum and i would hate to see it come to that.
As a reminder, see "blender style GUI by BrendaEM"

Moving on:
As Rod mentioned, this needs to be cleaned and packaged and be ready for users with as little options/editing as possible, as simple as possible to use and it should just work. The How to should be clear and concise (that leaves me out ).
Preferably a much earlier version of it, with less options, and this version should be the left as ultimate Plasma config, with everything included, so two separate threads.

rodw wrote:
Just a question. Will the GUI update itself to reflect the selection that is made from gcode?

Yes it does.

tommylight wrote:
Also a decision should have been made regarding CAM, not chasing back and forth the CAM and post processor issues. <<< whoever thinks this is not OK, please read the entire thread before posting about this.

Using the material file or using a 'tool change' (I guess this should be called a material change) is not a requirement, if none is specified then all the cut parameters may be set from the run tab.
The only requirement in gcode is F#<_hal[plasmac.cut-feed-rate]> to set the feed rate and M3S1 to start the ball rolling.
I am not interested in any particular CAM, I have used FreeCad on my mill and I used the Inkscape/GcodeTools way to test out my X/Y axis. I am happy to try to write converters to allow creating a plasmac material file from other tool files as I have done for SheetCam which are the only ones I have seen and which I doubt I will use myself.

Yes, writing a proper How To is going to be a bunch of fun

Cheers, Phill.