RETROFIT Oxy Acetylene 3 HEAD CNC

RETROFIT Oxy Acetylene 3 HEAD CNC

HELLO

I want to retrofit Oxy Acetylene 3 HEAD CNC.

Wich has:

X-axis with 2 parallel moving motor.

y-1 axis
y-2 axis
y-3 axis

z-1 axis
z-2 axis
z-3 axis


Parts to use:


CONTROLLER:
MESA 6I24-16 FPGA based PCI Anything I/O card
eusurplus.com/index.php?route=product/pr..._62_70&product_id=78

MESA THCAD-300 High isolation A-D accessory
eusurplus.com/index.php?route=product/pr..._61_67&product_id=53


MOTORS:

To use step and direct motors like this or something similar.
www.omc-stepperonline.com/Integrated-Ste...op.html?search=servo


50 pin daughter cards
eusurplus.com/index.php?route=product/category&path=59_61_73


Basic machine operation.

At the moment most of the time we use one head only the other head is manually put it at the side or it stays where we want the motor is turned off.
Some times the second head is in parallel operation to duplicate parts.

3 head is unused.
We want to add to the 3 head a plasma cutter.


My question is?

Is it possible to config LinuxCNC into two operation modes? Cutting with Oxy-Acetylene Or with Plasma cutter like MODE1 MODE2?
And how to conf 8 motors in LinuxCNC?
And how should the machine operate 3 heads when I choose different operation modes.
And how the should be done the parallel cutting with 2 head Oxy-Acetylene?



Any ideas are great there is something similar done already, to point me to the right direction

Thanks for listening.

Thanks a lot, it is very helpful

I think what you are asking for is very possible, but far from "standard".

I've retrofitted some multi head routers to Linuxcnc that are configured similarly, but without the ability to adjust the distance between the routers.

For starters, use Linuxcnc version 2.8 or newer. The joint-axis clarification in those newer versions will make setting up this machine easier. (2.8 is technically still pre-release but for all intents and purposes it is ready for public consumption.)
X1, and X2 are easy, this is simply a standard gantry configuration. Follow examples given for gantry machines for these joints.

For the 3 Y-axis joints. You need to decide how you'd like to use them. If you want to use them only for making duplicate parts, with potentially using all 3 at the same time, I think I would slave them together as a single Y-axis, with a secondary axis letter or letters specifying the distance between each one. So a G1V500 command would move either one or all the Y-joints 500mm apart. Then a Y commands would move all of the Y-joints the same distance in parallel motion.

Finally for the Z axis. For my machines I normally have each parallel Z axis configured with their own axis letter, Z,W,U,V. That is fine if you only have 4, but what if you need more? This also ran afoul of the new trajectory planner if you need more than 1 line of look ahead such as for a 3-D wood carving machine. So I worked out a way to temporarily slave and unslave the joints of the U,V,W axis to the Z axis using custom M -codes. This let me easily control and set different offsets for each of these joints. It also removed the need to assign an axis letter to each of these parallel Z axis joints. I did this all with some complex hal trickery. The addition of external offsets to Linuxcnc kind of does some of the same things I was doing but with fewer hal complexities, I've played with using it instead in a simulation but have not implemented it or a Joint/Axis configuration on a machine yet.

The temporary joint slaving/unslaving idea could also be implemented for your 3rd Y joint if you want to treat it as an independent Y-axis. Where Y1 and Y2 are two slaves with V being the offset between them and Y3 is normally parked off to the side and unused. then when you switch Y1 and 2 are moved together, and parked to the side and Y3 and Z3 becomes the commanded Y and Z axis.

Working out the details of how soft-limits are handled might be the most difficult task. It might be simpler just to ignore them and only rely on hard limit switches, but what's the fun in that. Crash prediction is something you shouldn't have to give up.

I've posted my configuration files for this multiple times on the forum. both for a machine running servos with a Mesa 5i25/7i77 combo and a stepper config running off the parallel port. I'd suggest veiwing the parallel port example it is much simpler and my servo config has other quirks such as running a floating point base thread and nested PID loops for running torque mode servos.

I am not a programer, and writing C components is a little out of my league. This is cobbled together using "standard" Linuxcnc stuff from Linuxcnc v2.7. Because of the complexities of the Hal file it may not import well into Linuxcnc v.2.8. I can easily see the auto conversion script choking on it.

Here is the parallel port config so you don't have to hunt for it.