I am getting an odd and consistent gcode error. The file is very simple, just some simple cuts and markings. I have rebuilt the lightwave project and the illustrator assets multiple times to ensure it is not related to some funky vectors. The vector images look perfect in illustrator and they look perfect in lightwave. Lightwave’s preview looks perfect, but the cut and a web based gcode simulator output consistently different results from what I am seeing in lightwave or illustrator. anybody have an idea what is going on here? I am running the latest version of lightwave 9.16…
After a ton of gcode testing I have found the problem creeps in after I reduce the lasers speed setting below 7mm/sec. I decided to install an earlier version of lightburn 9.14 and the problem cleared up. Is this a bug?
Thank you for reporting this and continuing to track down what you are observing.
You have posted pictures, circling something but I do not understand what you are saying below.
Can you please re-phrase the issue you are noticing. It is not clear from what you have provided.
Ok, I’ll try to rephrase this.
To give you a better understanding, you are looking at a template for a guitar neck. The line down the middle is a centre line, and it is lightly tapered from left to right. These are simple vectors output from illustrator. You can see the top two images are just what I describe. This is also what output gcode looks like this when the speed is is above 7mm/sec. when I drop the speed below 7mm/sec then output gcode changes to the bottom image. You will see that the centre line is no longer centred. The bottom taper has flattened, meaning that the far left edge is no longer meeting the bottom edge properly. The top taper has also flattened out adding extra length to the far right edge which causing the centre line to no longer be centred. This exact same error occurs whether I rebuild the scene from scratch or use new vectors from illustrator. The only factor I can nail it down to is the laser speed setting. This error occurs in both v9.16 and v9.15, but does not occur in v9.14 . I hope that helps. Don’t hesitate to ask if you have more questions or need a scene file.
I know what this is - It’s been fixed already for the next release, and is related to a new feature that went in with the last one. In the device settings, turn off “Reduce Smoothieware pause delay”
When the next release comes out you can turn that back on, but that’s what is causing the error. We’re subdividing geometry into small pieces based on the speed you move, and if the pieces get really small, we weren’t accounting for rounding errors, and it was possible for very long, slow moves to basically vanish.
2 Likes
Interesting, that would account for some of the other little buggy things I have seen lately. Thanks for the explanation.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.