Snuggly's Plasma Build

In an effort to save the newcomer, I'm starting this new thread so they can follow progress.

I have a 5x10 plasma table running linuxcnc 2.8. My controller is a Mesa 7i96 w/ dm542a stepper drivers powering Nema 23's. The THC is a Proma 150.

My current plasma cutter is a HF start Eastwood Versacut40; it will be among the first things to be upgraded. Because the machine is HF start, I've gone to great effort to ground the machine including running a ground wire to my shop's earth.

Now that the controller is setup and the machine files are largely complete, it's time to integrate the THC. The Toma files from Proma were developed for Parallel Port and were too difficult to modify for the Ethernet board. Grotius had/had been developing a plasma/laser branch that looks promising; however at this stage the development is too new for a machine to reliably run for a noob as myself. For posterity, here is the link is to the Grotius development thread: forum.linuxcnc.org/plasma-laser/34916-us...lasma-thread?start=0

For the reasons above, I will be trying to use THCUD (THC specific to Mesa) : linuxcnc.org/docs/html/man/man9/thcud.9.html

I've had difficulty in the past implementing THCUD, I hope that this thread will hope those struggling with the software end of the plasma cutter build!

Ok, good start.

Do you have your basic X,Y,Z motion working with all desired homing and limits? Are you running 2.8 pre because you have a dual drive gantry machine? Do you have your probing for material surface working ( G code subroutine or inline code)? What input pins do you have your Arc Ok, Down and Up signals connected to? Does your Arc Ok signal work correctly when you manually trigger the torch? Have tried to use Halscope to monitor your input pins yet? To sound like a broken record .ini and .hal files are a big help when trying to solve configuration problems.

John

I am able to jog the machine but I have some errors on my limit switches that pop up. I have the switches setup as normally closed so I'll have to find a way to make sure that the software shows a low level trigger

I am using 2.8 because I have a dual drive gantry.

I do have a float switch, however I've not been able to verify that it works.

Pinouts for the THC are:
Input #7 = float switch
Input #8 = arc ok
Input #9 = down
Input #10 = up

I'm not familiar with halscope yet, it's something I'm working on figuring out. I'll post my THCUD build here soon when I'm done with it.

Just a bit of wiring practice and question about specific components. Obviously question marks will show what I don't quite understand how to wire up. I'm not running an encoder on my Z axis, so I think a few of these commands are superfluous for my application.

WILL MY PROMA WORK ON HF START?

THCUD connections found @: linuxcnc.org/docs/ja/html/man/man9/thcud.9.html

thcud.torch-up bit in = pin 10 (hm2_7i96.0.gpio.010.in)

thcud.torch-down bit in = pin 9

thcud.current-vel float in = Connect to motion.current-vel ????????????????

thcud.requested-vel float in = Connect to motion.requested-vel ??Float switch (pin 7)??

thcud.torch-on bit in= Connect to motion.spindle-on ?????????

thcud.arc-ok bit in = pin 8

thcud.enable bit in = Enable the THC, if not enabled Z position is passed through ?????????

thcud.z-pos-in float in = Z Motor Position Command in from axis.n.motor-pos-cmd ?????????

thcud.z-pos-out float out = Z Motor Position Command Out

thcud.z-fb-out float out = Z Position Feedback to Axis

thcud.cur-offset float out = The Current Offset

thcud.vel-status bit out = When the THC thinks we are at requested speed

thcud.removing-offset bit out = Pin for testing

snugglylovemuffin wrote: WILL MY PROMA WORK ON HF START?

Yes, it will.
If you have to open plasma to get the voltage for it ( in case your plasma does not have a connector with the voltage divider inside ), have a look at this before you attempt to wire it yourself.

Ok, I've never tried to use this hardware or configuration but this is where I would start. If you haven't figured out using Halscope at least use Halmeter to verify that all your connections work as desired. Read about the problems with motion.requested-vel as at some point in the future you may wish to change how the component works, this is not a problem when working out basic configuration and cutting.

John

[Just a bit of wiring practice and question about specific components. Obviously question marks will show what I don't quite understand how to wire up. I'm not running an encoder on my Z axis, so I think a few of these commands are superfluous for my application.

WILL MY PROMA WORK ON HF START? YES

THCUD connections found @: linuxcnc.org/docs/ja/html/man/man9/thcud.9.html YES

thcud.torch-up bit in = pin 10 (hm2_7i96.0.gpio.010.in) YES

thcud.torch-down bit in = pin 9 YES

thcud.current-vel float in = Connect to motion.current-vel ???????????????? YES

thcud.requested-vel float in = Connect to motion.requested-vel ?? YES

Float switch (pin 7)?? = motion.probe−input

thcud.torch-on bit in= Connect to motion.spindle-on ????????? Usually

thcud.arc-ok bit in = pin 8 YES

thcud.enable bit in = Enable the THC, if not enabled Z position is passed through ?????????YES

thcud.z-pos-in float in = Z Motor Position Command in from axis.n.motor-pos-cmd ?????????YES

thcud.z-pos-out float out = Z Motor Position Command Out pid.z.command

thcud.z-fb-out float out = Z Position Feedback to Axis YES

thcud.cur-offset float out = The Current Offset

thcud.vel-status bit out = When the THC thinks we are at requested speed

thcud.removing-offset bit out = Pin for testing
/quote]