Don’t know why LB won’t move correctly, have been fighting this for two years. Thing is Open Builds runs my laser perfectly. LB is very inconsistent, won’t home correctly, won’t show correct laser position, etc. Sometimes works with jog, same with constant move, only will only move so
far. Using a Keystudio V.1 controller, have checked cables numerous times. It is NOT my system! I have several cnc and laser programs and everything works correctly but LB. I wind up
designing in LB, saving the nc file and burning with OB. Something in your USB algorithm is not working.
I don’t know exactly how Lightburn interfaces with the USB port. Most likely with standard system calls for I/O.
Home is a function of the controller in your machine. Lightburn only sends the gcode to initiate the operation.
How did you set up the Device? ‘Edit → Device Settings’
Can you cut/paste your boot message from the ‘console’ tab in the cut/layer window?
Exact same pb here. Have to export gcode file and burn it with LaserGrbl… Most of my engraving files don’t work with Lightburn anymore, i’ve to use LaserGRBL. 0 problem with the exact same files with Lasergrbl, so i’m thinking of USB parsing error too with LightBurn.
This is highly unusual that one would work fine and the other not. LightBurn doesn’t directly manage the USB connection. It only thinks in serial communication.
Can you take screenshot of LightBurn Device Settings?
Also a screenshot from LaserGRBL Settings->Protocol tab?
I’m having a similar problem - I’m hooked up with a ethernet cable and it has worked fine on my old computer and Win 7 and earlier Lightburn. Changed to a Win 10 computer with the latest Lightburn and it shows the laser (Ruida) is ‘ready’ but nothing happens.
Hey Bob,
Can you connect LightBurn up to your engraver, open the Console window and Copy the error messages and paste them into a reply here? I’m looking at OpenBuilds for a project and I’d like to know what i’m up against.
Is this your controller?
https://wiki.keyestudio.com/KS0288_Keyestudio_CNC_GRBL
Which Version of GRBL is your controller running, 0.9, 1.0, 1.1?
Just trying to lock down some concepts in my head. Thanks!
You may be having a substantially different problem. USB and Ethernet are different enough that I’d have to recommend that you start a thread in the Ruida group. The Ruida / ethernet folks are fantastic - they’ll get you set up.
That’s the controller. GRBL V1.1H
Boot and GRBL settings$$
$0=10
$1=25
$2=0
$3=4
$4=0
$5=0
$6=0
$10=1
$11=0.010
$12=0.002
$13=0
$20=0
$21=1
$22=1
$23=0
$24=50.000
$25=635.000
$26=250
$27=10.000
$30=1000
$31=0
$32=1
$100=100.000
$101=325.000
$102=366.670
$110=800.000
$111=800.000
$112=800.000
$120=50.000
$121=50.000
$122=50.000
$130=600.000
$131=1000.000
$132=200.000
ok
Waiting for connection…
Waiting for connection…
Grbl 1.1h [’$’ for help]
[MSG:’$H’|’$X’ to unlock]
error:9
G-code locked out during alarm or jog state.
[MSG:Caution: Unlocked]
ok
[VER:1.1h.20190825:CUSTOM]
[OPT:V,15,128]
Target buffer size found
ok
Error 9 is super helpful - and solidly not USB related.
It looks like OpenBuilds has already seen this on more than one occasion.
If this resolves the issue please mark it as solved.
Good Luck!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.