When I started using V2.0 I had an issue with the fire button not matching the laser FIRE condition. Red was off or on or Gray was on or off. I could duplicate the condition as reported. by the next release the condition was patch to work better but was still not fixed but was said could take some time to correct. As of V2.0.3 the Fix list says something was corrected with the laser “Fix for Stop button not properly resetting laser state to off”. Not sure if this was related but I’m still having the same issue with the fire button show on but laser is off and on when indication is off. I’m using Lightburn with two Ortur LM2 Pro GRBL/Gcode laser. I have not installed the latest version .04 Lghtburn as the 2 fixes listed are not related to my issue. Was this issue forgotten or still on the backburn for other than Hobbie class systems.
There are no “Hobbie class” systems in Lightburn. It is either Core or Pro, determined by the controller type. I have 3 “Hobbie class” machines and the Fire button works (indicates) properly on all of them.
Please provide a screen capture (SHFT+WinKey+S) of both states (conditions) you see on your screen. There may be something else in play here.
I don’t see where i screen shot of a fire button in a red or green state will give you much information without seeing laser condition at the same time.
Explanation of condition i found to cause the issue.
Start Lightburn, boot laser. Draw an object then frame object. Before framing stops go to Move and select the Fire button. Fire will go from gray to red. When framing stops laser goes off but button is in red state. Select Fire again button goes gray but laser turns on. Select again and laser flashes but stay red and system is back to normal.
Text of console below if that means anything.
I didn’t have this issue before 2.0 and was I reported issue during the RC phase that was patched to work better but was never totally fixed. As the joke goes, Doc, when i move a arm like this it hurts. Doc says don’t move your arm like that.I go between using the fire button to line up objects and the frame button frequently.
<Idle|MPos:113.475,48.213,0.000|Bf:35,7679|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0>
ok
Starting stream
Stream completed in 0:17
ok
ok
ok
ok
<Idle|MPos:113.475,48.213,0.000|Bf:35,7679|FS:0,0|Pn:P|CL:0,100|PS:2,1|ER:0,0|VA:24508,0|A:S>
[GC:G0 G54 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F100 S0.]
ok
ok
ok
ok
ok
ok
What you describe happened to me back on v1.0.06 when I had some screen layout issues. I just ignored it then because it did not happen again.
If Lightburn was busy streaming the Frame when you clicked the button, that might explain it. Maybe the button should have been ignored? I always have the laser on (0.25%) when framing, so I would never be clicking the fire button during that operation.
I agree this could be a software glitch. It sounds like the toggle state can get confused. I do not see this as a safety issue because you should have glasses or closed enclosure when Framing, but I see where it can be irritating.
Didn’t Know the issue had to be a safety issue to be corrected. Your right this is a annoyance. Condition two recreation for Lightburn not detecting the off state. Select FIRE button to place laser at corners of an item and not work quick enough laser condition times out. The button state is now Red (ON) but laser turns off. The annoyance is having to select FIRE twice to restart laser to continue framing. Does seem to be a toggle state issue.
I had what I thought was an issue with the RC version not showing the exact position of the laser in relation to the object I was find the corners zoomed in tight to restart a cut when laser was bumped. Laser would go everywhere other than the corner. Was told the pre 2.0 did’t show the exact location of the laser, beam size was larger than Lightburn grid size. Lightburn 2.0 was actually reading the location of the laser and not the place the laser the corners i was selecting. So with that I can assume Lightburn would think as with laser position read the sate of the laser being on or off.
There is another condition that causes the Fire button to show RED,on, but i have not taken the time to figure out how to reproduce the condition. Running two of the same lasers at the same time may have something to do with this third condition that only happens when powering up the other Laser.
I have a few other issues but they are not safety related and not FIRE button related. Just another annoyance. I could not do the things I do with these laser without LaserBurn. I always look forward to updates to not only see what new features are added to help in being creative but to see what bugs have been worked out to give us software with smooth annoyance free operation.
Thanks for supporting the users of LightBurn.
I am sure you did not mean that the way it sounded. To correct any issue, somebody has to figure out what is causing the issue. And sometimes the issue is so rare, or not irritating, that it takes the Developers time to hear about it. Obviously safety issues go to the top of the list. You can see what else gets fixed by reading the Bug Fix Report issued with each patch file. Not much gets ignored.
You can run Lightburn with 2 instances by using the New Window selection. However, you cannot run 2 lasers off the same USB port. Most hubs will not instruct Windows to assign separate COM ports to the same PC USB outlet. You may need 2 USB cables plugged into the PC.
I am just one of the many Users helping other users of Lightburn.
I am sure you did not mean that the way it sounded
Did sound sarcastic, maybe… or just a little frustration over a 2.03 bottom of the bug fix list that somehow again missed my CORE “Hobby” laser. '“Fix for Stop button not properly resetting laser state to off". Seems like work was done here yet no fix for me. I agree safety comes first yet it’s easy to see by reading the bug reports that more popular lasers or PRO “Business” class lasers get more attention.
Run Lightburn with 2 instances
I already got that going some time ago which is why I bought a second slow cheap Laser. Double my production level. I’m not sure how you’d run two laser off one port other than a cheap TEMU multiport hub or spicing two cables together. I do have two location for my USB ports, motherboard and front of system. Each laser has its own assigned port COM 1 and 3 with one at the MB and the other at front of system.
helping other users of Lightburn
I had started helping others with the RC release phase and was promoted to Private First class helper. Sarcasm? just goofing but true. Most issues were mostly the fact no-one reads the very well put together manual. I stepped back from that due to the etiquette manual I had to follow in making replies.
I do appreciate you providing help with issues. At least here its not like dealing with an IPS where I can’t understand the broken English and they read off a sheet of paper in front of them steps for me to do of all the simple things that i’ve already tried. Just hook me up with the tech that actually knows what the issues are and what to do to fix. It may be me being an engineer for forty years but unplugging the router and plugging it back in “REBOOT” does fix many issues.
With that is there a place to actually report an issue other than the forum. The first time i worked with someone with this issue that tech reported the issue and a patch that somewhat got me going where I am today was in the following release. As with release 2.03 stating that programmers fixed an issue of the laser off state means someone was working in the area of the laser indication yet i’m still having the issue previously reported. This may mean the patch of many months ago was what was considered a fix and ticket closed which is why i brought the issue up again.
Thanks, and have a super day… Really, No Sarcasm!
Wow! That was quite a reply for what is a simple issue. No matter, it is okay to vent as long as you keep it civil. 
I just tested the Fire button with v2.0.04 (Win10, diode laser) to see if I could duplicate your issue.
- Fire on/off works as expected.
- Laser On When Framing enabled. Laser behaves as expected.
- Fire button on, laser on. Frame, laser frames with laser on. Frame ends, laser remains on. Fire button off, laser off.
- Laser On When Framing disabled. Frame, no laser as expected.
- Fire button on, Frame, laser turns off as it should. Frame ends, laser stays off as it should. Fire button still red. Click Fire button, goes grey, laser still off.
- Fire button (red), laser on. Fire button off, laser off.
Summary: I see nothing that duplicates your complaint about the Fire button.
Update to v2.0.04 now. If you still have this issue, describe the detailed sequence of events leading up to and during your test. Without the exact details, there is no way this can be resolved by the programmers.
I followed your steps after updating to 2.04 and you replicated the issue in step five I’m guessing there nothing wrong if the laser is off when Lightburn indicates the laser state “red” is meaning the laser should be on.
Try turn laser on, Indication RED and just let the laser time out from the on state. Mine takes around two minutes, the laser shuts down but FIRE indication is red stating laser should be on. You then need to turn Laser off and back on for laser to return to on state. Seems lightburn is not truly reading the laser state but red or gray is just an indication that a button was pressed.
It’s just an annoying condition that happens when I’m tasking Lightburn to do sometihng that most user may never do. Lightburn is far better than the basic free laserGRBL and inkscape.
There is no “read the laser state” mode in this system. Lightburn is more like a request and response web page. It sends GRBL commands (request) to the controller and waits for a response. A study of GCode commands will illustrate what is available to Lightburn. It seems you see more interaction between the controller and Lightburn than actually exists.
…anything available at their (or any) price point.
Think in terms of safety.
No, Lightburn is indicating the last Fire button command (request) was “on”, not that the laser should be on.
Well now, maybe it’s because the fire button function was technically explained on how it operates or the fact I installed 1.7.08 and gave it a go I see that the state of the button , red or gray is just an indication that it was selected to start or stop that function. To add to this if it was a indication that the laser was on vs an indication that the button was pressed it would turn red any time the laser was on. Duh on me. Sorry to bother you with this non issue. I’m going to run the older version on a new project I’m starting to see if some of the other quirks are in the old version or something new since 2.0. Maybe I can bother you again…..
V1.7.08 is a stable version, so you should have few issues. v2.0.04 is also stable, with only some display issues easily fixed.
No worry, I will be here.