Error 22 (feedrate not set)

Hi, so I’m getting a message in the console that my feedrate has not been set/defined. (error 22). I haven’t the slightest idea how to fix this, and can’t find an answer. My machine uses GRBL, and I’m on a Mac. Here are my current settings:

$0=5.0

$1=100

$2=0

$3=2

$4=7

$5=11

$7=0

$10=2047

$11=0.050

$12=0.002

$13=0

$14=0

$15=3

$16=0

$17=4

$18=0

$20=1

$21=1

$22=1

$23=3

$24=1000.0

$25=3000.0

$26=100

$27=1.000

$28=0.100

$29=0.0

$30=1000.000

$31=0.000

$32=1

$33=2000.0

$34=0.0

$35=0.0

$36=100.0

$37=0

$39=1

$40=1

$41=1

$42=1

$43=1

$44=3

$45=0

$46=0

$47=0

$56=1.0

$57=1800.0

$58=95.0

$59=6000.0

$60=0

$61=1

$62=0

$63=3

$64=0

$100=100.000

$101=100.000

$102=100.000

$103=80.000

$110=6160.000

$111=3030.000

$112=600.000

$113=5040.000

$120=500.000

$121=500.000

$122=200.000

$123=500.000

$130=100.000

$131=100.000

$132=100.000

$133=100.000

$160=0.000

$161=0.000

$162=0.000

$163=0.000

$180=3030.000

$181=2121.000

$182=600.000

$183=5040.000

$270=921600

$271=921600

$272=921600

$273=921600

$341=0

$342=30.0

$343=30.0

$344=180.0

$345=200.0

$376=0

$384=0

$392=5.0

$393=3.0

$600=0

$601=5

$602=0

$603=5.0

$604=6.0

$605=1

$606=1

$607=0

$608=1

$609=10.000

$610=0

$611=0

$613=37

$614=0

$617=0

$618=0

$622=63

$623=0,0.000000,0.000000

If the Jog Continous switch is on, it will forget the setting for Speed in the Move window. The latest release v2.1.01 has that fixed.

That’s typically due to picking a different GRBL dialect than the one the machine controller understands.

Unless you know differently, choose GRBL as the Device Type:

If that doesn’t solve it, upload a screenshot of the Devices window so we can see the configuration:

I haven’t changed anything. This happened right after the last .01 update. Even when framing, the speed is choked. Thank you to both of you for the help, btw.

Here is my Device screenshot:

Updating LightBurn definitely counts as “changing something”. :grin:

@JohnJohn: Looks like this one’s for your crew.

Okay, true, funny guy, lol. After resetting to the factory default and testing my laser from its control panel, I have determined that the file I was trying to cut had somehow become corrupted. In short, I think the problem is fixed. Thanks so much!