I built a CNC Plasma table that uses OpenBuilds Control software to drive the table. I am adding a THC to my build but the THC references having to create cutting instructions in SheetCam in order to take advantage of the anti-dive capabilities of the THC. I have been using Fusion 360 since I have a Mac and the OpenBuilds post processor. It seems that the post processor is where the cutting instructions should live for the THC. The anti-dive features seem to be tied to specific types of cuts like in the attached pictures - i.e. corners tighter than 45 degrees, or shapes smaller than 5mm. Any thoughts on how to handle THC with OpenBuilds post processor or with Fusion 360?
I am wondering what causes this diving that makes antidive necessary? (is it some fundamental problem with the THC?) do we know for sure that we need it? (ie, run the machine and prove it) then there is the lack of an output pin from which to control it, maybe relay2 can do it after a recompile with custom pin mapping. but, given a relay to control the signal, say tied to 'mist coolant' on M7/M9, then, yes, the relevant logic can be added to a postprocessor to output the relevant Gcode, provided Fusion gives us the information we need during processing.
It seems cutting small areas can cause the voltage to change if the speed slows down. Tools like Sheetcam can generate gcode that slows down the cuts to cut better in small areas like small circles. This causes the THC voltage to raise which it decides to lower the torch height to compensate. The anti dive stops that from happening. I haven’t seen where fusion could give the chance to insert hints for gcode generation. Sheetcam looks at the geometry based on rules that you can provide
Also if the cut path crosses already cut areas that have dropped out, the THC will plunge the cut head into the open hole to try to maintain the voltage
