Everyone -
I'm very interested in managing an opensource THC project. I've already hacked my Harbor Freight
plasma cutter to enable trigger control. I've also designed a
holder for that torch that I can add to the project. As you can see, I've taken a low-cost approach to enter this market - and it's working pretty well so far.
Regarding Jim Colt's list of criteria - it looks as though that's a decent criteria list for the
ultimate THC. As a DIY guy (my real job is in a sterile office :-), I'd only be interested in addressing a subset of those criteria for a DIY system. But, if that roadmap can be designed to extend to the ultimate criteria list, there is little risk in covering the basics.
What are the basics for an entry-level, DIY THC? In my opinion:
2. Ability to quickly retract to proper pierce height before firing the torch.
4. Ability to be switched to arc voltage feedback control after x and y motion accelerates to proper speed.
(optional) 7. Ability to auto compensate for electrode wear (arc voltage increase) over the life of a set of consumables)
As a novice user, I'm mostly interested in getting better cuts out of my system. I'll stare at it for the whole cut if I need to. I'm not doing production, just prototypes. So, raw flame quality and location are the dominant drivers of the fundamental criteria. Automation and a refined flame quality are less critical.
I believe an integrated THC is the proper path to take for this project roadmap. It allows for more software-control flexibility to accomplish more of the future criteria.
I'm sure that THC vendors will not be particularly interested in an opensource THC project. But, there is a market for DIY and low-end shops that can't justify the cost of a QA'ed system with a warranty. Selling components into that project is still a market. And, with more engineers participating and exploring possibilities, the R&D could be better optimized over time.
So, do you think it is possible to start a project to develop an opensource THC hw/sw system that is integrated into MACH3 or with a generic API?
--Joe