In our shop we have a Plasma cutter fitted with a MASSO G3-2042 controller, v2 core, v3.48 software. We're trying to install a Proma THC 150, and while the tests suggest it's properly wired, at the moment of cutting it doesn't work as intended.
Upon turnig the controller on, and putting the THC on test mode, things seem fine as the simulated voltage variation traslates to the adecuate up and down movements of the torch. However, after loading any code, something breaks down and this test mode no longer works: it seems to work on the THC, but on the DRO, in the box that notifies the torch status (up, down, in-postion) stays "in-position", only very brifly showing that it receved an up or down instruction, that at much moves the torch by 0.0001 mm. And when executing a code, the status box shows up and down instructions for several seconds, but the Z value is unnafected, and the torch doesn't move in this direction.
We assume the THC is properly wired, since we have checked it several times and it conforms to both the MASSSO documentation and the THC manual, plus how it manages to test correctly before loading a G code. But we're at a loss about what's preventing it to perform as it whould when running a program. In the meantime we're wasting time leveling the sheets we have to cut, so feedback would be very much appreciated.
Here's the code we're using to test the THC with a simple cut:
Upon turnig the controller on, and putting the THC on test mode, things seem fine as the simulated voltage variation traslates to the adecuate up and down movements of the torch. However, after loading any code, something breaks down and this test mode no longer works: it seems to work on the THC, but on the DRO, in the box that notifies the torch status (up, down, in-postion) stays "in-position", only very brifly showing that it receved an up or down instruction, that at much moves the torch by 0.0001 mm. And when executing a code, the status box shows up and down instructions for several seconds, but the Z value is unnafected, and the torch doesn't move in this direction.
We assume the THC is properly wired, since we have checked it several times and it conforms to both the MASSSO documentation and the THC manual, plus how it manages to test correctly before loading a G code. But we're at a loss about what's preventing it to perform as it whould when running a program. In the meantime we're wasting time leveling the sheets we have to cut, so feedback would be very much appreciated.
Here's the code we're using to test the THC with a simple cut:
