That log is very interesting, and it shows that your GRBL can be connected to, and is in an ‘IDLE’ state after boot which is good.
I’m thinking it might be some kind of timing/buffer issue where MillMage is getting confused by the output that your GRBL sends on startup and could be conflating that with the ‘OK’ response it is expecting from its ‘G0’ prompt.
If you could please collect a debug log from MillMage then it should be more obvious and I can pass this on to the dev team:
Close GRBL Diagnostic web app.
Restart the CNC machine for good measure.
In MillMage, go to Help > Enable Debug Log
Right-click the ‘Devices’ button to force a reconnection attempt
After about 5 seconds go to Help menu and select ‘Enable Debug Log’ again (to stop the logging).
Look in your Documents folder for “MillMageLog.txt” and attach that here.
Something else worth a try is to click the ‘Stop’ button, which might kick MillMage out of the ‘Busy’ state.
You may also want to check your Z limit switch which reports as activated, and may be an issue, but probably is unrelated.
Please delete the existing MillMageLog.txt from your documents folder and try again with settings just as above, and attach the new MillMageLog.txt, thanks.
I can see activity in that MillMage debug log that shows the last connection was successful…did you notice any difference to the connection in MillMage?
Nicholas, I definitely noticed a difference, I am now able to jog the tool. What I noticed now is I can preview the work, I can frame it, but when I try to cut the design, the spindle shuts off.
But otherwise, that seemed to work!!!
Thank you
