ModuloFS

> There hasn't been any "design" comments since @chennes said it was an intentional design decision. Every time i use the spreadsheet I am dismayed to see this bizarre behavior...

Unfortunately i am not a software developer and i am not so deeply involved in this project. I changed the way to connect with fluidNC now. I removed the transistors...

It appears on build in tools as you can see on tool 6 and 7 as well as on self made ones like the tool 16. I have to say...

Ok, if i change QtCore.QSize(200, 235) in the shapewidget.py to QtCore.QSize(400, 470) the icon in the tools parameter editor window gets bigger but the dpi resoluion stays roughly the same....

Resolution looks a little better but not perfect sharp. 

In gSenders jogging presets. The maximum speed in the FluidNC config is 5000 mm/min. Whats the root cause of your question? These interruptions happens, even if i send the jogging...

The host machine is Windows 11 or Ubuntu 22.10 at booth i have the same probelm. If i connect, it does not matter if the host is Windows or Linux,...

Just tried movements with G0 and G1 commands with gSender, there are the same interruptions in movement. So this problem is not direct related only to jogging but to basically...

Is this explaining the motion interruptions? And why i have the same issue with the Candle gcode sender? It seems i am not the only one with this problem. How...

No with FluidTerm everything works perfectly. It makes me wonder because with version 3.5.1. i had no such issue.