Hi Chris;
After I corrected my thread order the symptom remained the same.
Additional information observed is; the first home after EMC has been
started the value loaded at the home/limit release point is approximately
the position the axis was at EMC start, as loaded from the
PARAMETER_FILE =. This is far enough to spike the "axis.n.f-error" off
the scale instantly and produce the Joint Following Error.
I am running EMC 2.3.? off the last Live Disk install.
Maybe I could park the system at the limit switches before system shutdown.
Here is hoping there is better solution.
Thanks
Don
On Wed, Jun 16, 2010 at 3:06 PM, Chris Radek <ch...@timeguy.com> wrote:
> On Wed, Jun 16, 2010 at 01:43:46PM -0500, Chris Radek wrote:
> >
> > I assume you're homing to index. If so this sounds like the "homing
> > thump" problem. You should update to 2.4.1 and then hook up your
> > pid.N.index-enable pins to the corresponding index-enable nets.
>
> Jeff reminded me that having your servo thread in the wrong order can
> cause this too. The correct order is motenc read, motion command
> handler, motion controller, pid, motenc write.
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
