So I noticed something with Laserweb4’s Raster engraving feature. This is the same .png file with the same power settings, but with very different gcode outputs. I will attach the gcode and photos of my settings below. Any ideas?
Here are the two gcode files from LW3 and LW4 along with the source png image, and screenshots of my settings in both versions of Laserweb. https://drive.google.com/open?id=0B8ZXvH-aGzn9UXg0QmRQdVRyc1E
Yep, found the same glitches today. It depends on the selected features like “trim pixels”, “join pixels” or “burn white”.
@Sebastien_Mischler @Todd_Fleming Are you already aware of that?
First time I’ve seen that issue. What settings does it take to reproduce?
One problem I found is that the raster code creates a failure after every y move (S value + \n before X move):
G1 X0.05 Y0.05 S0.0000
S0.8131
X0.20
X0.30 S0.7987
I forgot about that lone S value. I used a sed script to strip it out when testing grbl-lpc. +Peter van der Walt said it’s there to aid LW3’s gcode preview.
I actually wish I new what all those settings “trim pixels, burn white, join pixels, verbose gcode, etc” actually meant. Does anyone have a write-up if what each of those settings does?
I think someone summarized those settings in a reply to a G+ post asking what they are.
@Ryan_Branch See this posting for some of the info on settings. Make sure you load all the comments to start from the top. https://plus.google.com/105504973000570609199/posts/S9N9i5TCtK3
@Todd_Fleming I posted screenshots of my settings in that link. Basically I used the default settings (trimp pixels,burn white, etc) but I think I had speed set to 80 mm/s with 20% power and a 0.1mm beam diameter, single pass. Does anyone have any ideas? I couldn’t tell if someone was working on a fix or anything. I really like LW4, so I hope we might be able to resolve this.
We probably need a volunteer to help with the rasterizer when Sebastian is busy.
I am strictly a hardware guy otherwise I would jump right in. 