Hi, After cutting a whole airplane (56 parts) without a hitch, GRBL has suddenly started throwing up an error at random times. This is the error. I thought it might have been notifications from Dropbox, or some other web app, so I turned off WiFi. Same result. So I rebooted GRBL. Still the same result. Has anyone else experienced these seemingly random GRBL errors? Duncan
Error 9 is a lockout from a prior alarm. Its merely the symptom of something that happened earlier. Pay note next time it happens to look for the Alarm pop up, and scroll back in the log. See what the alarm was in the first place, that put it into Alarm mode, which is why its now locked out and not accepting gcode anymore (until alarm is cleared) Find the root cause that causes the Alarm Most likely just EMI based false limit: docs:blackbox:faq-emi [OpenBuilds Documentation]
Yes, the Serial Terminal has a log of all the major events (last 200 lines) Many things can make Grbl go into Alarm state, but as mentioned above, EMI triggering false hard limits is the more popular reason: Others are:
