Error 23 when sending custom G-code (M3011) to LaserPecker 4 via LightBurn, despite using official .lbdev file

LightBurn Hardware Compatibility GRBL
, , ,
1

Hello,

I am experiencing a critical error when trying to switch the laser source on my LaserPecker 4 using LightBurn.

  1. Software: LightBurn (latest version)
  2. Device: LaserPecker 4 (LP4)
  3. Configuration: I have installed the device profile using the .lbdev configuration file downloaded directly from your official website link.
  4. Problem: When I send the custom G-code command M3011 (to select the 1064nm fiber laser) directly in the LightBurn Console, the job immediately halts.
  5. Error Message: The console displays:
    error:23
    G-code command in block requires an integer value.
    On or near line 1:

This error suggests that the LP4’s GRBL firmware is not recognizing M3011 as a valid command,
or is incorrectly parsing it as a command that requires an integer parameter, leading to the error 23.

Please provide the correct and current G-code command or syntax for switching to the 1064nm laser in LightBurn,
or advise on necessary firmware updates.

Thank you.

2

Hello everyone,

I previously posted about an issue using the custom G-code M3011 to switch to the 1064nm fiber laser on my LaserPecker 4 (LP4) via LightBurn. The machine kept returning “error:23 - G-code command in block requires an integer value,” and the laser would default to 450nm even after manual selection.

The Issue: The LP4 firmware was not correctly interpreting the M3011 custom G-code command sent by LightBurn.

** The Solution:**

I received a tip and updated my LaserPecker 4 firmware to the latest version (V6.5.6).
After updating the firmware, the M3011 command (and likely other custom M30XX commands) is now correctly recognized and accepted by the machine. The 1064nm laser now switches properly when M3011 is sent in the console or placed in the layer start G-code.

If you are experiencing similar M3011 or Error 23 issues with your LP4 and LightBurn, please check and update your LP4 firmware first.

Thanks for all your input! I hope this helps others facing the same compatibility problem.

1 Like