Advanced Search

Those TB6600 modules sure seem like an awkward form factor, especially given you need 3 or 4 or 5 of 'em.

Sorry but i can not help as stated above, but i can move this to QtPyVCP section where the masters of Probe Basic reside.




This is a Qtvcp screen so it's in the right place.

More things I learned today, about Grbl:

Say you start a jog, and realize you meant to go the other way, and select the other direction. In LinuxCNC, this Just Works. Using Grbl, first the errant jog has to finish, and only then the next queued jog is executed. Not terribly efficient.

If you try and start a jog that would take the axis too far, you get an error. To clear that error, you need to go to a different tab (I'm using UGS), clear it, then go back to the jogging tab. It may be that there's a way to have both displayed all the time, but even then, having to specifically clear an error from a jog that never happened, seems... difficult.

I'd only started using it recently in LinuxCNC, but I found out today that neither Grbl (not surprising) nor FluidNC (surprising) supports the R parameter to G10 L2/L20. R lets you specify rotation, which can be very handy in cases where it's easier to get your hold-down clamps set securely if you rotate the stock.