Breezytree
August 21, 2021, 10:58am
1
I’ve looked through the docs and forum but can’t find an answer. When I’m trying new substrates, I like to change the power and speed settings while running a job (under the Move menu) until I get the desired look. Lightburn doesn’t keep track of the changes / current output so I keep track myself. Question: is each increase / decrease cumulative? Eg, if I start at 1000mm per min and press the +10%, it would change to 1100. If I press it a second time, does it add another 100 (based on my original setting) or add 110 (based on the adjusted setting)? Sorry for the long question but I can’t seem to find the answer anywhere.
Rick
August 25, 2021, 8:38pm
2
# 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
We are simply sending the realtime commands to GRBL.
More here about this subject.
The way LightBurn works internally, when you click ‘Start’, the entire GCode for the job is created, put into a buffer in memory, and the system begins streaming it from that buffer. This means that you can close the file, open a different one, and start working on the next thing without affecting the current one.
Many of the things that you can change in LightBurn, like the dither settings, DPI, etc, make very drastic changes to the content of the GCode, so they would not be at all simple to …
system
September 24, 2021, 8:38pm
3
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.