aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/Code_Overview.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/Code_Overview.md b/docs/Code_Overview.md
index 7b26f85d..22bbf2d3 100644
--- a/docs/Code_Overview.md
+++ b/docs/Code_Overview.md
@@ -335,10 +335,11 @@ Useful steps:
coordinates from the current position of each stepper. It does not
need to be efficient as it is typically only called during homing
and probing operations.
-5. Other methods. Implement the `check_move()`, `home()`,
- `set_position()`, and `get_steppers()` methods. These functions are
- typically used to provide kinematic specific checks. However, at
- the start of development one can use boiler-plate code here.
+5. Other methods. Implement the `check_move()`, `get_status()`,
+ `get_steppers()`, `home()`, and `set_position()` methods. These
+ functions are typically used to provide kinematic specific
+ checks. However, at the start of development one can use
+ boiler-plate code here.
6. Implement test cases. Create a g-code file with a series of moves
that can test important cases for the given kinematics. Follow the
[debugging documentation](Debugging.md) to convert this g-code file