You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OMTech Polar provides an electronic focus by moving the lens up an down as a separate axis. This is not supported currently with VisiCut, as the axis cannot be moved from the device directly (the user interface is basically a single big button that functions as play/pause when used with VisiCut).
Other software, e.g., LightBurn, provides an option to configure a focus value. For this specific device, we know that the honeycomb bed is at an offset of -17. To focus on, e.g., a 3mm thick material, one enters a value of -14.
I could imagine support for this in VisiCut by combining an option from the Epilog Zing driver (focus on the bed instead of the material surface) in combination with a global focus offset (-17 in this case). To work on such a 3mm thick material, one would enter a focus offset of 3mm for surface work (marking, engraving) or 1.5mm for cutting.
The text was updated successfully, but these errors were encountered:
The OMTech Polar provides an electronic focus by moving the lens up an down as a separate axis. This is not supported currently with VisiCut, as the axis cannot be moved from the device directly (the user interface is basically a single big button that functions as play/pause when used with VisiCut).
Other software, e.g., LightBurn, provides an option to configure a focus value. For this specific device, we know that the honeycomb bed is at an offset of -17. To focus on, e.g., a 3mm thick material, one enters a value of -14.
I could imagine support for this in VisiCut by combining an option from the Epilog Zing driver (focus on the bed instead of the material surface) in combination with a global focus offset (-17 in this case). To work on such a 3mm thick material, one would enter a focus offset of 3mm for surface work (marking, engraving) or 1.5mm for cutting.
The text was updated successfully, but these errors were encountered: