**Hey, @Dirk1000 I am no snapmaker staff **
1 Like
Only people who have traced out the circuits have figured out schematics, and I haven’t seen anyone do that for the laser driver.
Snapmaker has not provided any design schematics or boardviews.
Does anybody knows how much current can be delivered from the 24V path and how much by the 12V path? I ordered https://optlasers.com/plh3d-series/plh3d-2w and want to connect it directly. In question I would use 24V.
1 Like
Hi @brent113
A few cases about the discontinuous laser beam were reported recently. Mostly, it is because the user does not operate the Laser engraving module correctly and the Fabscreen UI does not give a clear and comprehensive guide. We should have made the guide of camera calibration more user-friendly.
-
As you can see in the picture below, can you control the laser engraving module via the touchscreen?
-
How about the 3D printing module and the CNC carving module? Can these two modules work normally?
Step 1:
I think it will take 7 days that the returning module will arrive at our office. You can try the manual focus and that would work.
Go as the following steps:
Settings --> Laser --> turn off “Auto-focus”
Step 2:
Please check the default laser height in the touchscreen. The path is “Settings --> Laser --> Adjust Laser Height”
The height should be 15 - 20mm, and you can adjust it by yourself and choose a better one.
Hello Edwin,
please watch this video. A brighter spot means less power, due to automatic of the phone camera, a smaller spot is higher power. All set to manual, only M3 P35 and M5 used. In the middel of a few characters you see the change from 2%-3% to 35% and burning.
https://www.md-it.de/Common/Snapmaker_Laser_Error.mp4
Hello Edwin,
is the black core common ground? Or does the PWM has a separate ground?
Thank you.
@Edwin please have a look at this video 
@Dirk1000 I’m pretty sure this was mentioned above so sorry if I’m repeating myself.
That’s the same effect I’ve noticed - it does not appear to be a failure of the laser module but instead an effect of engraving materials that take a bit of time to absorb enough laser energy to begin to engrave.
Add a delay at the start of each cut motion so the laser has time to darken the material and absorb laser energy better. I use 100ms, and that fixes that issue.
2 Likes
I did so, G4 P100 after every M3 P35. No change, sorry.
Could you figure out which speed would engrave properly?
Like laser full power, movement 100mm/min, 200mm/min, etc.
I guess the same thing like @brent113, that the material needs more time to absorb the laser light.
May you even try other material like wood or so to double check your code?
2 Likes
Not sure of this helps at all but on another forum that uses a laser running marlin, the same issue occurs at any speed above 25mm/s so I think its a marlin bug. You could try using grbl for laser, there is another thread on here about getting true grayscale where some one els ran grbl for lasering with good results.
1 Like
Hello,
I was wondering whether there has been a solution for the discontinuities in the laser cutting. Im trying to cut a map out of paper and have similar issues as Dirk described. Some parts cut out completely but some sections are just not cut (see picture) Used both 3000 mm/min / 600 mm/min speeds and 1500/400. Made no difference for me. It also didn”t matter wether controlled from the pc or send it via WiFi. Thanks.
Try much slower like a couple hundred as in like 400 mm/min or less
Oke, sry let me clarify. I used 1500 mm/min for moving to the next job and 400 mm/min for the actual cutting. Are you suggesting that I should also decrease the moving in between jobs?
How can I add this, I do not see this option in luban? Thanks
Hi,
Just received my SM 2.0 last week! This is my first post. I got to solve the issue adding G4 P500 after each M3 to the G code. Does not matter the speed at what you are working, it will force the laser to dwell for half a second every time it turns on. That was for cutting a white cardboard (160 g/m2) at 100% power. Other materials will need more/less time to reach cutting power.
I use Notepad++ to edit the code, but sure there are other ways. Just a find and replace did it for me.
Would be nice to have the possibility to add this direct from Luban, maybe a box under “Working Parameters” where you can add the dwell time. In that case, you can load the code direct to Workspace.
2 Likes
@Dirk1000 did you found any solution? I’m facing the same issue now =(