cncdrive wrote:The laser plugin is not making g-code and will not make g-code because it would be a large waste of memory.
Now one pixel is stored a single byte and if a g-code was generated then usually one pixel would take one line of g-code in avarage.
It might not sound a problem with todays's computer memory sizes, but in reality it can with very large images.
Of course. OTOH, What does happen between UCCNC and the UC400ETH is a bit of a "black box" protocol-wise. From just looking at network diagnostics, a substantial amount of traffic is passed during an engrave, which lead me to focus on that angle as a potential source of the problem.
cncdrive wrote:What do you mean "temporary" set backlash? Please explain how you want to do that and maybe my collegue can help you to write a macro for it.
Recall my
previous post. To get crisp engraves, I have to add 0.02" backlash to the x-axis, even though my machine uses GT2 belts and has none. If I forget to clear the backlash from the x-axis config after the engrave, my next cut gets ruined. Being able to set a temporary backlash during the engrave would take an error-prone step out of my workflow.
Cheers.