I’ve been over all the threads, tested everything voltages everywhere, cleaned the z assembly, and for the life of me, I can get no consistency out of this setup. It has been working flawlessly up until this point (yes, the THC and Razor cut 45 were working at one point).
I’m using the Razor Cut 45 and the THC. I’m running V21.1.2 of the firecontrol software. The plasma torch fires just fine if I walk up and pull the trigger on it, but the Resting THC voltage always comes back with 0.0v and the subsequent test firings do not fire.
My frustration with this entire rig is approaching my limit.
I just started seeing something like this today. The THC has been working perfectly up until today; it worked fine, in fact, for a couple cuts and then started acting up. It would fire for a brief moment and then cut out. Doing a health test showed 0V, but when I trigger the torch directly through the software and perform straight cuts (using the jog feature) I get a correct live voltage readout.
That is correct. It fired the torch during the test but said that it was seeing 0.0V and sent me to THC troubleshooting, but during cutting I did see live voltage (though I believe it was 33-34V while doing straight cuts with jog).
It’s worked fine previously so I sincerely doubt anything is miswired. I’m running an Everlast 52i.
The torch would fire on GO and then immediately go out, whereupon I would get an error about the torch moving without voltage being sensed.
Weirdly, I just went back out to the shop to re-test and everything worked fine this time. Is it possible that a splash from the water table may have caused poor voltage readings?
Thanks so much!
------ THC health check report 11/11/2021 ------
RESTING VOLTAGE TESTS
[17:31:20] average voltage = 0.00V
LIVE VOLTAGE TESTS
[17:31:39] average values: [71.00V] [71.95V] [73.33V]
I’ve tested the wire for continuity and it checks out OK (I taped the testers to the torch firing wire). I manipulated the wire over and over and around and around (and pretty aggressively) and I couldn’t simulate the short (if indeed that’s what the problem is).
Something in this rig is hairbrained - it works, works well, then poof - stops working.
Could bad consumables (ie: maybe I’m running them too long) be the culprit?