-
Notifications
You must be signed in to change notification settings - Fork 295
Tool Types Beyond Spindle
We would like to consider expanding the concept of a toolhead in ways that are mostly compatible with NIST-style gcode without a plethora of additional M-codes or the need to unnecessarily re-interpret the meaning of axes.
As a secondary goal, we would like to encourage and support the use of "device-independent gcode." This primarily means that the gcode designed for one type of machine (say an FFD 3D printer) should work on any other machine of the same type and with the same used set of features. There will of course be exceptions (a gcode file that uses 2 extruders won't work on a machine with one, for example), but we can still eliminate the incorporating of transient settings into the gcode, such as filament diameter.
In current gcode (not counting extensions such as those used by RepRap flavors of 3d Printer, etc), there is the concept of an ever-present "spindle". That spindle may also make use of a "tool changer" to change the bit held by the tool (or possibly the entire spindle itself). These tools start at index 1 and go up, with 0 being a special meaning "empty spindle" or "no tool".
Usage example:
G0 X0 Y0 ; move to (0,0) quickly
M3 S12000 ; Turn on the spindle, rotating clockwise at "12000"
... ; moves while the spindle is on
G1 ... S11000 ; move to ... after adjusting the speed to "11000"
M5 ; turn spindle off
There are other traditional CNC facilities, such as "coolant" that may be reappropriated as well.
We change the term "spindle" to "toolhead," and extend the concept of a "tool." Then we say that there are different types of toolheads, one of which is a spindle.
Types of toolhead:
-
Spindle
-
M3
,M4
,M5
behavior: Turn on the spindle at the RPM specified by the S word.- Motion will plan to a stop for
M3
,M4
, and possibly S word changes, with a configurable delay to allow the RPM to be achieved. - Some spindles will have a signal to indicate that they are at speed, in which case we could wait for that signal.
- Motion will plan to a stop for
- Tool in a spindle means a rotary bit, and would have tool length offsets and such applied to it.
-
-
Laser
-
M3
,M4
,M5
behavior: Turn on a laser, with the power setting based on the S word, possibly with some coversion table between input and output.- Motion will not have to be paused for laser enabling or power level changes.
- Power level applied is to be adjusted by the active velocity dynamically (on a segment-by-segment basis) to maintain consistent laser coverage even during acceleration and deceleration.
- Lasers have other controls as well. These just highlight the primary controls.
-
-
Extruder
-
M3
,M4
,M5
behavior: TheS
word is interpreted as mm³ (or microliters, uL). All feed moves (G1, arcs, etc) will move the associated axis motor by the appropriate amount in order to extrude that uL of filament per linear mm of travel.- An otherwise configured or measured filament diameter will be used in the computation of how far to move that extruder axis.
- The extruder axis should be one of U, V, or W linear axis. The axis should not be used directly except for the case of loading filament.
- Filament retraction can be handled internally and driven by
M3
andM5
. Retraction will not happen on aG1
toG0
transition or aG0
toG1
transition.
- Tool in an Extruder means the filament itself. Different tools in the same toolhead may have different filament diameters, jerk settings for the extruder "axis," etc.
-
Each toolhead can have a different type. Each tool number can refer to a different toolhead, and multiple tools can refer to the same toolhead. This allows multiple of one toolhead type (2 extruders) or different toolhead types on a machine (extruder and spindle).
Tool switching will be controlled by M6
and a T
word. The process of switching is TBD.
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