Another plasma component...

Tom
I think the reason arc start attempts doesn't work is that I don't have a delay between attempts and the peripherals only see a continuous torch on signal.
I could only guess at what time between attempts is required...
Could you let me know which of the following would be best:
1. Set a specific time in the component.
2. Use the time the user has set in the config tab for arc failure timeout.
3. Add a pin for this and another spinbox in the config tab.

Cheers, Phill.

I have just added a dry run facility.
This runs through the gcode without a torch on signal and THC is disabled.

phillc54 wrote: Could you let me know which of the following would be best:
1. Set a specific time in the component.
2. Use the time the user has set in the config tab for arc failure timeout.
3. Add a pin for this and another spinbox in the config tab.
Cheers, Phill.

Preferably number 2.
I own a Thermal Dynamics PAK90 with HV start and it takes 4 to 8 seconds from the torch on signal till arcok signal, so if i set it to 15 seconds i would save a lot of time. Also have an ISKRA 50 with HV that takes 8 to 13 seconds for the same thing. But an older Hypertherm MAX 40 with HV/HF start takes over 20 to 30 seconds for the same operation.
It is perfect as is, so i will test this week on actual hardware and report the results.
Thank you.

The only one that could really use a database of cut feeds and currents and nozzles and gases.... it's sold.

An sich that is not so difficult.
I prefer to use excel based cutting chart's. Python is good in loading and saving this data. It's much better then
text file data storing. This one i use for that purpose : python-xlsxwriter.
It also capable of storing much more data, like user interface data. In fact Mach3 uses one big excel file to store all data.

Grotius wrote:

The only one that could really use a database of cut feeds and currents and nozzles and gases.... it's sold.

An sich that is not so difficult.
I prefer to use excel based cutting chart's. Python is good in loading and saving this data. It's much better then
text file data storing. This one i use for that purpose : python-xlsxwriter.
It also capable of storing much more data, like user interface data. In fact Mach3 uses one big excel file to store all data.

Excel is a flat file database. It cannot represent the real world relationships that exist in this data model. Plasma is becoming more complex. Even the small Hypertherm 45XP now does marking, as well as cutting. Marking on this machine has many combinations, 2 gases, and three marking methods. I do remember being shown marking on a High Definitiion plasma cutter that supported 5 gasses. It took the operator longer to find the correct settings in the flat file database on the controller than it did to mark the part!

We can do better then that. With a relational database, the lists become dynamic so when you select material, marking and the gas, you'll just see the possible options in the cut file and various gas solenoids could be triggered to send the right gas to the machine. This list of options varies with the material being marked. Anyway, I've added some imperial cutting settings and I will persevere with what I'm doing but probably won't discuss further on this thread unless Phil wants to incorporate into his config.

Rod,

You are so far in your mind.... I will explore database for you. Will set up some stuff...
You Australian basterd... Excel tool chart's are to simple... Swifcut would be happy with this. But we think it could be better.

But database with a next to select option is really what go's to high end level in plasma world.
But i am in.

Don't think anyone uses argon for marking on a XP45. First connect the RS485.
After that we talk about a gas valve switch, what will problably not happen on a xp45.

Thermal Dynamic's has a new inverter. It can do marking on 10 amps and cutting on 60 amps.
Hypertherm only has this option on 45 amp's. I can get the Thermal Dynamics inverters for very low introducion price.