diff options
| author | Kevin O'Connor <kevin@koconnor.net> | 2017-04-15 15:22:50 -0400 |
|---|---|---|
| committer | Kevin O'Connor <kevin@koconnor.net> | 2017-04-15 22:26:03 -0400 |
| commit | 2cce67ad847ca1a92c118295148c1e2216d0bace (patch) | |
| tree | ebe59917135caabbf28621fbb3ced6e7119beb31 /docs/Code_Overview.md | |
| parent | 2cb935c3006d919e1796644e51caedb3e46f6a3b (diff) | |
| download | kutter-2cce67ad847ca1a92c118295148c1e2216d0bace.tar.gz kutter-2cce67ad847ca1a92c118295148c1e2216d0bace.tar.xz kutter-2cce67ad847ca1a92c118295148c1e2216d0bace.zip | |
docs: Add initial Kinematics document
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/Code_Overview.md')
| -rw-r--r-- | docs/Code_Overview.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/Code_Overview.md b/docs/Code_Overview.md index 011de21a..07df5599 100644 --- a/docs/Code_Overview.md +++ b/docs/Code_Overview.md @@ -113,7 +113,8 @@ Code flow of a move command A typical printer movement starts when a "G1" command is sent to the Klippy host and it completes when the corresponding step pulses are produced on the micro-controller. This section outlines the code flow -of a typical move command. +of a typical move command. The [kinematics](Kinematics.md) document +provides further information on the mechanics of moves. * Processing for a move command starts in gcode.py. The goal of gcode.py is to translate G-code into internal calls. Changes in |