Remove + swap PLANNER_XY_FEEDRATE_MM_S
w/ XY_PROBE_FEEDRATE_MM_S
#27411
+26
−29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR removes and replaces
PLANNER_XY_FEEDRATE_MM_S
w/XY_PROBE_FEEDRATE_MM_S
Something that stood out to me is
planner.settings.max_feedrate_mm_s[*_AXIS]
, which is defined byDEFAULT_MAX_FEEDRATE
, which X/Y_AXIS is usually something in the hundreds.However, in motion.h, we have:
so when not using a probe it is
#define XY_PROBE_FEEDRATE_MM_S PLANNER_XY_FEEDRATE_MM_S
and
PLANNER_XY_FEEDRATE_MM_S
can be:(from planner.h)
so basically,
PLANNER_XY_FEEDRATE_MM_S
should be something like "60", but being defined asmax_feedrate_mm_s
in the hundreds doesn't make sense. soXY_PROBE_FEEDRATE_MM_S = PLANNER_XY_FEEDRATE_MM_S = max_feedrate_mm_s
doesn't make sense.that is why
XY_PROBE_FEEDRATE_MM_S
should beXY_PROBE_FEEDRATE
, which is((homing_feedrate_mm_m.x + homing_feedrate_mm_m.y) / 2)
, andhoming_feedrate_mm_m
=HOMING_FEEDRATE_MM_M
={ (50*60), (50*60), (4*60) }
Requirements
Benefits
Configurations
Related Issues