3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Note that FORCE_MOVE can lead to "No next step" errors in G-Codes.md 

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2020-09-08 10:18:28 -04:00
parent c285f8b6cf
commit 9197975625
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/G-Codes.md
View File

@ -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=<value>] [Y=<value>] [Z=<value>]`: Force
the low-level kinematic code to believe the toolhead is at the given
cartesian position. This is a diagnostic and debugging command; use