2009-01-25 00:48:56 +01:00
|
|
|
/*
|
2011-01-14 16:45:18 +01:00
|
|
|
motion_control.c - high level interface for issuing motion commands
|
2009-01-25 00:48:56 +01:00
|
|
|
Part of Grbl
|
|
|
|
|
2013-12-31 06:02:05 +01:00
|
|
|
Copyright (c) 2011-2014 Sungeun K. Jeon
|
2011-01-14 16:45:18 +01:00
|
|
|
Copyright (c) 2009-2011 Simen Svale Skogsrud
|
2011-12-09 02:47:48 +01:00
|
|
|
Copyright (c) 2011 Jens Geisler
|
2011-09-07 03:39:14 +02:00
|
|
|
|
2009-01-25 00:48:56 +01:00
|
|
|
Grbl is free software: you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
the Free Software Foundation, either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
Grbl is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with Grbl. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
2014-01-11 04:22:10 +01:00
|
|
|
#include "system.h"
|
2011-02-05 00:45:41 +01:00
|
|
|
#include "settings.h"
|
2014-01-11 04:22:10 +01:00
|
|
|
#include "protocol.h"
|
2012-10-01 03:57:10 +02:00
|
|
|
#include "gcode.h"
|
2014-01-11 04:22:10 +01:00
|
|
|
#include "planner.h"
|
|
|
|
#include "stepper.h"
|
2009-01-25 00:48:56 +01:00
|
|
|
#include "motion_control.h"
|
2012-10-22 03:18:24 +02:00
|
|
|
#include "spindle_control.h"
|
|
|
|
#include "coolant_control.h"
|
2011-12-09 02:47:48 +01:00
|
|
|
#include "limits.h"
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
#include "probe.h"
|
2014-02-25 21:19:52 +01:00
|
|
|
#include "report.h"
|
2014-01-11 04:22:10 +01:00
|
|
|
|
2009-02-03 09:56:45 +01:00
|
|
|
|
2011-12-09 02:47:48 +01:00
|
|
|
// Execute linear motion in absolute millimeter coordinates. Feed rate given in millimeters/second
|
|
|
|
// unless invert_feed_rate is true. Then the feed_rate means that the motion should be completed in
|
|
|
|
// (1 minute)/feed_rate time.
|
|
|
|
// NOTE: This is the primary gateway to the grbl planner. All line motions, including arc line
|
|
|
|
// segments, must pass through this routine before being passed to the planner. The seperation of
|
2013-10-30 02:10:39 +01:00
|
|
|
// mc_line and plan_buffer_line is done primarily to place non-planner-type functions from being
|
|
|
|
// in the planner and to let backlash compensation or canned cycle integration simple and direct.
|
2014-02-26 20:10:07 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
2014-02-19 15:48:09 +01:00
|
|
|
void mc_line(float *target, float feed_rate, uint8_t invert_feed_rate, int32_t line_number)
|
2014-02-26 20:10:07 +01:00
|
|
|
#else
|
|
|
|
void mc_line(float *target, float feed_rate, uint8_t invert_feed_rate)
|
|
|
|
#endif
|
2009-01-25 00:48:56 +01:00
|
|
|
{
|
2013-10-30 02:10:39 +01:00
|
|
|
// If enabled, check for soft limit violations. Placed here all line motions are picked up
|
|
|
|
// from everywhere in Grbl.
|
|
|
|
if (bit_istrue(settings.flags,BITFLAG_SOFT_LIMIT_ENABLE)) { limits_soft_check(target); }
|
|
|
|
|
|
|
|
// If in check gcode mode, prevent motion by blocking planner. Soft limits still work.
|
2012-11-19 03:52:16 +01:00
|
|
|
if (sys.state == STATE_CHECK_MODE) { return; }
|
|
|
|
|
2014-02-19 15:21:40 +01:00
|
|
|
// NOTE: Backlash compensation may be installed here. It will need direction info to track when
|
|
|
|
// to insert a backlash line motion(s) before the intended line motion and will require its own
|
2012-01-10 16:34:48 +01:00
|
|
|
// plan_check_full_buffer() and check for system abort loop. Also for position reporting
|
2014-02-19 15:21:40 +01:00
|
|
|
// backlash steps will need to be also tracked, which will need to be kept at a system level.
|
|
|
|
// There are likely some other things that will need to be tracked as well. However, we feel
|
|
|
|
// that backlash compensation should NOT be handled by Grbl itself, because there are a myriad
|
|
|
|
// of ways to implement it and can be effective or ineffective for different CNC machines. This
|
|
|
|
// would be better handled by the interface as a post-processor task, where the original g-code
|
|
|
|
// is translated and inserts backlash motions that best suits the machine.
|
|
|
|
// NOTE: Perhaps as a middle-ground, all that needs to be sent is a flag or special command that
|
|
|
|
// indicates to Grbl what is a backlash compensation motion, so that Grbl executes the move but
|
|
|
|
// doesn't update the machine position values. Since the position values used by the g-code
|
|
|
|
// parser and planner are separate from the system machine positions, this is doable.
|
2011-12-09 02:47:48 +01:00
|
|
|
|
|
|
|
// If the buffer is full: good! That means we are well ahead of the robot.
|
|
|
|
// Remain in this loop until there is room in the buffer.
|
|
|
|
do {
|
|
|
|
protocol_execute_runtime(); // Check for any run-time commands
|
2012-01-06 18:10:41 +01:00
|
|
|
if (sys.abort) { return; } // Bail, if system abort.
|
2014-02-09 18:46:34 +01:00
|
|
|
if ( plan_check_full_buffer() ) { protocol_auto_cycle_start(); } // Auto-cycle start when buffer is full.
|
2013-10-30 02:10:39 +01:00
|
|
|
else { break; }
|
|
|
|
} while (1);
|
|
|
|
|
2014-02-26 20:10:07 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
2014-02-07 00:10:27 +01:00
|
|
|
plan_buffer_line(target, feed_rate, invert_feed_rate, line_number);
|
2014-02-26 20:10:07 +01:00
|
|
|
#else
|
|
|
|
plan_buffer_line(target, feed_rate, invert_feed_rate);
|
|
|
|
#endif
|
|
|
|
|
2012-11-19 03:52:16 +01:00
|
|
|
// If idle, indicate to the system there is now a planned block in the buffer ready to cycle
|
|
|
|
// start. Otherwise ignore and continue on.
|
|
|
|
if (!sys.state) { sys.state = STATE_QUEUED; }
|
2009-01-25 00:48:56 +01:00
|
|
|
}
|
|
|
|
|
2011-12-09 02:47:48 +01:00
|
|
|
|
|
|
|
// Execute an arc in offset mode format. position == current xyz, target == target xyz,
|
|
|
|
// offset == offset from current xyz, axis_XXX defines circle plane in tool space, axis_linear is
|
|
|
|
// the direction of helical travel, radius == circle radius, isclockwise boolean. Used
|
|
|
|
// for vector transformation direction.
|
2012-12-20 01:30:09 +01:00
|
|
|
// The arc is approximated by generating a huge number of tiny, linear segments. The chordal tolerance
|
|
|
|
// of each segment is configured in settings.arc_tolerance, which is defined to be the maximum normal
|
|
|
|
// distance from segment to the circle when the end points both lie on the circle.
|
2014-02-26 20:10:07 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
2014-05-26 00:05:28 +02:00
|
|
|
void mc_arc(float *position, float *target, float *offset, float radius, float feed_rate,
|
|
|
|
uint8_t invert_feed_rate, uint8_t axis_0, uint8_t axis_1, uint8_t axis_linear, int32_t line_number)
|
2014-02-26 20:10:07 +01:00
|
|
|
#else
|
2014-05-26 00:05:28 +02:00
|
|
|
void mc_arc(float *position, float *target, float *offset, float radius, float feed_rate,
|
|
|
|
uint8_t invert_feed_rate, uint8_t axis_0, uint8_t axis_1, uint8_t axis_linear)
|
2014-02-26 20:10:07 +01:00
|
|
|
#endif
|
2014-05-26 00:05:28 +02:00
|
|
|
{
|
2012-10-08 23:57:58 +02:00
|
|
|
float center_axis0 = position[axis_0] + offset[axis_0];
|
|
|
|
float center_axis1 = position[axis_1] + offset[axis_1];
|
|
|
|
float r_axis0 = -offset[axis_0]; // Radius vector from center to current location
|
|
|
|
float r_axis1 = -offset[axis_1];
|
|
|
|
float rt_axis0 = target[axis_0] - center_axis0;
|
|
|
|
float rt_axis1 = target[axis_1] - center_axis1;
|
2011-09-07 03:39:14 +02:00
|
|
|
|
|
|
|
// CCW angle between position and target from circle center. Only one atan2() trig computation required.
|
2012-10-08 23:57:58 +02:00
|
|
|
float angular_travel = atan2(r_axis0*rt_axis1-r_axis1*rt_axis0, r_axis0*rt_axis0+r_axis1*rt_axis1);
|
2014-05-26 00:05:28 +02:00
|
|
|
if (gc_state.modal.motion == MOTION_MODE_CW_ARC) { // Correct atan2 output per direction
|
2012-11-10 20:49:33 +01:00
|
|
|
if (angular_travel >= 0) { angular_travel -= 2*M_PI; }
|
|
|
|
} else {
|
|
|
|
if (angular_travel <= 0) { angular_travel += 2*M_PI; }
|
|
|
|
}
|
2012-12-20 01:30:09 +01:00
|
|
|
|
|
|
|
// NOTE: Segment end points are on the arc, which can lead to the arc diameter being smaller by up to
|
|
|
|
// (2x) settings.arc_tolerance. For 99% of users, this is just fine. If a different arc segment fit
|
|
|
|
// is desired, i.e. least-squares, midpoint on arc, just change the mm_per_arc_segment calculation.
|
2014-05-26 00:05:28 +02:00
|
|
|
// For the intended uses of Grbl, this value shouldn't exceed 2000 for the strictest of cases.
|
|
|
|
uint16_t segments = floor(fabs(0.5*angular_travel*radius)/
|
2014-01-11 04:22:10 +01:00
|
|
|
sqrt(settings.arc_tolerance*(2*radius - settings.arc_tolerance)) );
|
2011-09-07 03:39:14 +02:00
|
|
|
|
2012-12-20 01:30:09 +01:00
|
|
|
if (segments) {
|
|
|
|
// Multiply inverse feed_rate to compensate for the fact that this movement is approximated
|
|
|
|
// by a number of discrete segments. The inverse feed_rate should be correct for the sum of
|
|
|
|
// all segments.
|
|
|
|
if (invert_feed_rate) { feed_rate *= segments; }
|
|
|
|
|
|
|
|
float theta_per_segment = angular_travel/segments;
|
2014-05-26 00:05:28 +02:00
|
|
|
float linear_per_segment = (target[axis_linear] - position[axis_linear])/segments;
|
2014-01-11 04:22:10 +01:00
|
|
|
|
2012-12-20 01:30:09 +01:00
|
|
|
/* Vector rotation by transformation matrix: r is the original vector, r_T is the rotated vector,
|
|
|
|
and phi is the angle of rotation. Solution approach by Jens Geisler.
|
|
|
|
r_T = [cos(phi) -sin(phi);
|
|
|
|
sin(phi) cos(phi] * r ;
|
|
|
|
|
|
|
|
For arc generation, the center of the circle is the axis of rotation and the radius vector is
|
|
|
|
defined from the circle center to the initial position. Each line segment is formed by successive
|
|
|
|
vector rotations. Single precision values can accumulate error greater than tool precision in some
|
|
|
|
cases. So, exact arc path correction is implemented. This approach avoids the problem of too many very
|
|
|
|
expensive trig operations [sin(),cos(),tan()] which can take 100-200 usec each to compute.
|
2011-09-07 03:39:14 +02:00
|
|
|
|
2012-12-20 01:30:09 +01:00
|
|
|
Small angle approximation may be used to reduce computation overhead further. A third-order approximation
|
|
|
|
(second order sin() has too much error) holds for nearly all CNC applications, except for possibly very
|
|
|
|
small radii (~0.5mm). In other words, theta_per_segment would need to be greater than 0.25 rad(14 deg)
|
|
|
|
and N_ARC_CORRECTION would need to be large to cause an appreciable drift error (>5% of radius, for very
|
2012-12-21 16:51:36 +01:00
|
|
|
small radii, 5% of 0.5mm is very, very small). N_ARC_CORRECTION~=20 should be more than small enough to
|
|
|
|
correct for numerical drift error. Also decreasing the tolerance will improve the approximation too.
|
2012-12-20 01:30:09 +01:00
|
|
|
|
|
|
|
This approximation also allows mc_arc to immediately insert a line segment into the planner
|
|
|
|
without the initial overhead of computing cos() or sin(). By the time the arc needs to be applied
|
|
|
|
a correction, the planner should have caught up to the lag caused by the initial mc_arc overhead.
|
|
|
|
This is important when there are successive arc motions.
|
|
|
|
*/
|
|
|
|
// Computes: cos_T = 1 - theta_per_segment^2/2, sin_T = theta_per_segment - theta_per_segment^3/6) in ~52usec
|
2013-10-30 02:10:39 +01:00
|
|
|
float cos_T = 2.0 - theta_per_segment*theta_per_segment;
|
|
|
|
float sin_T = theta_per_segment*0.16666667*(cos_T + 4.0);
|
2012-12-20 01:30:09 +01:00
|
|
|
cos_T *= 0.5;
|
2011-09-07 03:39:14 +02:00
|
|
|
|
2012-12-20 01:30:09 +01:00
|
|
|
float sin_Ti;
|
|
|
|
float cos_Ti;
|
|
|
|
float r_axisi;
|
|
|
|
uint16_t i;
|
2012-12-21 16:51:36 +01:00
|
|
|
uint8_t count = 0;
|
2012-12-20 01:30:09 +01:00
|
|
|
|
2014-05-26 00:05:28 +02:00
|
|
|
for (i = 1; i<segments; i++) { // Increment (segments-1).
|
2012-12-20 01:30:09 +01:00
|
|
|
|
|
|
|
if (count < N_ARC_CORRECTION) {
|
|
|
|
// Apply vector rotation matrix. ~40 usec
|
|
|
|
r_axisi = r_axis0*sin_T + r_axis1*cos_T;
|
|
|
|
r_axis0 = r_axis0*cos_T - r_axis1*sin_T;
|
|
|
|
r_axis1 = r_axisi;
|
|
|
|
count++;
|
2014-05-26 00:05:28 +02:00
|
|
|
} else {
|
2012-12-20 01:30:09 +01:00
|
|
|
// Arc correction to radius vector. Computed only every N_ARC_CORRECTION increments. ~375 usec
|
|
|
|
// Compute exact location by applying transformation matrix from initial radius vector(=-offset).
|
|
|
|
cos_Ti = cos(i*theta_per_segment);
|
|
|
|
sin_Ti = sin(i*theta_per_segment);
|
|
|
|
r_axis0 = -offset[axis_0]*cos_Ti + offset[axis_1]*sin_Ti;
|
|
|
|
r_axis1 = -offset[axis_0]*sin_Ti - offset[axis_1]*cos_Ti;
|
|
|
|
count = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Update arc_target location
|
2014-05-26 00:05:28 +02:00
|
|
|
position[axis_0] = center_axis0 + r_axis0;
|
|
|
|
position[axis_1] = center_axis1 + r_axis1;
|
|
|
|
position[axis_linear] += linear_per_segment;
|
2014-02-26 20:10:07 +01:00
|
|
|
|
|
|
|
#ifdef USE_LINE_NUMBERS
|
2014-05-26 00:05:28 +02:00
|
|
|
mc_line(position, feed_rate, invert_feed_rate, line_number);
|
2014-02-26 20:10:07 +01:00
|
|
|
#else
|
2014-05-26 00:05:28 +02:00
|
|
|
mc_line(position, feed_rate, invert_feed_rate);
|
2014-02-26 20:10:07 +01:00
|
|
|
#endif
|
2012-12-20 01:30:09 +01:00
|
|
|
|
|
|
|
// Bail mid-circle on system abort. Runtime command check already performed by mc_line.
|
|
|
|
if (sys.abort) { return; }
|
2011-09-07 03:39:14 +02:00
|
|
|
}
|
2011-02-06 22:25:01 +01:00
|
|
|
}
|
2011-09-07 03:39:14 +02:00
|
|
|
// Ensure last segment arrives at target location.
|
2014-02-26 20:10:07 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
2014-02-07 00:10:27 +01:00
|
|
|
mc_line(target, feed_rate, invert_feed_rate, line_number);
|
2014-02-26 20:10:07 +01:00
|
|
|
#else
|
|
|
|
mc_line(target, feed_rate, invert_feed_rate);
|
|
|
|
#endif
|
2011-12-09 02:47:48 +01:00
|
|
|
}
|
|
|
|
|
2011-09-07 03:39:14 +02:00
|
|
|
|
2011-12-09 02:47:48 +01:00
|
|
|
// Execute dwell in seconds.
|
2012-10-08 23:57:58 +02:00
|
|
|
void mc_dwell(float seconds)
|
2011-12-09 02:47:48 +01:00
|
|
|
{
|
2014-05-29 23:41:53 +02:00
|
|
|
if (sys.state == STATE_CHECK_MODE) { return; }
|
2014-05-26 00:05:28 +02:00
|
|
|
|
2011-12-09 02:47:48 +01:00
|
|
|
uint16_t i = floor(1000/DWELL_TIME_STEP*seconds);
|
2014-02-09 18:46:34 +01:00
|
|
|
protocol_buffer_synchronize();
|
|
|
|
delay_ms(floor(1000*seconds-i*DWELL_TIME_STEP)); // Delay millisecond remainder.
|
2012-01-29 04:41:08 +01:00
|
|
|
while (i-- > 0) {
|
2011-12-09 02:47:48 +01:00
|
|
|
// NOTE: Check and execute runtime commands during dwell every <= DWELL_TIME_STEP milliseconds.
|
|
|
|
protocol_execute_runtime();
|
2012-01-06 18:10:41 +01:00
|
|
|
if (sys.abort) { return; }
|
2011-12-09 02:47:48 +01:00
|
|
|
_delay_ms(DWELL_TIME_STEP); // Delay DWELL_TIME_STEP increment
|
|
|
|
}
|
2009-01-25 00:48:56 +01:00
|
|
|
}
|
|
|
|
|
2011-12-09 02:47:48 +01:00
|
|
|
|
New startup script setting. New dry run, check gcode switches. New system state variable. Lots of reorganizing.
(All v0.8 features installed. Still likely buggy, but now thourough
testing will need to start to squash them all. As soon as we're done,
this will be pushed to master and v0.9 development will be started.
Please report ANY issues to us so we can get this rolled out ASAP.)
- User startup script! A user can now save one (up to 5 as compile-time
option) block of g-code in EEPROM memory. This will be run everytime
Grbl resets. Mainly to be used as a way to set your preferences, like
G21, G54, etc.
- New dry run and check g-code switches. Dry run moves ALL motions at
rapids rate ignoring spindle, coolant, and dwell commands. For rapid
physical proofing of your code. The check g-code switch ignores all
motion and provides the user a way to check if there are any errors in
their program that Grbl may not like.
- Program restart! (sort of). Program restart is typically an advanced
feature that allows users to restart a program mid-stream. The check
g-code switch can perform this feature by enabling the switch at the
start of the program, and disabling it at the desired point with some
minimal changes.
- New system state variable. This state variable tracks all of the
different state processes that Grbl performs, i.e. cycle start, feed
hold, homing, etc. This is mainly for making managing of these task
easier and more clear.
- Position lost state variable. Only when homing is enabled, Grbl will
refuse to move until homing is completed and position is known. This is
mainly for safety. Otherwise, it will let users fend for themselves.
- Moved the default settings defines into config.h. The plan is to
eventually create a set of config.h's for particular as-built machines
to help users from doing it themselves.
- Moved around misc defines into .h files. And lots of other little
things.
2012-11-03 18:32:23 +01:00
|
|
|
// Perform homing cycle to locate and set machine zero. Only '$H' executes this command.
|
|
|
|
// NOTE: There should be no motions in the buffer and Grbl must be in an idle state before
|
|
|
|
// executing the homing cycle. This prevents incorrect buffered plans after homing.
|
2013-12-30 04:34:51 +01:00
|
|
|
void mc_homing_cycle()
|
2009-01-28 23:48:21 +01:00
|
|
|
{
|
New startup script setting. New dry run, check gcode switches. New system state variable. Lots of reorganizing.
(All v0.8 features installed. Still likely buggy, but now thourough
testing will need to start to squash them all. As soon as we're done,
this will be pushed to master and v0.9 development will be started.
Please report ANY issues to us so we can get this rolled out ASAP.)
- User startup script! A user can now save one (up to 5 as compile-time
option) block of g-code in EEPROM memory. This will be run everytime
Grbl resets. Mainly to be used as a way to set your preferences, like
G21, G54, etc.
- New dry run and check g-code switches. Dry run moves ALL motions at
rapids rate ignoring spindle, coolant, and dwell commands. For rapid
physical proofing of your code. The check g-code switch ignores all
motion and provides the user a way to check if there are any errors in
their program that Grbl may not like.
- Program restart! (sort of). Program restart is typically an advanced
feature that allows users to restart a program mid-stream. The check
g-code switch can perform this feature by enabling the switch at the
start of the program, and disabling it at the desired point with some
minimal changes.
- New system state variable. This state variable tracks all of the
different state processes that Grbl performs, i.e. cycle start, feed
hold, homing, etc. This is mainly for making managing of these task
easier and more clear.
- Position lost state variable. Only when homing is enabled, Grbl will
refuse to move until homing is completed and position is known. This is
mainly for safety. Otherwise, it will let users fend for themselves.
- Moved the default settings defines into config.h. The plan is to
eventually create a set of config.h's for particular as-built machines
to help users from doing it themselves.
- Moved around misc defines into .h files. And lots of other little
things.
2012-11-03 18:32:23 +01:00
|
|
|
sys.state = STATE_HOMING; // Set system state variable
|
2013-12-30 04:34:51 +01:00
|
|
|
limits_disable(); // Disable hard limits pin change register for cycle duration
|
|
|
|
|
|
|
|
// -------------------------------------------------------------------------------------
|
|
|
|
// Perform homing routine. NOTE: Special motion case. Only system reset works.
|
New startup script setting. New dry run, check gcode switches. New system state variable. Lots of reorganizing.
(All v0.8 features installed. Still likely buggy, but now thourough
testing will need to start to squash them all. As soon as we're done,
this will be pushed to master and v0.9 development will be started.
Please report ANY issues to us so we can get this rolled out ASAP.)
- User startup script! A user can now save one (up to 5 as compile-time
option) block of g-code in EEPROM memory. This will be run everytime
Grbl resets. Mainly to be used as a way to set your preferences, like
G21, G54, etc.
- New dry run and check g-code switches. Dry run moves ALL motions at
rapids rate ignoring spindle, coolant, and dwell commands. For rapid
physical proofing of your code. The check g-code switch ignores all
motion and provides the user a way to check if there are any errors in
their program that Grbl may not like.
- Program restart! (sort of). Program restart is typically an advanced
feature that allows users to restart a program mid-stream. The check
g-code switch can perform this feature by enabling the switch at the
start of the program, and disabling it at the desired point with some
minimal changes.
- New system state variable. This state variable tracks all of the
different state processes that Grbl performs, i.e. cycle start, feed
hold, homing, etc. This is mainly for making managing of these task
easier and more clear.
- Position lost state variable. Only when homing is enabled, Grbl will
refuse to move until homing is completed and position is known. This is
mainly for safety. Otherwise, it will let users fend for themselves.
- Moved the default settings defines into config.h. The plan is to
eventually create a set of config.h's for particular as-built machines
to help users from doing it themselves.
- Moved around misc defines into .h files. And lots of other little
things.
2012-11-03 18:32:23 +01:00
|
|
|
|
2013-12-30 04:34:51 +01:00
|
|
|
// Search to engage all axes limit switches at faster homing seek rate.
|
2014-02-09 18:46:34 +01:00
|
|
|
limits_go_home(HOMING_CYCLE_0); // Homing cycle 0
|
|
|
|
#ifdef HOMING_CYCLE_1
|
|
|
|
limits_go_home(HOMING_CYCLE_1); // Homing cycle 1
|
2013-12-30 04:34:51 +01:00
|
|
|
#endif
|
2014-02-09 18:46:34 +01:00
|
|
|
#ifdef HOMING_CYCLE_2
|
|
|
|
limits_go_home(HOMING_CYCLE_2); // Homing cycle 2
|
2013-12-30 04:34:51 +01:00
|
|
|
#endif
|
|
|
|
|
2013-01-19 01:02:44 +01:00
|
|
|
protocol_execute_runtime(); // Check for reset and set system abort.
|
2012-11-15 01:36:29 +01:00
|
|
|
if (sys.abort) { return; } // Did not complete. Alarm state set by mc_alarm.
|
Hard limits, homing direction, pull-off limits after homing, status reports in mm or inches, system alarm, and more.
- Thank you statement added for Alden Hart of Synthetos.
- Hard limits option added, which also works with homing by pulling off
the switches to help prevent unintended triggering. Hard limits use a
interrupt to sense a falling edge pin change and immediately go into
alarm mode, which stops everything and forces the user to issue a reset
(Ctrl-x) or reboot.
- Auto cycle start now a configuration option.
- Alarm mode: A new method to kill all Grbl processes in the event of
something catastrophic or potentially catastropic. Just works with hard
limits for now, but will be expanded to include g-code errors (most
likely) and other events.
- Updated status reports to be configurable in inches or mm mode. Much
more to do here, but this is the first step.
- New settings: auto cycle start, hard limit enable, homing direction
mask (which works the same as the stepper mask), homing pulloff
distance (or distance traveled from homed machine zero to prevent
accidental limit trip).
- Minor memory liberation and calculation speed ups.
2012-10-17 05:29:45 +02:00
|
|
|
|
2014-02-09 18:46:34 +01:00
|
|
|
// Homing cycle complete! Setup system for normal operation.
|
|
|
|
// -------------------------------------------------------------------------------------
|
2013-10-30 02:10:39 +01:00
|
|
|
|
2014-02-09 18:46:34 +01:00
|
|
|
// Gcode parser position was circumvented by the limits_go_home() routine, so sync position now.
|
2013-10-30 02:10:39 +01:00
|
|
|
gc_sync_position();
|
2014-02-19 03:23:39 +01:00
|
|
|
|
2014-02-09 18:46:34 +01:00
|
|
|
// Set idle state after homing completes and before returning to main program.
|
|
|
|
sys.state = STATE_IDLE;
|
|
|
|
st_go_idle(); // Set idle state after homing completes
|
2012-11-01 16:37:27 +01:00
|
|
|
|
2012-11-15 01:36:29 +01:00
|
|
|
// If hard limits feature enabled, re-enable hard limits pin change register after homing cycle.
|
2013-12-30 04:34:51 +01:00
|
|
|
limits_init();
|
2011-10-12 04:51:04 +02:00
|
|
|
}
|
2012-10-22 03:18:24 +02:00
|
|
|
|
2014-02-28 06:30:24 +01:00
|
|
|
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
// Perform tool length probe cycle. Requires probe switch.
|
|
|
|
// NOTE: Upon probe failure, the program will be stopped and placed into ALARM state.
|
2014-02-28 06:30:24 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
void mc_probe_cycle(float *target, float feed_rate, uint8_t invert_feed_rate, int32_t line_number)
|
2014-02-28 06:30:24 +01:00
|
|
|
#else
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
void mc_probe_cycle(float *target, float feed_rate, uint8_t invert_feed_rate)
|
2014-02-28 06:30:24 +01:00
|
|
|
#endif
|
2014-02-25 21:19:52 +01:00
|
|
|
{
|
2014-03-07 19:33:57 +01:00
|
|
|
if (sys.state != STATE_CYCLE) protocol_auto_cycle_start();
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
protocol_buffer_synchronize(); // Finish all queued commands
|
|
|
|
if (sys.abort) { return; } // Return if system reset has been issued.
|
2014-02-25 21:19:52 +01:00
|
|
|
|
|
|
|
// Perform probing cycle. Planner buffer should be empty at this point.
|
2014-02-28 06:30:24 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
mc_line(target, feed_rate, invert_feed_rate, line_number);
|
2014-02-28 06:30:24 +01:00
|
|
|
#else
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
mc_line(target, feed_rate, invert_feed_rate);
|
2014-02-28 06:30:24 +01:00
|
|
|
#endif
|
2014-02-25 21:19:52 +01:00
|
|
|
|
2014-05-26 00:05:28 +02:00
|
|
|
// NOTE: Parser error-checking ensures the probe isn't already closed/triggered.
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
sys.probe_state = PROBE_ACTIVE;
|
2014-02-25 21:19:52 +01:00
|
|
|
|
2014-07-07 03:05:12 +02:00
|
|
|
bit_true_atomic(sys.execute, EXEC_CYCLE_START);
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
do {
|
|
|
|
protocol_execute_runtime();
|
|
|
|
if (sys.abort) { return; } // Check for system abort
|
|
|
|
} while ((sys.state != STATE_IDLE) && (sys.state != STATE_QUEUED));
|
2014-02-25 21:19:52 +01:00
|
|
|
|
2014-07-07 03:05:12 +02:00
|
|
|
if (sys.probe_state == PROBE_ACTIVE) { bit_true_atomic(sys.execute, EXEC_CRIT_EVENT); }
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
protocol_execute_runtime(); // Check and execute run-time commands
|
|
|
|
if (sys.abort) { return; } // Check for system abort
|
2014-02-25 21:19:52 +01:00
|
|
|
|
|
|
|
//Prep the new target based on the position that the probe triggered
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
uint8_t i;
|
2014-02-25 21:19:52 +01:00
|
|
|
for(i=0; i<N_AXIS; ++i){
|
|
|
|
target[i] = (float)sys.probe_position[i]/settings.steps_per_mm[i];
|
|
|
|
}
|
|
|
|
|
|
|
|
protocol_execute_runtime();
|
|
|
|
|
|
|
|
st_reset(); // Immediately force kill steppers and reset step segment buffer.
|
|
|
|
plan_reset(); // Reset planner buffer. Zero planner positions. Ensure homing motion is cleared.
|
|
|
|
plan_sync_position(); // Sync planner position to current machine position for pull-off move.
|
|
|
|
|
2014-02-28 06:30:24 +01:00
|
|
|
#ifdef USE_LINE_NUMBERS
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
mc_line(target, feed_rate, invert_feed_rate, line_number); // Bypass mc_line(). Directly plan homing motion.
|
2014-02-28 06:30:24 +01:00
|
|
|
#else
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
mc_line(target, feed_rate, invert_feed_rate); // Bypass mc_line(). Directly plan homing motion.
|
2014-02-28 06:30:24 +01:00
|
|
|
#endif
|
2014-02-25 21:19:52 +01:00
|
|
|
|
2014-07-07 03:05:12 +02:00
|
|
|
bit_true_atomic(sys.execute, EXEC_CYCLE_START);
|
2014-02-25 21:19:52 +01:00
|
|
|
protocol_buffer_synchronize(); // Complete pull-off motion.
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
if (sys.abort) { return; } // Did not complete. Alarm state set by mc_alarm.
|
2014-02-25 21:19:52 +01:00
|
|
|
|
|
|
|
// Gcode parser position was circumvented by the this routine, so sync position now.
|
|
|
|
gc_sync_position();
|
|
|
|
|
2014-05-26 00:05:28 +02:00
|
|
|
// Output the probe position as message.
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
report_probe_parameters();
|
2014-02-25 21:19:52 +01:00
|
|
|
}
|
2012-10-22 03:18:24 +02:00
|
|
|
|
G38.2 probe feature rough draft installed. Working but needs testing.
- G38.2 straight probe now supported. Rough draft. May be tweaked more
as testing ramps up.
- G38.2 requires at least one axis word. Multiple axis words work too.
When commanded, the probe cycle will move at the last ‘F’ feed rate
specified in a straight line.
- During a probe cycle: If the probe pin goes low (normal high), Grbl
will record that immediate position and engage a feed hold. Meaning
that the CNC machine will move a little past the probe switch point, so
keep federates low to stop sooner. Once stopped, Grbl will issue a move
to go back to the recorded probe trigger point.
- During a probe cycle: If the probe switch does not engage by the time
the machine has traveled to its target coordinates, Grbl will issue an
ALARM and the user will be forced to reset Grbl. (Currently G38.3 probe
without error isn’t supported, but would be easy to implement later.)
- After a successful probe, Grbl will send a feedback message
containing the recorded probe coordinates in the machine coordinate
system. This is as the g-code standard on probe parameters specifies.
- The recorded probe parameters are retained in Grbl memory and can be
viewed with the ‘$#’ print parameters command. Upon a power-cycle, not
a soft-reset, Grbl will re-zero these values.
- Moved ‘$#’ command to require IDLE or ALARM mode, because it accesses
EEPROM to fetch the coordinate system offsets.
- Updated the Grbl version to v0.9d.
- The probe cycle is subject to change upon testing or user-feedback.
2014-03-01 06:03:26 +01:00
|
|
|
|
2012-11-15 01:36:29 +01:00
|
|
|
// Method to ready the system to reset by setting the runtime reset command and killing any
|
|
|
|
// active processes in the system. This also checks if a system reset is issued while Grbl
|
|
|
|
// is in a motion state. If so, kills the steppers and sets the system alarm to flag position
|
|
|
|
// lost, since there was an abrupt uncontrolled deceleration. Called at an interrupt level by
|
|
|
|
// runtime abort command and hard limits. So, keep to a minimum.
|
|
|
|
void mc_reset()
|
2012-10-22 03:18:24 +02:00
|
|
|
{
|
2012-11-15 01:36:29 +01:00
|
|
|
// Only this function can set the system reset. Helps prevent multiple kill calls.
|
|
|
|
if (bit_isfalse(sys.execute, EXEC_RESET)) {
|
2014-07-07 03:05:12 +02:00
|
|
|
bit_true_atomic(sys.execute, EXEC_RESET);
|
2012-11-15 01:36:29 +01:00
|
|
|
|
|
|
|
// Kill spindle and coolant.
|
2012-10-22 03:18:24 +02:00
|
|
|
spindle_stop();
|
|
|
|
coolant_stop();
|
2012-11-15 01:36:29 +01:00
|
|
|
|
|
|
|
// Kill steppers only if in any motion state, i.e. cycle, feed hold, homing, or jogging
|
|
|
|
// NOTE: If steppers are kept enabled via the step idle delay setting, this also keeps
|
|
|
|
// the steppers enabled by avoiding the go_idle call altogether, unless the motion state is
|
|
|
|
// violated, by which, all bets are off.
|
2013-12-30 04:34:51 +01:00
|
|
|
if (sys.state & (STATE_CYCLE | STATE_HOLD | STATE_HOMING)) {
|
2014-07-07 03:05:12 +02:00
|
|
|
bit_true_atomic(sys.execute, EXEC_ALARM); // Flag main program to execute alarm state.
|
2014-02-09 18:46:34 +01:00
|
|
|
st_go_idle(); // Force kill steppers. Position has likely been lost.
|
2012-11-15 01:36:29 +01:00
|
|
|
}
|
2012-10-22 03:18:24 +02:00
|
|
|
}
|
|
|
|
}
|