From 9197975625daa421334807f6ce6c2b077f615023 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Tue, 8 Sep 2020 10:18:28 -0400 Subject: [PATCH] docs: Note that FORCE_MOVE can lead to "No next step" errors in G-Codes.md Signed-off-by: Kevin O'Connor --- docs/G-Codes.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/G-Codes.md b/docs/G-Codes.md index 04e3e6ef..628d8a3c 100644 --- a/docs/G-Codes.md +++ b/docs/G-Codes.md @@ -488,13 +488,15 @@ section is enabled: the given distance (in mm) at the given constant velocity (in mm/s). If ACCEL is specified and is greater than zero, then the given acceleration (in mm/s^2) will be used; otherwise no - acceleration is performed. No boundary checks are performed; no - kinematic updates are made; other parallel steppers on an axis will - not be moved. Use caution as an incorrect command could cause - damage! Using this command will almost certainly place the low-level - kinematics in an incorrect state; issue a G28 afterwards to reset - the kinematics. This command is intended for low-level diagnostics - and debugging. + acceleration is performed. If acceleration is not performed then it + can lead to the micro-controller reporting "No next step" errors + (avoid these errors by specifying an ACCEL value or use a very low + VELOCITY). No boundary checks are performed; no kinematic updates + are made; other parallel steppers on an axis will not be moved. Use + caution as an incorrect command could cause damage! Using this + command will almost certainly place the low-level kinematics in an + incorrect state; issue a G28 afterwards to reset the kinematics. + This command is intended for low-level diagnostics and debugging. - `SET_KINEMATIC_POSITION [X=] [Y=] [Z=]`: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use