Not all the time but with the latest update on Mac with Woodpecker 3.4 when moving with test fire enabled the laser stays on.
Additionally the pause / resume buttons doesn’t change. If hit stop button have to physically unplug USB to get to work again.
Also is the Z height supposed to change when doing the laser focus test as it doesn’t. (First time using)
Also Z doesn’t move when go to origins it also didn’t in previous version. Not sure if it should.
When you have the ‘Fire’ button enabled, the new version leaves the laser enabled. It was a constant source of complaint, so I relented.
If you hit Stop it is considered a “hard abort”, and the laser goes into alarm mode. You have to right-click the ‘Devices’ button to reset the connection and clear the alarm. If you pause first, then stop, it will stop without doing the emergency stop, and won’t throw the alarm. This is just how GRBL works.
Z doesn’t move unless commanded to, ever. If your machine includes Z in the homing cycle, it will reset when homing, but many lasers don’t have Z control at all, so it’s ignored unless enabled in the device settings.
Oz, ctrl+shift on older versions always left the fire enabled while doing frame. shift was documented as the way to keep fire button during frame. I don’t know why the discrepancy between what was documented and the behavior, but I suspect it was the source of complaints.
I just installed 0.9.14, and I have the fire button enabled and working on my diode laser. The frame button doesn’t have it turned on by default. Shift+frame does work, so does ctrl-shift-frame.
Because users are never satisfied, can I also request a way to run frame many times for one click, maybe with a toggle button, so I have time to get to my laser on the other side of the room and see the frame and place an object before it has finished it? Not indefinitely as someone is bound to leave it on for a week but maybe for thirty seconds or a configurable amount? Maybe even just add a preference for how many times the frame button draws the frame every time, with no UI changes?
Ctrl key doesn’t actually affect the frame, just Shift. We could conceivably make the Ctrl key act as a repeat - like, “run it 3 times”. I’ll think about it.
three times would be the bare minimum - frames happen quickly by their very nature! Ten is more like it, but a preference would be better. Ideally with the frame button toggled down so it can be sued to stop it if needed without using STOP and putting it in an alarm state.
I don’t need it slower, I’d like it to be faster - I need to keep moving the object and making sure every edge is still in the correct place, so a slower moving dot doesn’t really help with that. I didn’t really mean it went too fast anyway, just that drawing a frame is a simple operation and completes quickly. The correct solution is probably to get a camera and place objects based on that, except they are all double the price and out of stock right now. Having multiple passes run when you press frame is simple and foolproof.
Oz, in fact Ctrl+Shift is needed for fire to stay on during frame. If you change the behavior of Ctrl it will break those setups that require Ctrl+Shift unless you can ensure all setups can enable laser staying on during frame with Shift alone.
I know with code development there are a lot of dependencies. Debugging things requires acute observation. So here’s my setup and detailed behavior (some of which is probably not relevant, but added for completeness).
Device: Grbl
Fire button: toggled on
Start from: Current Position
Job origin : upper left radio button
Image upper left is placed at x,y = 25, 25mm (non-zero) Shift Key pressed, hit Frame button
Laser is on before Frame button is depressed
Laser turns off while moving to x,y=25,25mm
Laser stays off while framing.
Same setup as above, Ctrl+Shift button pressed, hit Frame button
Laser turns off while moving to x,y=25,25mm
Laser turns ON while framing
I will look at whether the image upper left is at the origin whether it toggles the behavior.
Happy hunting and Keep up the great work!
I can say for certain (I’m staring at the code right now) that it is not looking for the Ctrl key, only the shift key. The fire button does not need to be on for the power to be shown when framing. @T_Roth1 - Which version of LightBurn are you using?
Hi Oz, I’ve only tried the fire while framing since the Fire button showed up. If it was possible before fire button was even present then it was an Easter egg I was not aware of. Possibly the fire button on/off is a key dependency, I’ll have to verify later. Sorry I can’t be of more help, I can only tell you what I’m seeing.
Maybe it has been since 0.9.10 and still occurs up to 0.9.14, but not fresh installs.
Oz, as you mentioned with Fire button off Shift+Frame allows the frame with laser on at low power.
Another observation is that if you have the fire button on and try to frame once the laser turns off (if not holding Ctrl+Shift), to get the laser to fire at low power (when not framing) at that point takes selecting the Fire button 2x.