G-code & post-processors
G-code written for your controller, in its own dialect
Fourteen flavors, true arcs, custom blocks and one file per tool if you want. Dusty also opens any G-code program and checks it as strictly as its own.
In detail
Saving the G-code
- Written for your machine Its flavor, spindle, accessories, custom blocks and post-processor options; without a machine, GRBL 1.1 for a 3018-type CNC.
- One file or several A single file, one per tool, per sequence or per operation, or a dated folder — and presets of your own.
- File name tokens Project, operation, tool name, number or radius, date and time in braces; a slash in the format creates a folder.
- Strict ASCII output Accented letters are transliterated, so that no character can ever be taken for an immediate GRBL command.
- Every page at once In a series, the G-code of each page goes into its own folder, and the template page is skipped.
Flavors and arcs
- Fourteen G-code flavors GRBL 1.1, GRBL M3, grblHAL, GRBL-STM, FluidNC, Smoothieware, Marlin, Duet, LinuxCNC, Mach3/Mach4, UCCNC, MASSO, Centroid and generic RS-274.
- Tool changes in dialect An M0 pause after retract for GRBL, M6 T for grblHAL, T M6 for LinuxCNC or Mach3, a message box for Duet.
- True arcs Circles, fillets and their offsets written as G2 and G3: shorter programs and smoother motion on the machine.
- Segments when needed Arcs cut into pieces of 120° at most for radius mode, segments for Marlin, or segments only if your machine prefers.
Post-processor
- Post-processor options Tool change mode, automatic changer, dwell units, comment style, comments removed or verbose output, saved with the machine.
- Custom G-code blocks Header, program end, operation start and end, tool change, spindle, coolant, vacuum and dwell, each written at the right moment.
- Variables and conditions {tool_number}, {rpm}, {safe_z} and more; lines that vanish without a value, words written only when they change.
- Errors caught as you type Each problem shown with its line, and a preview of the expanded block with example values.
Opening a program
- Open G-code as is Any .nc, .gcode, .ngc or .tap file, shown as colored text, as a wireframe view and as a summary.
- Checked like Dusty’s own Travel, safe height, feeds and rapids below Z 0 are checked; a line Dusty cannot read blocks sending.
- Follow the current line While sending, the current line is marked in the text and highlighted in the wireframe view, the tool shown by a red crosshair.
- Resume at a line Dusty rebuilds units, coordinate system, spindle and feed, rises to the safe height and goes back down at the feed you choose.
In the manual
-
G-code
Save the G-code for your controller with flexible file names, open and replay a program, choose the flavor, arcs and post-processor options, and write custom blocks.
-
G-code flavors
The fourteen controller dialects Dusty writes — GRBL, grblHAL, FluidNC, Smoothieware, Marlin, Duet, LinuxCNC, Mach3, MASSO and more — and how each one changes tools.
-
Custom G-code
Write your own G-code blocks for program start and end, tool change, spindle, coolant and vacuum, with variables, optional values and mode macros, checked as you type.
-
Opening and replaying G-code
Open a .nc or .gcode file as is, read its colored text, wireframe view and summary, send it with the same checks as a Dusty job, or resume at a chosen line.
Explore the other features
- Drawing & text Draw exactly what the bit will cut
- Toolpaths Tell Dusty how to cut; it computes every toolpath
- Tools & feeds The right bit, the right feed, from the first cut
- 3D preview & checks See the part before the first chip flies
- Machine control Your CNC connected, zeroed and under control
- Workholding & safety Stock that stays put, a workshop that stays safe
- Files & projects Your drawings open, your setup follows you
All this, for €0.
Every feature on this page is included, on every platform, for everyone.