Advanced Search

I have some suggestions, you wont like them:
-Reservoir is utterly useless, unless you intend on using the machine about once every month or two, simple physics water evaporates and does so much more when it has a nozzle spewing 10000 degrees heat into it all day long. During summer here (35-40C) and heavy use, i have to refill every 2 or 3 days, meaning 2-4cm of water level is gone in that time. In general bigger table = less water level drop daily.
Having a water tap directly into it would be much more useful.
-You can cut underwater, easily, do not go above about 1-2cm deep with the torch, and that absolutely requires drying the torch whenever you do not use it as it will rust, quickly and badly. Everyday use should be fine.
-Roughly 15 cm deep would be nice (a lot less spill/spray over, 10 is very usable (mime are usually 10-12cm deep), and i would not go lower than 5cm on slats for up to 100A, 10cm for 200A and above.
-as for reservoir issues, see first paragraph.
Also, I might be utterly wrong here, but, stop watching youtube experts that built a single machine and now dispense advice like they are the "be all-end all".

I have a 20'x6'(6m x 1.8m) plasma that I'd like to convert to a water table. I plan on having a reservoir underneath that gets filled/drained with air pressure.
I have seen some water tables that have the water at the bottom of the sheet, but I've yet to see one that cuts underwater. How deep underwater does the plate need to be?
I guess I'm trying to figure out how deep the pan should be and how tall the slats should be.
The way the table is, it'd be fairly easy to make a 4"-6"(10-15cm) deep pan. It wouldn't be too hard to go deeper, but we're already at 100's of gallons and thousands of pounds at that depth.

My main reason for a water table is smoke control, but minimizing warping on sheet metal would be a plus.
I'm not certain I want underwater cutting, but I like the idea of it.

Some other questions.

How to keep sediment out of the reservoir? I thinking of having the last few inches of the pan go directly to the reservoir, with a sort of lip and screen. The upside of this would be easier fabrication, but that would also make the reservoir/pan one piece. Alternatively, I could use pipes, but I still don't know how I'd deal with sediment and I'm sure that would really increase the drain/fill time.

The building the plasma is in is unheated so I need a heater to keep the reservoir from freezing. I think a screw in or tri clamp element like you'd see in a residential water heater would be the best choice. How would I go about controlling the temp? I don't wanna reinvent the wheel if there are already off the shelf solution if anyone has a suggestion.

Any insights are appreciated.
 

I understand this currently comes with 8 digital inputs and 8 digital outputs, besides the analog I/O. If I later wanted to add additional inputs, would it be just a simple matter of stacking on additional input cards and updating my linuxcnc config, or would additional changes be needed?

Snowgoer- I get what your saying. I've heard enough "Can't you just...?" of my own. I know you can't please everyone, but I'm grateful for all your and everyone else's contributions.

I guess I'll see what I can do with axis. I do appreciate the plasmac statistics.
As a fabricator, most of my quoting involves chicken blood, planetary alignments and bs. I'll let you decide how much of each.

Does anyone quote by inches and pierces?

Sorry for double posting, but i forgot this trying not to forget to upload pictures, namely:
PlasmaC and QtPlasmaC have very detailed time logs, so if you have more than one of the same design to cut, cut one after resetting the timers and check how long it took after the cut, then you know exactly how long the rest of them will take.
This is magnificent for more than one off cuts.

Axis GUI, included with LinuxCNC has such a feature in "File>G code properties" menu:


It is fairly useful when you know what it actually shows, like the actual feed time, nothing else, so no G0 moves, no probing, no compensation for feed rate changes, etc.
Takes a bit of time to get used to it, so for simple stuff with not much pierces i just double that time, for more complicated stuff like 286 cuts on a plate i just wing it to 4 or more times the shown time. Works fine for rough estimates.

I've given this some consideration in the past. At first thought, I think most of the data is there, but I don't think any of it is neatly sorted out. There is just so much that goes into affecting an accurate estimation of run time that the effort goes very quickly from "that would be easy" to "holy crap, this is impossible". You have so much to consider. You have the main cut moves - lengths, velocity, velocity reductions, accelerations (and acceleration with regard to allowed deviation from paths), dwell times, delays, probe time, number of probes, etc. I am sure there is a "close enough" approximation. But I've also done this long enough to know that "close enough" will only satisfy some people, and others will be upset when it's off by several seconds, let alone several minutes.

Maybe I will think on it some more, but no real promises.

I've only seen this in real life on one plasma system (not LinuxCNC related) - we have a table at work that the software gives an estimation. It's so wildly inaccurate it's laughable.

You can reverse the direction a motor goes, three ways: Swap one of the coil's wires between the driver and stepper, swap the DIR pins (or switch between DIR+/DIR- if you're not using both) between the mesa card and the driver, or change the software.
You do not need to do more than one of these.
I

Yes, thread order issues might not be noticed except that with
the step in position on the first index, a 1 servo thread delay
in position causes a huge spike.

It is arguable that this position step should not be present in the basic
motion hal pins, but is needed for compatibility with encoder counter
hardware that clears the count on index.

You guys are great, thanks. I will try your suggestions and will then put together all the files you asked for etc.
Thanks very much.

Is there an easy way to estimate a programs run time? I tried searching and couldn't find anything.
I know there is a stickied post on creating a sim, but that doesn't seem useful for quoting.

Thank you!

The comments and overall formatting you did I greatly appreciate, makes it much easier to follow for someone like me and I think I'm starting to get an idea of how most of it works, well atleast to some extent.

For now the spindle drive is always in position mode, it's just a servo drive/motor. It seems to work okay, but then again it's a bit early to tell.

I will test things on the actual machine in the upcoming days as it's a bit of a drive, but I have high hopes this time

I’m trying to tune my servos but I’m getting around 0.02mm ferror instantly regardless the speed which then quickly drops to a couple microns steady. Can you recommend a way to fix it or is it ok as is?

Oha SEW?
Wenn für dich die 512inc Encoder kein Problem sind und die Analog Ansteuern möchtest.
Kann ich dir meine Anbieten.
MDX61b mit Profibus Karte (dfb21b) komplett mit Kabeln und Motoren.
Könnten auch auf ethercat Hochgerüstet werden