Hi, I’m new here and I hope this is the right place for my question. I have a laser engraver and I use it to engrave wood. It has been some time since I last used it and just now I need to use it again. I have encountered something that I have not the last time that I used laserweb.
When I create an image with gimp, I can export it as png and then import it using laserweb which will then generate the g-code to engrave it. The problem is however, that a lot of g-code is generated in which the servos simply move but the laser does not do anything (“green lines”). I didn’t have this problem the last time when I used laserweb.
This is a lot of lines to cover before it even starts to laser the position that needs lasering. Why does this happen? Why would g-code even be generated when 2 or more paths following no laser activation are in the code? Is there a way to optimise this?
Well, after weeks of nothing and picking up the project again, I made a very interesting discovery. I am using the software in the browser (don’t ask, it had something to do with preference). My browser is a brave browser, a clone of chrome with built-in adblocker. Now here comes the interesting part. If I open up the same software in another browser (say firefox), I get different results. I really thought that the browser served as a frontend for the application itself but apparently, it also does the image processing in the browser. I don’t know the specifics but I think that image processing is browser dependent and I assume that the people at google have built-in optimisation for png’s that will randomly add pixels into the image when it is processed. Firefox does not do this (but it has other issues).
