My Altmill was working fine yesterday, today it isn’t working at all.
When I try to run G-code from Vectric Pro, it goes into hold mode and gives me a series of Error 38 messages. If I click Start again, gSender acts as though it is carving while nothing happens. I can home the machine, activate the spindle, and move it about normally.
Things I have done:
Made sure Vectric is using the correct grblHAL. I even deleted it and downloaded it again.
Tried running a file that was working fine yesterday- same result, implying this is a machine issue.
Reset gsender to factory settings and reinstalled my spindle and touchplate. No change in results.
Of course, several shutdown/reboot cycles.
Ensured all bits and selections were correct in Vcarve.
Tried not to invent new words or compare my shiny new CNC to the FoxAlien brick I started with.
Any thoughts, remedies, or new swear words would be appreciated.
Nope. I have a TLS- but not installed. I would put it off to some kind of a vCarve issue in generating the gcode, but it does the same thing with a old file that worked just fine and hasn’t been changed.
Error 38 is a tool out of range error - do you have an M6 in your gcode with a T command that’s over 32 because that’s not allowed - it has to be in the 1-32 range if there is a tool table compiled in like our recent grblHAL firmware releases (or 1-N where N is the size of the compiled tool table).
I was confused by the fact that it cropped up in a file that I had already downloaded and successfully run. I thought it might be a gcode corruption of some kind, so my admittedly low-tech way of testing was to try to run a file that was unchanged and previously worked. When I did that, it produced the same error. I don’t know if that proves anything, but it seemed like a reasonable test to me.