THC Stopped Working - Both THC Enabled and THC Active not illuminated

rodw wrote:

Sparky, there is an address here you can send your brix to here.  www.vmn.com.au/
I'll try and get it going for you when I have a free moment. You can also contact me through that site via chat or the contact us page. 

 

Thanks heaps Rod! I will post it up soon. I will be very interested to see how you go with it. It will be good to rule out human error as the issue with someone who knows what they are doing taking control

THC Update 7/04/2022.

I have been monitoring the behaviour of the faulty THC for the last few days to see if I can find any patterns.

What I didnt realise at first is that on startup the 'THC Enabled' button is illuminated.

Once I start to run a job, the 'THC Enabled' stays on and the 'THC Active' lights up. For the first cut on any job the THC runs perfectly as it should. as the arc stops at the end of the first cut, both the 'THC Enabled' and 'THC Active' lights go out. The THC then stops working. Torch still works, arc volts are still read by PlasmaC when cutting next part, just no THC.

Does this point towards a post processor issue? Even though I haven't changed anything at all in that space.

I have played around with THC Enabled in the 'Materials Tab', THC Auto/Enabled, Auto Volts, VAD lock all on/off in the 'Run Tab' and have not noticed any difference. I have also checked sheetcam and doesn't appear as though I've hit any buttons I shouldn't have. The only thing I can think of is there is a new update I still need to run, perhaps it has disabled THC like some cars disable cruise control when the engine light comes on? Time to get to the mechanic image missing /media/kunena/emoticons/laughing.png

It would be helpful if you could post a backup of your config (made from the backup button on the config tab of PlasmaC), as well as the g-code file you are trying to cut.  That will take a lot of the guessing out of the equation.  

Here is the backup and g-code file. 

Had to convert the .tap to a txt file.

 

 

Just took a quick look at your g-code file.  There are several lines with this:

At a minimum, if you remove them, that should do the trick.

As far as where they are coming from, it's harder for me to say.  It could be your post processor but it's probably more likely that you accidentally enabled a code snippets in the operation on SheetCAM.  I did something similar once on total accident/was unaware of it at first.  I set it back to the 60% velocity reduction on holes snippet that comes with the post, etc.  I dont have SheetCAM loaded on this computer, or I'd grab you a screen shot, but it's in the operation where you choose the material, layer to cut, etc.

Ah yes! I can see what you mean, I will turn that off and see what results I get