103
« on: July 27, 2019, 12:44:01 PM »
I would get the latest dev build and do a clean install of it, copy the default plasma profile as something unique and configure that unique profile for your machine. Old screens modules, macros, profiles, etc. may cause problems.
Yes, the THC module uses an OB axis to control the extra moves of the Z to maintain the set distance from the material. The reason it uses an OBA is because the only way to control a coordinated axis is through Gcode. OBA gives us a layer we can control independent of what the coordinated axes are doing.
Sounds like you should be running in Digital mode with the up and down outputs of your THC is mapped to the thc up and thc down input signals in Mach. Also make sure you have set the configure/plasma screen config. settings. What ever OBA you use, its motor should have the same motor tuning settings as your Z.
Make sure you play with the THC settings to get it all dialed in for your machine. Adjust rate, min, max, etc. I would start with very low adjust rates and a large window (min, max).
Not all motion devices support OBA. I know THC works well with the ESS.
It is a software solution and while not as fast as hardware it should be fast enough for the vast majority of users.
The way it works is really pretty simple. If the THC sends an up or down signal a velocity jog of the OBA at the adjust rate is started in the right direction. When no signal exist, your slower than anti dive rate, THC is off, etc. a velocity jog stop is called.
M5 basically just turns off the torch and moves the OBA back to 0.000 where it should have been when the M3 began.