I recently had my laptop die on me so I’m now using another PC. When I setup Lightburn and and use the move controls the positioning isn’t registering or something, not really sure. I have Home at X=0 Y=400. If I jog it to any direction it will register that distance one time then any additional jogs will not. If I jog the other direction the same thing happens except it resets the other axis. It appears to be reseting the position to X=0 Y=400 on every move. Nothing I have tried works. I’ve tried reloading the machine lbdev and reflashing the firmware.
Any help would be appreciated.
Edit 7/18/2024
This is printing in the console and should not be. I don’t know how to keep it from resetting sys position and offset coodinates.
Starting stream
[I][PLAT]Program End
Stream completed in 0:01
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
[I][PLAT]max rpm: 0
[I][PLAT]max rpm: 1000
<Idle|WPos:0.000,400.000,0.000,0.000|FS:0,0|WCO:0.000,-400.000,0.000,0.000|SD:8.44,boundary.nc>
[I][PLAT]Set coordoffset: 0.000, 400.000
[I][PLAT]reset coordoffset
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]reset coordoffset
I appreciate the response but in my case I didn’t have the opportunity to export anything. I was only smart enough to use NAS for backing up my project files which did backup laser setting for each project but that’s all I had. Anything on the local drive where Lightburn autosaves is toast.
I setup Lightburn before just fine and without any issues once I had the Y -400 set but things didn’t go as smoothly this time which this new issue I hadn’t encountered or found anyone else discuss before.
Thanks for your response. Yes, those are the ones I used when reloading all my files. I’ve deleted all my devices and reloaded them with a new download of this file. I also reflashed the Snapmaker Ray firmware just to be sure. It does appear to be a disconnect between the machine and the Lightburn software. I used Snapmaker’s software Luban just to see if it worked properly and it does so that isolated Lightburn software and the machine being the issue.