-
Notifications
You must be signed in to change notification settings - Fork 296
Configuring 0.99 Actions and Reports
<<< Back to Configuring Version 0.99 Main Page
These $configs invoke reports and functions
Command | Description | Notes |
---|---|---|
{sr:n} | get Status Report | SR also sets status report format in JSON mode |
{qr:n} | get Queue Report | |
{qf:_} | flush_planner_queue | Used with '!' feedhold for jogging, probes and other sequences. Usage: {qf:1} |
{md:n} | Disable motors | Unpower all motors |
{me:_} | Energize motors | Energize all motors with timeout in seconds |
{test:_} | Invoke self tests | $test=n for test number; $test returns help screen in text mode |
{defa:1} | reset to DEFAults | Reset to compiled default settings |
[{flash:1}] | Enter_FLASH_loader | WILL ERASE AND REFLASH BOARD. BE CAREFUL WITH THIS |
^x | Reset g2core | cntl+x restarts g2core same as hardware rest button |
[{help:_}] | Show help screen | Show system help screen; $h also works |
Note: Status report parameters is settable in JSON only - see JSON mode for details
These commands cause various actions, and are not technically "settings".
Returns a status report or set the contents of a status report (JSON only). Identical to ? command. See Status Reports for details.
Manually request a queue report. See $QV for details.
Removes all Gcode blocks remaining in the planner queue. This is useful to clear the buffer after a feedhold to create homing, jogging, probes and other cycles.
Unpower all motors. See Power Management
Energizes all non-disabled motors. Motors will time out according to their power management a mode and timeout value. See Power Management
Execute $test
to get a listing of available tests. Run $test=N
, where N is the test number.
g2core comes with a set of defaults pre-programmed to a specific machine profile. The default profile is set for a relatively slow screw machine such as the Zen Toolworks 7x12. Other default profiles are settable at compile time by including the right settings_XXXXXX.h file. If you are having trouble with your settings and want to revert to the default settings enter: $defa=1
WARNING This will revert all settings to defaults. Do a screencap of the $$ dump if you want to refer back to the current settings
Getting Started Pages
- Home
- What is g2core?
- Who uses g2core?
- Jerk-Controlled Motion
- Getting Started with g2core
- Connecting to g2core
- Configuring g2core
- Flashing g2core
- Troubleshooting
Reference Pages
- Gcodes
- Mcodes
- Text Mode
- JSON Communications
- GPIO Digital IO
- Alarms & Exceptions
- Power Management
- Coordinate Systems
- Status Reports
- Status Codes
- G2 Communications
- Tool Offsets and Selection
- Probing
- Feedhold, Resume, Job Kill
- Marlin Compatibility
- 9 Axis UVW Operation
- gQuintic Specs
Discussion Topics
- Roadmap
- GPIO for 1.X Releases
- Toolheads
- Raster Streaming Prototol
- g2core REST Interface
- Gcode Parsing
- G2 3DP Dialect
- Consensus Gcode
- Digital DRO
- Overview of Motion Processing
Developer Pages
- Development & Contribution
- Branching and Release - DRAFT
- Getting Started with g2core Development
- Project Structure & Motate
- Compiling G2
- OSX w/Xcode
- OSX/Linux Command Line
- Windows10 w/AtmelStudio7
- Debugging G2 on OSX
- Board and Machine Profiles
- Arduino Due Pinout
- Arduino DUE External Interfaces
- Diagnostics
- Debugging w/Motate Pins
- Development Troubleshooting
- g2core Communications
- Git Procedures
- Windows 10 / VMware 8 Issues
- Dual Endpoint USB Internals
- G2core License
- VSCode Setup
- Compatibility Axioms
- Wiki History