In past versions os lightburn turning on “Show Last Position” will show the current position of the laser with a cross hair. In the 2.0 version turning on this function does nothing until i select “Get Position”. When laser is moved to a new position that new position is not indicated until I select “get position” again. I’m not sure if this is a new way the programmers feel this function should work or just as bug. It’s very cumbersome to use this way.
So i guess my question would be is this the future of this function or a bug and if future is there a way to do a command peek and poke to make this 2.0 function like its predecessor.
I’m pretty sure the laser position hasn’t been shown live in older versions.
Thanks for a reply
As per instructions on documents the function was working as shown in the video demo of how it works. Click “Show Last Position” and a cross hair shows at the current laser position. Move laser to another location and the new location is shown each time I move to a new location without having to click Get Position each time. In 2.0. i must click “Show Last Position” but no position is shown until I go to MOVE tab and select “Get Position” each time I want to show the indicator of that new location. Hover over show last position and info says “Note that this only updates with click to move or when get position is clicked”. Every version prior to 2.0 has worked an shown in docs. I just started using 2.0 RC7 and now 2.0 RC8. If this is how it’s supposed to work then docs need changed and the Show last Position button can be removed or replaced with Get Position as show last position button serves no purpose on the laser tab.
Ok, then I’m remembering wrong.
Hi Don, I have tested what you write on my Linux machine which has the last version of Linux (1.7.08) and here it works as you describe it with the small limitation that after about 10 seconds the function "Set Laser position…) in the left menu must be reactivated. I think it has always been like this, for safety’s sake. However, the cross moves depending on where it is moved, it is correct and is displayed “live”.
In Mac version RC 8 it does not work. I can move the laser head around but the current position is only displayed if the button “Get position” is pressed, and it must be pressed again for updating, so no live movement for the 10 seconds.
So you are right, it must be a bug.
I’ll send a link of your post to the beta section.
1 Like
Thank you, I’ll report as a bug. So far i like the new version and for most everything I commonly use and test of new items this is the only issue i have found.
1 Like
I’ve reported it and Rick is taking care of it. 
3 Likes
This has been raised internally and being discussed. Thank you for drawing our attention. 
@Brandrew Can I ask what protocol you’re using for your machine?
We found a similar bug in the Emblaser 2 protocol, but I wanted to check where else it might hide.
Thanks.
I’m running Lightburn on two Ortur Lasermaster 2 pro lasers if that info helps. GRBL
1 Like
Thank you. We’re putting a bunch of fixes in for gcode machines currently. We’re running through another batch of tests internally now, and hopefully the next RC will have fixed your issues.
2 Likes
The position tool now works on the new release thank you. It does work different manner that prior version and that’s okay, but i find it’s not accurate. The different is as someone use to say “Finer than a frogs hair” but i do like accurate. To produce the issue, draw a 5mm star since that’s made simple now. Zoom in close and use the position tool to move laser to any point of the star. The position cross hair never points to the actual point of any point of the star. If you move the mouse to reposition the laser down the line of a vertical side of the star in small increments the position is shown left or right of the line. never on the line of the star. It’s like the position is displaying a small unseen grid and not that of the actual line drawn.
I’m guessing since the tool now works in a different manner than prior releases the code is actually reading the laser position in a tolerance of some small pixel size pattern and showing a corner of the pixel and not showing location of the actual drawn object.
We’ll take a look at that.
Are your units in inches for design or device configuration by any chance? It sounds like we’ve got a rounding error somewhere, so any feedback you can share will help us narrow it down.
Even better would be if you could share your configuration bundle (with the LB configuration included, not just device profile) to help us replicate and debug this last bit of oddity.
Unfortunately not on my Mac OS. I still have to press “Get Position” to make the “target marker/crosshair” visible every time.
I have not seen this problem in my version/setup. The positioning of the laser on the tips of that star is very precise. The picture shows short laser pulses, right on target.
(the size of the star is 23mmx22mm)
Pic 1 shows position indicated when I select top peak of star. Pic 2 shown position indicated when I select left peak of star. I’m zoomed in tight on a 5mm star, I only used the start for the pinpoint to select for the example.
There is a difference in 2.0 VS 1.7 on how the position in processed. When I select the peak in 1.7 the cross hair indicates immediately where the laser is going to be and in 2.0 indicated location after laser moves to position which seems like a representation of the actual location. Measurement of how far location is off in any location from the selected object is .01mm. Like i said in the original message, finer than a frogs hair. The actual laser spot is about .05 mm so .01 mm is maybe not as and much of an issue as the representation of where the crosshair lands.
That’s probably why it’s almost invisible in my practical test.
But, the bug (in MacOS) of not showing the current laser position “live” is still there.
config.lbzip (5.8 KB)
If this is not what you are looking for, please tell me how to get this Bundle. I mostly use my setup in MM so I have LB set up for that.
I guess what i sent was correct. App settings and Device settings The only items i left out of the bundle are my projects. I really don’t want those public. I attached my machine settings file if that helps.
Machine Settings.lbset (5.9 KB)
I just created another Device setup and have the same results. What i have found playing with the position tool is that the selected location is spot on accurate if i zoom in all the way and select a cross point of the grid.Indicated location varies when selection is not of the grid pattern.
It is possible that your snap function is messing with you a bit. To test it, you can turn it off and try again.
My snap is set to grid and nodes, when I snap to the tip of the star from the drawing, it “sucks” itself almost to the target. Then I just press the pulse button.
Finding/hitting a physical object precisely with the help of the camera function alone is not that easy.