Yesterday we uploaded Carbide Motion 366 to fix reports of “Cutter Stopped Responding” messages. This should almost never happen “in real life” but it’s happening anyway. From what we can tell, it seems to be the operating system delaying some messages getting passsed around the program.
Build 366 has the following changes:
- Boosted priority of main thread when program starts
- Eliminated timeout for GRBL to reply to status requests
- Extended timeout for initial GRBL reply
As we begin to finish up support for GRBL 1.1, we’ve stopped putting a lot of effort into this branch of Carbide Motion so this might be the last release of Carbide Motion V3.