Hi team,
Is it possible to move either the ‘camera control’ or the ‘move laser’ tab into the bottom half of the right column?
We’re looking at using a head mounted camera to assist with print and cut line-ups, and being able to have an image preview and the laser move controls both active at once would be super helpful.
Also helpful would be a ‘pulse’ button available from the move laser panel, but I’m not sure if this is a feature the controller (Ruida) exposes to Lightburn.
You can grab any window by the top bar and drag it off the dock, then re-position it where you like, as long as there’s room for it.
It doesn’t, unfortunately. It would be possible for me to send a job to the controller that consisted of a single pulse. I’ll think about it.
We’re in the early stages of adding head mounted camera support, so there’s a decent chance that you’ll be able to click-to-move within the camera control window when that’s done, and I may try to add jog controls too, if there’s room.
Ah! I tried dragging the tab handle, and could only get it to change order in the tab stack.
Head mounted camera support would be a great addition. We find (in our particular case) the red dot alignment isn’t accurate enough for pass-through jobs, so we pulse the laser to dial the alignment in. This involves a lot of move-pulse-walk over-lean in-walk back carry on which gets tiresome on big jobs.
For that, if your laser is a DSP controller, you can jog close to the mark, then set the speed to 1mm/sec for fine tuning. I’ve used this with the pulse feature myself on a machine without a red dot. Then just bump the speed back up to move to the next mark.
That’s exactly what I do when I am using Print and Cut. It works well.
Yep, that’s what we’re doing. While I’m feature-requesting on this topic, it’d be great to have a fast/slow toggle to avoid having to manually reset the speed for those traverses.
Ctrl / Shift / Alt in combination with the jog buttons will move in larger or smaller steps, but that only works in “discrete” jog mode, not continuous.
The specifics are:
case KM_None: break; // no change
case KM_Shift: moveDistance *= 5.f; break;
case KM_Control: moveDistance /= 5.f; break;
case KM_ControlShift: moveDistance /= 10.f; break;
case KM_Alt: moveDistance /= 50.f; break;
So Ctrl, Ctrl+Shift, and Alt all reduce the distance, and Shift by itself increases it.
Thanks Oz. I knew these worked for general moves around the program, but we’ve been doing the alignment on the controller, and only using Lightburn to “set” the targets. If we had the head camera vision on screen, we would definitely be doing this all through Lightburn.
I think having a 300mm/s and 1mm/s (for example) direct select of some sort from Lightburn would be helpful for this workflow, instead of the Ctrl/Alt modifiers.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.