-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move along boundingbox ("Preview") #181
Comments
I like this feature very much and want it myself, so as soon as I have time, I will implement it. |
Quick Solution: Create a new Laserprofile with a name like "Preview" or "Move Outline" and select the "use outline option". Also disable any optimization by selecting "FILE" as optimization algorithm. In the laser-settings for that profile just select 100% speed and 0% power. Works for me. This also has the advantage, that it does use a tighter outline than just a bounding box. Didn't test it with complex shapes though, so it may be, that it will also move around "inner" shapes. |
Ruida devices apparently have a specific command built-in for such a preview feature. I retrofitted a control panel on an OMTech Polar (which features a 6442S controller). It has a "Frame" button that (like in LightBurn) runs move commands to show the bounding box of the object for the currently selected job. I suppose this feature depends on a correct bounding box being sent to the device as part of the job, which the Ruida driver does. As discussed in #711 VisiCut could just send a job doing the same (or in the distant future send these commands directly ad hoc). |
Some people might want a preview of the boundingbox of their design on the material.
We could add a "Preview" button next to the execute button that only sends the outline of the complete job. The preview power could be 0% power and speed could be100%, but of course it would be great if this was configurable.
I would place this button left to the execute button.
(I still think the VisiCam solution is a better one, but it's more work to setup)
The text was updated successfully, but these errors were encountered: