Creality Laser Module Not Firing After Switch Back to Laser Cutting

LightBurn Hardware Compatibility
1

I have a pretty new Creality 5W Laser Module on my Creality Ender 3 S1 Plus. I had recently changed it back to a 3d printer, and I just reconnected it. To my surprise, the laser will not fire at all. I have tested voltage, pwn, and wiring connectivity. Does anyone know why my laser isn’t firing? Is it somehow just dead?

2

Can you type $$ or M503 In Lightburn Console Window and check your settings?

3

Here you go:

ok
M503
echo:  G21    ; Units in mm (mm)
echo:; Filament settings: Disabled
echo:  M200 S0 D1.75
echo:; Steps per unit:
echo: M92 X80.00 Y80.00 Z400.00 E424.90
echo:; Maximum feedrates (units/s):
echo:  M203 X500.00 Y500.00 Z10.00 E25.00
echo:; Maximum Acceleration (units/s2):
echo:  M201 X5000.00 Y5000.00 Z100.00 E5000.00
echo:; Acceleration (units/s2): P<print_accel> R<retract_accel> T<travel_accel>
echo:  M204 P500.00 R500.00 T500.00
echo:; Advanced: B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> X<max_x_jerk> Y<max_y_jerk> Z<max_z_jerk> E<max_e_jerk>
echo:  M205 B20000.00 S0.00 T0.00 X15.00 Y15.00 Z0.40 E5.00
echo:; Home offset:
echo:  M206 X0.00 Y0.00 Z0.00
echo:; Auto Bed Leveling:
echo:  M420 S0 Z10.00
echo:; Material heatup parameters:
echo:  M145 S0 H200.00 B60.00 F255
echo:  M145 S1 H240.00 B100.00 F255
echo:; PID settings:
echo:  M301 P14.49 I0.96 D54.59
echo:  M304 P54.86 I10.06 D199.38
echo:; Power-Loss Recovery:
echo:  M413 S1
echo:; Z-Probe Offset (mm):
echo:  M851 X-31.80 Y-40.50 Z0.00
Input Shaping:
  M593 X F0.00 D0.15
  M593 Y F0.00 D0.15
echo:; Filament load/unload lengths:
echo:  M603 L0.00 U100.00
echo:; Filament runout sensor:
echo:  M412 S1
echo:; UI Language:
echo:  M414 S0
ok
4

Does anybody have any ideas on what is going on?

5

Before we dig deeper could you try with Creality Print?

6

Sorry I forgot about this. Basically my motherboard was not sending the signal, and it also was not spinning the hotend fan. I reached out to Creality and they sent me a new motherboard. I still don’t know what caused this, but I’m using the GRBL controller that it came with now so it doesn’t happen again.

1 Like