mirror of
https://github.com/Klipper3d/klipper.git
synced 2025-08-05 21:14:05 -06:00
Allow manual_stepper to run in parallel than an other stepper
Signed-off-by: Jeremy Briffaut <kakou@kakou.org> Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
6b7e917a8e
commit
6be552f6e6
2 changed files with 23 additions and 15 deletions
|
@ -255,18 +255,22 @@ The following command is available when a "manual_stepper" config
|
|||
section is enabled:
|
||||
- `MANUAL_STEPPER STEPPER=config_name [ENABLE=[0|1]]
|
||||
[SET_POSITION=<pos>] [SPEED=<speed>] [ACCEL=<accel>]
|
||||
[MOVE=<pos> [STOP_ON_ENDSTOP=[1|2|-1|-2]]`: This command will alter
|
||||
the state of the stepper. Use the ENABLE parameter to enable/disable
|
||||
the stepper. Use the SET_POSITION parameter to force the stepper to
|
||||
think it is at the given position. Use the MOVE parameter to request
|
||||
a movement to the given position. If SPEED and/or ACCEL is specified
|
||||
then the given values will be used instead of the defaults specified
|
||||
in the config file. If an ACCEL of zero is specified then no
|
||||
acceleration will be performed. If STOP_ON_ENDSTOP=1 is specified
|
||||
then the move will end early should the endstop report as triggered
|
||||
(use STOP_ON_ENDSTOP=2 to complete the move without error even if
|
||||
the endstop does not trigger, use -1 or -2 to stop when the endstop
|
||||
reports not triggered).
|
||||
[MOVE=<pos> [STOP_ON_ENDSTOP=[1|2|-1|-2]] [SYNC=0]`: This command
|
||||
will alter the state of the stepper. Use the ENABLE parameter to
|
||||
enable/disable the stepper. Use the SET_POSITION parameter to force
|
||||
the stepper to think it is at the given position. Use the MOVE
|
||||
parameter to request a movement to the given position. If SPEED
|
||||
and/or ACCEL is specified then the given values will be used instead
|
||||
of the defaults specified in the config file. If an ACCEL of zero is
|
||||
specified then no acceleration will be performed. If
|
||||
STOP_ON_ENDSTOP=1 is specified then the move will end early should
|
||||
the endstop report as triggered (use STOP_ON_ENDSTOP=2 to complete
|
||||
the move without error even if the endstop does not trigger, use -1
|
||||
or -2 to stop when the endstop reports not triggered). Normally
|
||||
future G-Code commands will be scheduled to run after the stepper
|
||||
move completes, however if a manual stepper move uses SYNC=0 then
|
||||
future G-Code movement commands may run in parallel with the stepper
|
||||
movement.
|
||||
|
||||
## Probe
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue