Hello Chris,
The Machine Units should be the same in both places.
This can be set in the Device Settings (F3 key).
Can you try changing it here and let us know if it updates in both places?
Hi John,
1. Random hangs laser just stops.
2. Random hangs of GUI, laser keeps running and finishes job correctly.
3. RC 6 forgets laser is attached over night.
4. Camera freezes both web cam and AC1 Atomstack
5. Camera setup leaves rounded sides regardless of camera mode
6. Busy time estimate is WAY OFF so is preview
7. You need to set default for Z increment on Move dialog to 1.0 instead of Zero
8. No ability to restart at last good known G-code line index
9. No laser cooling cycle available
10. Need a laser hours timer with a 10hr pop up to remind user to clean their laser
- Weāll need more information to diagnose, are you able to replicate the issue in a repeatable way?
- Same as above - weāll need steps to replicate in order to diagnose.
- Could you go into more detail? I wouldnāt be surprised if your PC goes to sleep overnight if USB comms get affected.
- When the camera freezes, do you get a crash? Are you using a USB hub or extender?
- Could you provide a screenshot of this? After lens correction it is expected to have a non-square image
- Time estimate is configureable from the āEdit > Device Settingsā screen. You can read your device settings from the controller, or input them yourself and adjust until correct.
- Does changing the move increment here not work correctly?
- You can restart a job at any point from the Preview window - we have a video covering how to do that here: https://youtu.be/o1_FKGhJoek?t=263
- This has actually already been suggested and logged on Fider, Iād suggest you show your support there so we can prioritize feature requests appropriately: Most manufacturers of diode lasers recommend so sort of burn/cooldown cycle. Ā· LightBurn
- Another good feature request! Please submit that to Fider via the link above.
Oh no, not that bloody german user again ā¦ just kidding ā¦
And in case I forgot to mention it: Lightburn is a damn good piece of software.
1 Like
Iām noticing another potential issue from this screenshot.
The underlined shortcut indicator for each menu item doesnāt correlate to the listed shortcut.
Example:
āExporitierenā shows a shortcut of Alt-X, not Alt-E as would be expected based on the underlined menu entry.
Note that Iām not aware if this is something wrong in the menu entry, in the shortcut displayed, in shortcut customization, in the localization model, or something else entirely. Only noting the discrepancy.
Hi, I have downloaded Lightburn pre release 2.0. My laser goes to frame but then stops and does nothing. Can someone please tell me why? Thank you.
Any updates on this issue in RC5 & 6?
Itās much easier on me if you donāt say āthis issueā and make me scan backwards through a half dozen posts to find it. I generally have about 15 or so ongoing things, so I donāt always remember who posted what.
And yes, as posted before, the jogging issue for DSP controllers is fixed, but weāre waiting on some additional confirmations before posting an updated RC.
Keeping in mind that the M1 was released in 2020, the last Intel MacBooks/iMacs were discontinued in January 2023, and that QT has supported ARM M1/M2/M3/M4 āApple Siliconā natively since v6.2, is there a possibility of an Apple/ARM build?
I realize that Lightburn can currently run via Rosetta but it would be nice to get some native RC builds going because eventually Rosetta will be deprecated- and because itās an annoyance to install the compatibility layer.
1 Like
Taper warp worked twice and then I closed out for the day. The next day it has the same settings but a new design and itās overcompensating. The width is becoming much longer than the circumference of the thickest part of the tumbler leaves a gap where the top touches but the bottom is left open.
1 Like
The generator for testing materials does not change the red outline when turning off the outer contour and text. the outline by size remains the same. Is this a problem for me or does everyone have it?
1 Like
I am having exactly the same issue with A win 10 HP Laptop, Ruida 6442, chinesium 1300x900 80W laser. - running RC6 the move window will not get the position at all, -if I enter the move to position coordinates and press Go it will move the head to those coordinates but they are not reflected in the get position info and attempting to Get Position results head returning to the 0/0 position and everything reading 0/0?? Also attempting to move using the distance and arrows in the window also results in everything going back to zero/zero,I have reverted to 1.
7.04 and all is working normally there - Hope you can provide a fix with your usual speed and efficiency!!! Thanks, Bill
1 Like
In prior versions of Lightburn, the thickness values displayed in the Material Library reflected the selected type of measurement - Imperial or Metric.
In 2.0.00-RC-6, at least on my installation any thickness is always displayed in Imperial.
If this is an intentional change, it seems a step backward but Iām hoping itās a bug that will be resolved.
I donāt know the reason for what you are seeing but for info, I am not experiencing this, my thickness values in RC-6 are displayed in metric which is correct for my set up.
I am curious - if you change the unit of measure, is the thickness updated to reflect the current unit? I have both 1.7.08 and RC6 installed, 1.7.08 updates the display in the Material Library, RC6 does not.
I just compared 1.07 with 2.0 RC 6.
In 1.07, you can edit the description and switch between āinā and āmm.ā
I couldnāt do that in 2.0 RC.
I am able to toggle the unit of measure in RC-6 and most measurements in the UI are updated as expected - except the thickness in Material library and the Distance in the āMoveā window.
You are right, after changing the unit of measure in RC-6 the thickness is not updated. It does however update in 1.7.08.
2.00 rc6
Rudia co2 laser
Will not read current position on move tab and no red mark.
Cut setting editor cant resize window to hit ok button
Screen resution on laptop 1366 x 768
Yes, an ARM build is on the roadmap.
Thank you all. I can confirm the observed behavior and will generate a report. 
Moving this to the main RC6 thread for tracking.
2 Likes