Engrave glitches

[peteruithoven]

Presumably fixed related issues:

http://redmine.laoslaser.org/issues/47 There was a bug that caused bitmap data to be corrupted (last word of the data was not engraved). This is fixed in latest GIT commit of the firmware.

http://redmine.laoslaser.org/issues/58 Seems to be related to the incorrect handling of SVG sub-paths. At the end of each subpath a line is drawn to the start of the path. In Inkscape subpaths can be avoided by ungrouping all objects, convert all objects to paths and then split all paths.

Also see: http://redmine.laoslaser.org/boards/3/topics/680 http://redmine.laoslaser.org/boards/1/topics/747

A first step to debug this might be to check the simplecode files, this would be easier when it could be previewed, see: http://redmine.laoslaser.org/boards/3/topics/640

[thinkl33t]

I see these on my cutter too when engraving, it seems to happen when the laser head changes direction after decelerating.

[t-oster]

Can you re-check with VisiCut's "empty space per raster line" setting? It is in the LAOS driver's properties.

[peteruithoven]

@thinkl33t, that's a very interesting observation.

@t-oster you mean setting the "empty space per raster line" to zero? To check if that's the culprit?

[t-oster]

depends... if the glitches occur with the setting non-zero, I recommend testing with zero and vice versa ;)

[t-oster]

also setting it to a redicusluly high number could be used to check, if the glitches only occur at the very end of a line, so maybe you can set them 5cm away from your drawing.

[peteruithoven]

There might be progress: http://redmine.laoslaser.org/boards/1/topics/747?r=820#message-820

[peteruithoven]

Thanks to Hackerspace-FFM this issue was fixed, see: redmine.laoslaser.org/boards/1/topics/747?r=820