Faster way to stop than stop()?

154 views
Skip to first unread message

the ether

unread,
May 18, 2013, 10:10:09 AM5/18/13
to accels...@googlegroups.com
The speed at which the motor stops when stop() is called is governed by the previously defined acceleration setting. Is there a faster way to stop - other than setting the acceleration to an incredibly high number?

I have microswitches that designate the end of a track. If the device being powered by the motor hits one of these, it must stop absolutely immediately.

Sandy Noble

unread,
May 18, 2013, 10:24:55 AM5/18/13
to accels...@googlegroups.com
motor.setSpeed(0);

will do it.
sn

the_ether

unread,
May 18, 2013, 11:48:00 AM5/18/13
to accels...@googlegroups.com
Makes sense. Thank you.

--- On Sat, 18/5/13, Sandy Noble <sandy...@gmail.com> wrote:

From: Sandy Noble <sandy...@gmail.com>
Subject: Re: [accelstepper] Faster way to stop than stop()?
To: "accels...@googlegroups.com" <accels...@googlegroups.com>
Date: Saturday, 18 May, 2013, 15:24

motor.setSpeed(0);

will do it.
sn

--
You received this message because you are subscribed to a topic in the Google Groups "accelstepper" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/accelstepper/ThRpGvuAPrQ/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to accelstepper...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

the ether

unread,
May 18, 2013, 12:19:24 PM5/18/13
to accels...@googlegroups.com
I just saw another post about a similar problem. According to that, I need to also call motor.moveTo(motor.currentPosition); after setting the speed to zero.

On Saturday, May 18, 2013 4:48:00 PM UTC+1, the ether wrote:
Makes sense. Thank you.

Reply all
Reply to author
Forward
0 new messages