I read to use $33=750 it said ok but still is not working. How can I unlock the g code?
$33 is PWM frequency and generally should never be below 1KHz. (1000). Typical is 5KHz to 20KHz. Never seeing one run at 750Hz, though not that far from 1KHz. Safe settings are 5KHz (5000).
I do not believe it has anything to do with Error 9, but who knows!
You can unlock it with “$X” but your homing has failed. You need to fix that or if you are comfortable to run without homing - disable it: “$21=0”.
This file has been truncated.
# Grbl v1.1 Commands
In general, Grbl assumes all characters and streaming data sent to it is g-code and will parse and try to execute it as soon as it can. However, Grbl also has two separate system command types that are outside of the normal g-code streaming. One system command type is streamed to Grbl like g-code, but starts with a `$` character to tell Grbl it's not g-code. The other is composed of a special set of characters that will immediately command Grbl to do a task in real-time. It's not part of the g-code stream. Grbl's system commands do things like control machine state, report saved parameters or what Grbl is doing, save or print machine settings, run a homing cycle, or make the machine move faster or slower than programmed. This document describes these "internal" system Grbl commands, what they do, how they work, and how to use them.
## Getting Started
First, connect to Grbl using the serial terminal of your choice.
Set the baud rate to **115200** as 8-N-1 (8-bits, no parity, and 1-stop bit.)
you should get the Grbl-prompt, which looks like this:
Grbl 1.1e ['$' for help]
Type $ and press enter to have Grbl print a help message. You should not see any local echo of the $ and enter. Grbl should respond with:
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.