Thats my point. You only need to send the divided voltage and ArcOK to Linuxcnc and the motion controller can directly control z axis torch height instead of using a rather crude method of generating up and down signals for the reasons outlined so eloquently by Peter from Mesa in a more recent post. But not only that, you can build vastly more sophisticated control such as velocity anti dive, kerf crossing, auto torch sampling etc into the
motion control setup that has direct access to all real time motion in an environment with almost unlimited memory and CPU horsepower