On Sunday 11 August 2019 13:20:43 Peter C. Wallace wrote:
> On Sun, 11 Aug 2019, Les Newell wrote:
> > Date: Sun, 11 Aug 2019 18:11:42 +0100
> > From: Les Newell <[email protected]>
> > Reply-To: "Enhanced Machine Controller (EMC)"
> > <[email protected]>
> > To: [email protected]
> > Subject: Re: [Emc-users] PID feed forward
> >
> > Thanks Peter,
> >
> > That is exactly what the problem was. This hal file was originally
> > generated by pncconf and it connected the signal without driving it.
> > What is the recommended way to connect this? If I connect it to
> > motor.n.vel-cmd it trips a following error as it hits the index when
> > homing. If I leave it unconnected I don't have any problems when
> > homing.
> >
> > Les
>
> Ahh thats a bug in index handling so I guess you will need to leave
> the PIDs command-deriv unconnected until that is fixed.
>
> I really really wish that index handling did not cause a joint
> position jump. this is just plain wrong and hatches a nest of ugly
> patch-arounds. (though maybe needed for broken encoder hardware that
> clears its count on index) sigh...
>
> >> Yes, previously the PID command-deriv pin did not work so FF1 was
> >> always calculated internally by using DP/DT, Now it does work in
> >> the somewhat magic way it was intended to work ( calculate the
> >> velocity internally if the command-deriv pin is unconnected but use
> >> command-deriv if its is connected)
> >>
> >> So if you had your PID components command-deriv pin connected to a
> >> signal but the signal was not driven (connected to motions
> >> commanded velocity pin for example) You would get your present
> >> symptoms if you upgraded
> >>
> >> Peter Wallace
> >> Mesa Electronics
> >>
I stayed with master on all my machines, and I recently had to slow
things a bit, maxaccel and maxvel both in those axises that were
formerly fast, to get rid of the following errors that showed up while
homing.
I'll have to print out my ini's and hal's to dbl-check, but what today is
best practice?
The rpi3 on the big lathe can't be checked as the spindle is out of the
lathe ATM for a new upper counter shaft and bearings + belts, but the
rest of the machines have a 5i25 + bobs on The Little Monster 7x12
lathe, or a 5i25+7i76 on the 2 mills.
But I just discovered a much bigger problem with this testing stretch
install. Despite all my printers being marked shared, they are not, they
are invisible to the rest of the network here.
Does anyone have a clue how to restore that? I see a new user can print
list so I added me to that for all 5 defined printers, but zip results.
The printers list is empty on all the other machines, which are still
running wheezy if they are running at all.
> >> (\__/)
> >> (='.'=) This is Bunny. Copy and paste bunny into your
> >> (")_(") signature to help him gain world domination.
> >>
> >>
> >>
> >> _______________________________________________
> >> Emc-users mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/emc-users
> >
> > _______________________________________________
> > Emc-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/emc-users
>
> Peter Wallace
> Mesa Electronics
>
> (\__/)
> (='.'=) This is Bunny. Copy and paste bunny into your
> (")_(") signature to help him gain world domination.
>
>
>
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
