You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This sentence in the README.md could be the clue: "I found out that at commands where the head has to travel long distances it makes more sense to wait 100ms until the next one is sent to avoid errors."
So I would guess that these 100ms are not enough, maybe one needs to calculate the time based on how far the head moves or so. Would be helpful to look at how the original software reacts - how long does it wait after the ACK before sending the next command?
Yeah thats a good point. In my tests and test images (also for empty lines), 100ms was good working delay time. I think this is calculated per line basis. Maybe a factor for the waittime is the travelspeed of the head...
This seems to aaaalmost want to work with the K6.
This link implies that it should work:
https://www.mariolukas.de/better-software-for-k3-k5-and-k6-laser-engraver/
But all the comments are talking about an issue in VisiCut that I also get.
Related issue here: t-oster/LibLaserCut#170
I'm using WSL / Ubuntu on Windows.
The text was updated successfully, but these errors were encountered: