Successful run boundary but laser job initiation failure

Snapmaker Ray
1

I want to do a simple project on my Snapmaker Ray that uses the whole working area. Therefore, I want to cut some small test circles to test my cutting Settings, but I cannot get my job to start, the boundary runs without any problems (laser spot mode). I’m using Luban 4.13.0 on Linux and firmware 1.7.4. I want to cut the following design:

image
image1647×1108 31 KB

I might get the job to run using a different origin mode, but I need to work on the whole workpiece after all and the boundary runs correctly so I don’t get what’s wrong.

Looking into the machine logs, I find the following lines:

[I][MPSVC]start SD file: /ray.nc
[I][SNMKR]SYS STA pre: STARTING, req: PRINTING, now: PRINTING
[I][FMGR]Plat SD started!
[I][SNMKR]got header start
<Idle|WPos:0.000,0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000,0.000|SD:0.61,ray.nc>

[I][SNMKR]total file line: 134
[I][SNMKR]estimated time: 19s
[I][SNMKR]motor mode: 1
[I][MPSVC]last motor mode = 3, new motor mode = 1
[I][PLAT]reset sys pos and WCO because disabling motor
[I][PLAT]Reset during SD file at line: 26
[I][SNMKR]plat alarm: 3
[E][FMGR]Plat alarm in working, stopped!
[I][SNMKR]SYS STA pre: PRINTING, req: COMPLETED, now: COMPLETED
ALARM:3
[I][SNMKR]SYS STA pre: COMPLETED, req: IDLE, now: IDLE
[I][FMGR]set file mgr status, now: 7, new: 0
[I][FMGR]print done!

For my 3D printer background, the gcode looks completely fine. It would need to fail on the first few lines:

;Header Start
;header_type: laser
;tool_head: 40W Laser Module
;machine: Ray
;gcode_flavor: grbl
;renderMethod: line
;max_power: 1000
;file_total_lines: 134
;estimated_time(s): 19.448
;is_rotate: false
;diameter: 0
;max_x(mm): 559.999
;max_y(mm): 370
;max_z(mm): 0
;max_b(mm): 0
;min_x(mm): 540
;min_y(mm): 350
;min_b(mm): 0
;min_z(mm): 0
;work_speed(mm/minute): 400
;jog_speed(mm/minute): 12000
;power(%): 100
;work_size_x: 600
;work_size_y: 400
;origin: bottom-left
;motor_mode: 1
;Header End
;Snapmaker Luban 4.13.0
;Fri Sep 20 2024 20:41:16
; Laser multi-pass, pass 1 with Z = 0
; G-code for laser engraving
; Generated by Snapmaker Luban
; G-code START <<<
G90 
G21 
M2000 W1P100
M2000 W2P100
M3 S0
M8 
M2000 L23P1
G0 F12000
G1 F400
G0 X540Y360
G1 X540.193Y358.05S1000
G1 X540.762Y356.174
G1 X541.686Y354.445
G1 X542.929Y352.929
G1 X544.445Y351.686
G1 X546.174Y350.762
G1 X548.05Y350.193

Thanks for any help and suggestions!

2

Does your ray move if you start the gcode and didn’t light up?
I didn’t get your problem…

Do you laser from Luban (is it possible to only laser from SD-card?)?

Its possible to do troubleshoot:
https://wiki.snapmaker.com/en/Snapmaker_Luban/manual/ray_supported_gcode_references
View Error Code
The following command can be used to view the error code information defined in Ray.
$E

Any way, shoot a ticket at support and in the end let us know what your problem and solution was.
Support@snapmaker.com or https://snapmaker.formcrafts.com/support-ticket

3

The ray does not move at all if a start a job. However I think I found the problem: Luban sets an incorrect (in my opinion) motor_mode if the gcode is generated while Luban’s workspace is not connected in control mode (either disconnected or set to manual mode which is the default). I have filed a bug report here: Bug: Cannot start jobs with absolute positioning when using Snapmaker Ray and when not connected to the machine in the beginning. · Issue #2490 · Snapmaker/Luban · GitHub. Until that is resolved I have to connect Luban to my ray first, the set control mode and home and then I can generate gcode.

1 Like