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

docs: Fix another typo in Code_Overview.md 

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2019-12-04 12:26:45 -05:00
parent f82a85aad0
commit 10270dc7ef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Code_Overview.md
View File

@ -447,12 +447,12 @@ but does not include moves on the look-ahead queue. One may use the
`toolhead.flush_step_generation()` or `toolhead.wait_moves()` calls to `toolhead.flush_step_generation()` or `toolhead.wait_moves()` calls to
fully flush the look-ahead and step generation code. fully flush the look-ahead and step generation code.
The "kinematic" position (`kin.set_tag_position()` and The "kinematic" position (`stepper.set_tag_position()` and
`kin.calc_tag_position()`) is the cartesian position of the toolhead `kin.calc_tag_position()`) is the cartesian position of the toolhead
as derived from the "stepper" position and is relative to the as derived from the "stepper" position and is relative to the
coordinate system specified in the config file. This may differ from coordinate system specified in the config file. This may differ from
the requested cartesian position due to the granularity of the stepper the requested cartesian position due to the granularity of the stepper
motors. If the robot is in motion when `kin.set_tag_position()` is motors. If the robot is in motion when `stepper.set_tag_position()` is
issued then the reported value includes moves buffered on the issued then the reported value includes moves buffered on the
micro-controller, but does not include moves on the look-ahead micro-controller, but does not include moves on the look-ahead
queue. One may use the `toolhead.flush_step_generation()` or queue. One may use the `toolhead.flush_step_generation()` or