Hi, I’m attempting to include two dxf files in a laser cut+engrave project using Luban. Everything looks nice and i can append toolpaths to both files, however, when I generate the gcode, the path for engraving has created nothing- leaving only the cut path as the result… Any ideas on what can I do to improve this?
Please, what firmware and Luban version?
Luban 4.9.1
And the firmware off the SnapMaker is what?
Its 2.5.17 - but i dont see how thats relevant - the exported Gcode itself doesnt contain any information regarding the dxf file i wanted to engrave so I never got to even put it on the machine
1 Like
How that GCode interfaces with changed Binary code for the system perameters doesn’t have any relevance? Are you mental? Maybe you should actually learn Gcode
what I meant is that the firmware of the machine itself shouldnt matter as the gCode generated by Luban doesnt contain any information regarding the engraving coordinates (Like it does for the cutting part). (I’m using laser to both engrave and cut). I completely agree that the software version for the Luban is relevant.
I might have misunderstood something here or formulate the issue poorly, if so - thank you for a very clarifying answer.
Actually, there seems to be some undocumented new additions in gcode spit out by Luban. While I haven’t checked on the CNC, I noted a few new commands I’m unaware what they are for laser.
M2000 W1 P100
M2000 W2 P100
M3 S0
M9
M2000 L23 P1
These three M2000s specifically.
Snapmaker has made a few custom gcode commands and if any are new, your firmware will have to be up to date for the machine to understand what they are. Especially with the latest introduction of inline control for the laser, there’s been a lot of trouble with people not being on the latest firmware and it causing issue. Also gcode is and of itself… coordinates, that’s what 99% of it is. I assume you mean it didn’t actually output the path for the other DXF though, that would be a problem listed below.
I think the main issue you’re facing is actually Luban not supporting DXF standards properly, I know some SVG standards it fails with as well. If there’s even a tiiiiiny gap making a line not closed, Luban will just chuck it out and not do a fill.
1 Like
Good find,
I’ve submitted a ticket, asking to update the g-code reference and explain what the commands mean.
Doubt they will update the g-code reference, last ticket was “appreciated” but
Never got into the current reference.
Thanks for reaching out to Snapmaker.
M2000 W1 P100 Control of the enclosure light
M2000 W2 P100 Controls the enclosure fan
M3 S0 Setting the laser power to 0
M9 turn off the air pump（RAY laser use）
M2000 L23 P1 Both lasers are on
Both lasers are on 
1 Like
So they’re not even keeping to their own standards, or trying to centralize. The enclosure controls were under M1010.
M1010 - Enclosure control
control code
S0: Disabled door opening trigger
S1: Enabled door opening trigger
S3: Set light power. M1010 S3 P[0 - 100]
S4: Set fan power. M1010 S4 P[0 - 100]
S12: Refresh door Status
https://snapmaker.github.io/Documentation/gcode/M1010
They need to update their documentation badly.
1 Like