Snuggly's Plasma Build

snugglylovemuffin wrote: Yeah the Toma system is supposed to work entirely off an M3 command, so I did edit the gcode tools window. I'll get back to it and report findings.

That is correct, if you leave the Z axis values, it will still work properly, but it will wait for the Z axis movement to finish. That means it will take longer to cut a plate of metal, mush longer when doing a lot of small parts.
Joint.3. on limit switch is just that, Z axis limit is active and set up incorrectly. On the right side of the Axis window, there is a LED with "float switch" written on it, test is by hand and it should switch on and off. If it does not, do not try to cut anything, it will not work properly.

I went into Halshow and I found out a problem. Pins 11 (com); 12 and 13 (relay) are oscillating on and off. Very strange, states should be static.

The float switch LED on the gui does come on when the switch is depressed.
#net TriggerLimit or2.2.out => joint.3.neg-lim-sw-in joint.3.pos-lim-sw-in joint.3.home-sw-in
^ commenting out works, no variation of removing pieces works.

Arcok, and torchon signals are not coming on and do not seem to interfere with the function of the float-switch as the above code seems to be the source of the error.

Ok, please be careful. This line appears to be an integral part of safety aspect of the THC.hal. I suspect that you have a logic polarity problem with one or more of the inputs as this is allegedly very tried and proven code.

John

www.youtube.com/channel/UCS0X88R7n7P2jIFwhIkw2Qw

Have a look, all the plasma machines use that config, there are more that i have no video for, and all of them work without any issues for several years.
The tube cutter uses the same config but without a THC, just for initial height sensing.

I was wrong, pins 13 + 14 are the problem (relay). My relay switches low which I completely spaced.

Doesn't seem to explain why pins 12,13,14 were acting strangely.

Pin 13 is input, pin 14 is output.