Continuing the discussion from Luban 4.9.0 Laser no longer works:
Actually using Luban 4.9.1 - with an A350 and 10W laser.
Vector engraving - does not turn off the laser on G0 moves. It does turn it off in dot filled engraving. Looking at the GCODE - in the dot filled engraving section, there is an M5 before each G0 move line and M3 after each G0 move. Manually edited the vector section to add the M5 and M3 commands and that worked.
Make sure to upgrade your machine to 1.17.17. Luban 4.9.1 changes how it does vector and line-filled engraving to do inline and requires the latest firmware.
2 Likes
Besides the problem with auto-update to 4.9.1 (I installed it manually instead), I found out, that you canāt set the diameter in 4-axis-CNC larger than 125. I understand that this is to prevent damage or something. But I was going to use an extension (2" - found on thingiverse) to carve a bigger model. In 4.8.x I was able to set the diameter higher than 125mm.
Now playing around with the given 125 I imported a model and then the width of it is restricted to 125mm, too - which is ridiculous since the width should be diameter (d) multiplied by Ļ which would be something around 392,7mm
Am I getting something wrong? And how can I set a bigger diameter for my model?
At one point I got a message in Luban āsomething went wrong. please restartā¦ā - I am not sure if it was regarding to the things mentioned above or accidentally, I canāt reproduce this message
Found the problemā¦ btw I am using the A350
I will not delete my first comment, in case someone else found this āproblemā. I wanted to start a laser job after my message and was wondering why I canāt set the workpiece bigger than 125x125 - Luban set my machine to āSnapmaker Originalā and did not ask for the machine settings at first start like in older versions.
The Problem with setting the modelās width is consisting - now it is restricted to 320mm (like the maximum width for 3-axis-models) - still this is wrong, since you need the width to be the circumference of your model. I found a workaround for this, too: you scale the model itself instead of typing the width in
1 Like