From c0d860487a70a05d44973d53a981e935ce7b3ad0 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Sat, 1 May 2021 00:27:43 -0400 Subject: stepper: Remove set_tag_position() code Have callers store the stepper positions in a dict. Signed-off-by: Kevin O'Connor --- docs/Code_Overview.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/Code_Overview.md b/docs/Code_Overview.md index f7d14463..167b7c18 100644 --- a/docs/Code_Overview.md +++ b/docs/Code_Overview.md @@ -331,12 +331,11 @@ Useful steps: seconds) to a cartesian coordinate (in millimeters), and then calculate the desired stepper position (in millimeters) from that cartesian coordinate. -4. Implement the `calc_tag_position()` method in the new kinematics - class. This method calculates the position of the toolhead in - cartesian coordinates from the position of each stepper (as - returned by `stepper.get_tag_position()`). It does not need to be - efficient as it is typically only called during homing and probing - operations. +4. Implement the `calc_position()` method in the new kinematics class. + This method calculates the position of the toolhead in cartesian + coordinates from the 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()`, `get_status()`, `get_steppers()`, `home()`, and `set_position()` methods. These functions are typically used to provide kinematic specific checks. -- cgit v1.2.3-70-g09d2