I posted my issue on Lightburn forum but it’s now becoming too much downtime. In the Lightburn console after every Move action it’s resetting position and coordinates. This means I cannot move the laser head to a position and mark/save it’s coordinates for repeat burns. I’ve tried setting the material up to be under a specific coordinate but this has never been ideal. Without the Ray having a mounted immobile laser bed it’s nearly impossible to use this method. I’m constantly switching from the rotary to bed so I can never place the bed/material in the same place. Without a camera on the Ray I cannot line up the design to the materials either.
If anyone can help I’d REALLY appreciate it.
Here is the output from the console after every head movement:
$H
ok
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
?
<Idle|WPos:0.000,400.000,0.000,0.000|FS:0,0|WCO:0.000,-400.000,0.000,0.000>
ok
Starting stream
G21 G54
G91
G1 X0 Y-100 F6000 S0
G90
M2
[I][PLAT]Program End
Stream completed in 0:01
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
?
<Idle|WPos:0.000,400.000,0.000,0.000|FS:0,0|WCO:0.000,-400.000,0.000,0.000>
ok
Starting stream
G21 G54
G91
G1 X0 Y100 F6000 S0
G90
M2
[I][PLAT]Program End
Stream completed in 0:01
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
Thanks for you response. I was using v1.7.2 with no issues before my laptop melted down. When I installed everything on the new PC I had this issue out of the gate. I learned they released a new firmware version the day after my issue was discovered.
I guess it wouldn’t hurt to rollback the firmware to see if anything changes. At least then I might be a little closer to the root cause of the problem. Right now it’s just speculation on my part that the issue was with Lightburn and the Ray since Luban works as expected.
It would be really nice to get this fixed today. My IR module is being delivered today. I supposed I could use it on the SM2 or use the Ray with Luban. I’ve spent all my time and energy learning Lightburn so without it I feel like I’m working without arms.
It would be really nice if some of the Snapmaker Team members could chime in.
I now have reason to believe the new A>B feature that was introduced is the cause of the newer firmware resetting the coordinate position in Lightburn. I wonder if there’s a way they can add a toggle to switch between A>B and Manual Modes. They have this option within Luban but nothing in Lightburn to make that switch and it appears to default to A>B.
With every move of the head in Lightburn the console says the position and coordinates are being reset because “disabling motor” expressed as:
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
So with the offset required to work with the ray (I’m talking about having to enter “G10 L2 P1 X0 Y-400” into the console in Lightburn) my home and start position is X0, Y400 (upper left). If I set the move steps to 100mm and move Y-100 when it gets there it resets back to X0, Y400. Lightburn will show the position as X0, Y300 because it’s calculating the last move into the start position.
Now if I move along Y the same direction it will show X0, Y300.
If I move the opposite direction it will say X0, Y500.
If I move along X it will say X100, Y400.
If I move the opposite along X it will say X-100, Y400.
No matter where the head is in the bed, if I hit Get Position it will tell me X0, Y400 so it is indeed resetting after each move.
When using the rotary with the IR module (which requires using the crosshair) it’s not aligning with the laser start position. When I set the crosshair exactly where I need it to be and start the burn the gantry doesn’t move to account for the crosshair offset. What’s more strange is once the burn is done the gantry moves back as if accounting for the crosshair offset. This means when I start a burn it starts burning on the edge tapering off the side of, let’s say, a cup rather than the gantry moving up and over to put the laser where the crosshair was located. Then when it finishes burn the edge of the cylinder the gantry moves the head’s crosshair to the location where it was incorrectly engraving.
I don’t know who I need to reach out to in order to get this addressed. I’ve attached the IR to the SM2 and it too has some really weird quirks itself like asking to calibrate but then when running a job that calibration meant nothing. You have to manually move the head to the job origin in order for it to burn the correct location. This is without using A>B which I also had trouble with. When I first got the IR and tested it on the SM2, I used their make something template and used the A>B and it worked perfect the first time. Now that I put it back on the SM2 to test a custom job and tried to A>B the work area the head took off and ended up in a completely wrong location. That’s when I had to find out I had to manually set the job origin location.
I feel like I’m either doing something completely wrong (I highly doubt but it’s not impossible) or the firmware for the IR is still in a beta 1.0 state. If it wasn’t truly ironed out before release then please work with me and I will do whatever I need to get this thing ready for primetime. Snapmaker machines are great but the pre-order and first run experience needs more polishing…critical feedback.
I’m afraid people are selling their machines and choosing to go with the multitude of other machines out there now that are unfortunately innovating significantly more in a shorter time.
Why are these two different and which one is actually correct? The numbers are so close and the crosshair lens is so large I cannot just measure it to find out unless I do it while the laser is installed, powered on and the crosshair is turned on.
Yes this is in Lightburn and there is a place where the start and end gcode can be edited. I too noticed this in the end code. I looked into the IBDEV files Snapmaker provided for both the 40w and 2wIR and the end code was only set in the newest 2wIR IBDEV file. I thought about taking it out but I’m going to wait for support to take a look at it. Just looking through the IBDEV files the most recent 2wIR files don’t really look…right? Not sure what the correct word would be. It doesn’t really compare to the other IBDEV files they’ve made. There shouldn’t be much difference between the modules.
Just so you know, I have an updated guide. It was specifically for the IR, but it works flawlessly with the 40W as well, and the other lasers as long as you get your initial focus height correct.
That’s a really good tutorial. Is there anything different than what is found in the IBDEV files? You can use Notepad++ to see what the settings are in the IBDEVs. This also lets you set your own macros in the console tab
Or you can simply right click the macro button in Lightburn and it opens a window for customization.
I’ve always built my own profiles before they began offering any. The main difference is they keep changing the profile type, they did “snapmaker” then “GRBL” and now apparently “Marlin” (technically the snapmaker system in Marlin except the Ray, which is grbl). I always used grbl, which removes a lot of fluff and works fine, it just breaks the control buttons in Lightburn (as they’re using grbl specific $ commands which marlin doesn’t understand) I don’t use those buttons, however.
Indeed, it would be amazing if they gave the full M-xxxx list to us with what description of what each one does. From what I understand GBRL has a ton of “extra” code that can be issued proprietary and it seem Snapmaker is using a lot of it.
It was specifically for the IR, but it works flawlessly with the 40W as well, and the other lasers as long as you get your initial focus height correct.
