Console

The Console panel is the raw G-code window. You can send commands directly to the controller and see every line it returns, with timestamps and direction indicators.

For most workflows you do not need the Console. Use it when:

• You want to read or write GRBL $ settings directly.
• You are debugging a connection issue and need to see what the machine says.
• You are testing a custom macro before binding it in the Macros panel.

Opening it

• Default dock zone: upper-right
• Visible by default: yes
• Hotkey: no default

What you see

Two regions:

Log output

A read-only scrolling area in monospace. Each entry has:

• Timestamp (HH:MM:SS).
• Direction indicator: → for commands you sent, ← for responses from the machine.
• The line content.

Lines that match error: or alarm: (case-insensitive) display in red.

The log auto-scrolls to the newest entry. The pane has a fixed height; scroll up to see history.

Input

A single-line text field with placeholder G-code... plus two buttons:

• Send: submits the typed command.
• Clear: clears the log display (the command history is preserved).

What you can do

Send a command

1. Type a G-code or GRBL command (e.g. $$, G0 X10 Y10, M3 S100).
2. Press Enter, or click Send.

The command appears in the log with the → indicator, and the machine's response (if any) appears with ←.

Walk through previous commands

• Up arrow in the input field, moves backward through your command history.
• Down arrow: moves forward.

History persists across panel close / re-open as long as the app is running.

Clear the log

Click Clear. The log displays clear; the underlying command history (for up-arrow recall) is untouched.

Read GRBL settings

Send $$. The machine dumps every $ setting with its current value. Each is one ← line.

Set a GRBL setting

Send $3=2 (or whatever the change). The machine responds with ok or an error.

Beware: GRBL settings persist in the controller's EEPROM. Always know what a setting does before changing it. See the GRBL settings reference.

Test a macro before binding it

Type the sequence of commands in the input one at a time. When you have something that works, save it as a macro in the Macros panel.

Behavior worth knowing

• The error/alarm regex catches anything starting with error: or alarm: (case-insensitive). It is a visual hint, not an interpretation. The machine still expects you to read the actual code.
• Sending commands during a running job can confuse the streamer. Wait until the job is paused or finished.
• The Console does not enforce GRBL syntax. Whatever you type goes to the machine verbatim.
• Long-running commands (homing, jogging large distances) tie up the channel until they complete. The Send button does not block but the response may take time.

Related

• Laser Control: machine connection, job controls
• Macros: bind sequences of commands to a hotkey
• GRBL essentials: concepts
• Dollar settings reference: every $ setting
• GRBL error codes: what error:N means