-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jerky motion due to too many instructions #659
Comments
Edit: One way to reduce the resolution of raster cuts is to increase the beam size, since the cut is rendered into a grid based on that.
You can also reduce the number of grayscale colors; there are options for this in the job settings; it defaults to 256, lowering this will produce fewer intensity value changes. If you are dithering, and using a diode laser, make sure you have the 'burn white' option enabled in the machine settings tab. |
Thanks for your reply. Sadly this problem occurs while rastering and (please correct me if I'm wrong) there is no "segment" option there. |
Sorry of the initial mis-read, I've fixed the original answer |
Hi,
I am dealing with an issue that I come across at different forums. When raster engraving (or raster merge) the laser becomes very jerky at higher speed (200 mm/s).
After a bit of a headache I tried generating gcode for the same image with LaserGRBL and that gcode ran fine with the same speeds and accels. After I compared the gcodes I came to the conlusion that LaserWeb is "too good" and for the M4 dynamic power it generates too many steps of the power. To simplify-where LaserGRBL steps down the S value by "1", LaserWeb steps by "0.1".
Is there any way to reduce the "resolution" of the dynamic power mode?
Thanks
Tomas
The text was updated successfully, but these errors were encountered: