This is the strangest part for me - If LightBurn detects that your machine is a KT332N, it automatically redirects all commands for the Z axis to use the U axis instead, including the jog buttons - When you click the up/down arrows, if your Z axis is moving, that part is using our remapped jogging commands.
The “Get Positions” function is reading the U axis position and displaying that as the Z position, which could explain why yours is reading funny, but I’d honestly expect the Z axis values not to change at all, not read weird values.
It sounds like Monport had them make a version of either the controller or firmware that sends Z commands to the U axis, but only when running a file (maybe?) which breaks all our internal remap logic. Can you verify that for me? As in, you push the Up/Down arrow buttons and the Z axis moves, but Z commands in a running job don’t work?
One thing that’s worth asking - Are you trying to make the laser go IN to the material, or away from it? Where does the auto-focus trigger? At the top of travel, or at the material surface?
Based on what your machine is reporting for the Z coordinate, I’m worried that there may be more going on “under the hood” that just redirecting the commands from Z to U.