-
Notifications
You must be signed in to change notification settings - Fork 295
Gcode Coordinate Offsets
Applies to firmware build 100.xx and above
G10 L2 Pn 'axes'
set coordinate system offsets relative to machine origin
G10 L2 offsets the origin of the axes in the specified coordinate system to the value of the axis word.
- P is coordinate system 1-6, corresponding to G54 - G59, respectively
- The offset values in the 'axes' words are from the machine origin established during homing
- Axis words not used will not be changed
- The offset value will replace any current offsets in effect for the specified coordinate system
- G10 L2 Pn does not change from the current coordinate system to the one specified by P, you have to use G54-59
- G10 L2 Pn offsets set are independent of G92 origin offsets, and are cumulative
- The coordinate system set by a G10 command may be active or inactive at the time the G10 is executed. If it is currently active the new coordinates take effect immediately
For example, if you wanted the X origin of coordinate system 1 (G54) to be 100 mm to the right of zero you would enter:
G10 L2 P1 X100
G10 L20 Pn 'axes'
set coordinate system offsets relative to the current position
G10 L20 is similar to G10 L2 except that instead of setting the offset/entry to the given value, it is set to a calculated value that makes the current coordinates become the given value. The axis value is the value you wish the current point to be.
For example, if you wanted the XYZ coordinates to be set to (0,0,0) for G55 at the current position you would enter:
G10 L20 P2 X0 Y0 Z0
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