From 2cce67ad847ca1a92c118295148c1e2216d0bace Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Sat, 15 Apr 2017 15:22:50 -0400 Subject: docs: Add initial Kinematics document Signed-off-by: Kevin O'Connor --- docs/Code_Overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/Code_Overview.md') 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 -- cgit v1.2.3-70-g09d2