Console shows communication with the controller and lets you send individual commands. Use the normal controls for routine homing, jogging, zeroing and job control.
Commands you send are outgoing requests; the following replies come from the controller. Keep the exact error and preceding messages when investigating a rejected command.
| Instructions |
Preview |
- Open Console. This shows the real-time communication with the controller. You can, for example, read the lines immediately before an alarm or error as well as the message itself.
- Replies can identify a rejected command or a failed operation. Compare them with the action that preceded the message.
|
 |
¶ 2. Send a command
| Instructions |
Preview |
- Enter one known command in the G-Code input and click Send. It is sent to the controller.
- Commands can change settings, move axes or start outputs. Check machine clearance and state before submitting.
- For routine homing, jogging, zeroing and job control, use the normal controls instead.
- Use the Up/Down arrow keys to recall previous commands; check the recalled text before sending.
|
 |
Enter $I and click Send. A connected grblHAL controller returns firmware/build identification; the exact text depends on its firmware. This query does not command movement or change settings.
Before clearing, copy useful messages or take a screenshot. For a support report, also use Export Troubleshooting Information.
| Instructions |
Preview |
- Clear Log clears visible terminal history.
- Capture useful messages before clearing them.
|
 |
Continue to Troubleshooting.