Hey, found this topic and figured it was best to hijack it rather than start a whole new thread.
I was using the PlasmaCNC last week (Wed and Thu) because I hadn’t seen this thread, and it worked fine after tightening some of the connections on the limit switches.
Yesterday I came in and tried to use it again, but ran into a problem. I set it all up, and did a dry run without the torch on and it all worked fine. But when I turned the torch on, the torch has fault 0-51. (See photo). The manual indicates this happens when the trigger on the torch is pulled when the machine is powered on, solution is to release the trigger and power cycle the Hypertherm.
I did some tracking down and debugging since the Torch-On signal is coming from the plasma CNC. It seems that the LinuxCNC PC has no effect, the Hypertherm has a fault on power on whether the PC is on or off, and also whether the LinuxCNC software is loaded or unloaded.
The Hypertherm will power on with no fault IF the PlasmaCNC table is powered off. So there is some signal for Torch-On. I tracked the cable for controlling the Hypertherm backwards through the THC, onto the PlasmaCNC table and down to this relay module.
The red and black wires on the right are ARC-START and ARC-STOP,
the red and black on the left are 5V, GND, and the white is PIN14 from the plasmaCNC table. There is a little light up on the top left that I believe is indicating the relay state, and the relay does not seem to switch at all during the dry run of a part.
I haven’t had time to dig further and look up documentation for the relay module or the controller, but it would seem that either there is a bad signal coming from the controller, or the relay is stuck.
I’m going to power off the LinuxCNC PC, blow it off, blow off the boards on the back of the table, and see if that helps, but for now the table seems completely down.