JohnJohn
May 30, 2022, 7:21pm
2
In LightBurn open the Console window and type the following:
Those commands come from here:
# 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.)
Once connected
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:
```
show original
I’d like to try to see what’s going on before we unlock or reset.
This may also be worth review:
Folks,
When asking for support for LightBurn via this forum, email or anywhere else, please keep the following tips in mind for the fastest and most helpful answers.
controller does it have , and what firmware it is running?
Are you running the latest version of LightBurn?
Is the issue new, or has it happened before? What kind of computer is it, and what Operating System is it running?
1 Like
