Re: [Emc-developers] [ emc-Bugs-1390123 ] recovering from estop causes following errors

[Jon E. <el...@pi...>]

SourceForge.net wrote:

>Bugs item #1390123, was opened at 2005-12-25 11:15
>Message generated for change (Tracker Item Submitted) made by Item Submitter
>You can respond by visiting: 
>https://sourceforge.net/tracker/?func=detail&atid=106744&aid=1390123&group_id=6744
>
>Please note that this message will contain a full copy of the comment thread,
>including the initial issue submission, for this request,
>not just the latest update.
>Category: EMC2 Motion Controller
>Group: None
>Status: Open
>Resolution: None
>Priority: 5
>Submitted By: skunkwork (skunkwork)
>Assigned to: John Kasunich (jmkasunich)
>Summary: recovering from estop causes following errors
>
>Initial Comment:
>Doing a g0 move (200 ipm) and hitting the estop(F1) 
>shuts the machine off.  when reseting the estop and 
>turning the machine back on I will get a "following 
>error"  which turns the machine back off again.  I 
>tried atleast 10 times (turning the machine back on 
>and getting the "following error").  This was also 
>tested multible times with the same result.
>
>I am not sure if it does it with an estop during a 
>g01 move but will test it and reply.
>  
>
If you are using Gecko drivers without additional hardware feedback, 
this is probably
unavoidable.  The Gecko drive goes open-loop when disabled, so there is 
no longer any
relationship between step pulses at the input and the machine position.  
This is true
for both 200 and 300-series drives.

What drives and interface to them are you using?

Jon