Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Duet3D/RepRapFirmware.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordc42 <dcrocker@eschertech.com>2018-05-04 10:52:05 +0300
committerGitHub <noreply@github.com>2018-05-04 10:52:05 +0300
commitcb02a03702229596edd7634be064c190ef4ae9c8 (patch)
tree4b29d46f4b682f69102d2b55ee788dae70aca396 /AddingNewKinematics.md
parent990e5f8ac5e79ba1dce55d1a0efa1a047e506c99 (diff)
Update AddingNewKinematics.md
Diffstat (limited to 'AddingNewKinematics.md')
-rw-r--r--AddingNewKinematics.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/AddingNewKinematics.md b/AddingNewKinematics.md
index 907dad4a..2c3c605b 100644
--- a/AddingNewKinematics.md
+++ b/AddingNewKinematics.md
@@ -6,7 +6,7 @@ The supported kinematics are defined in files in folder src/Movement/Kinematics.
To add new kinematics:
1. Tell me the name of your kinematics and ask me (dc42) to allocate a kinematics type number for it, via the Duet3d forum. The kinematics type number will be the K parameter in the M669 command.
-2. Create .h and .cpp files to declare and implement the class for your kinematics. If you want to support bed levelling using multiple independent leadscrews, or the facility to assist users in determining corrections to make to manual bed levelling screws, then you should derive your kinematics class from class ZLeadscrewKinematics. Otherwise it is normally appropriate to derive it directly from class Kinematics.
+2. Create .h and .cpp files to declare and implement the class for your kinematics. If your machine has a conventional Z axis and you want to support bed levelling using multiple independent leadscrews, or the facility to assist users in determining corrections to make to manual bed levelling screws, then you should derive your kinematics class from class ZLeadscrewKinematics. Otherwise it is normally appropriate to derive it directly from class Kinematics.
3. In your kinematics class, override virtual functions as needed. See the comments in file Kinematics.h for a description of those functions.