Manually drive forward/backward a stepper motor?
-
Hey,
I was wondering if anyone has an idea of making a standalone switch for driving back and forth a stepper motor.
For instance - I use a motor to drive a syringe so I'd like to tweak the steps back an d forth to adjust the tool in a fast fashion without running the feedrate/amount on the gui.
The switch shouldn't interfere the if I choose to use the MCU or run a g-code file.
If anyone knows the HYREL printers, something of that sort.
thoughts ?
-
@cj-bravo Might be possible. You could connect a switch to a spare end stop then set up an external trigger that will run a macro when the switch is pressed. Then maybe define the motor to be either another axis or an extruder. The macro would then run a G1 move for that motor. I'm on my phone right now and I can't off hand remember the trigger command.
-
https://duet3d.dozuki.com/Wiki/Gcode#Section_M581_Configure_external_trigger
you'd need two triggers/pins, one for each direction.
but i think this will be allowed to interfere during printing if accidentally pressed. removing the triggers in start.g will remedy that, but you'll have to recreate them in stop.g/cancel.g and have the silcer send M0 at the end of a print.
-
@bearer
Would it interfere with the g-code file only if pressed ? or if not pressed with will affect the g-code?
-
i'm not 100% sure where in the motion planning queue the triggered code would go as I haven't tried.
but of course if you don't press the buttons connected to the triggers then it will not interfere the running g-code. however using the two macros to clear and set the triggers is a solution if it turns out to be a problem. (you could do a relatively safe test with short slow moves in a g-code file and try pressing the buttons attached to the triggers and see what happens)
-
@cj-bravo said in Manually drive forward/backward a stepper motor?:
@bearer
Would it interfere with the g-code file only if pressed ? or if not pressed with will affect the g-code?
Take a look at the "C" parameter for M581 - that might answer you question
-
C Condition: whether to trigger at any time (C0, default) or only when printing a file from SD card (C1)
Seems that could do with a C2 option for only triggering when not printing?
