> On Monday 19 November 2018 05:06:29 Nicklas SB Karlsson wrote: > > > What did you want to discuss with the addf function? > > > > I used it and think it works but what's more? > > > We need a utility that detects out of order addf's, each of which then > causes a one thread execution delay in the data traveling that path. > Data from a limit/home switch to use a real simple circuit, should be > present at the motion input when motion is invoked. But what if the > debounce addf is out of its assumed order? Placed below motion in that > thread?
With out of order you mean output from one thread is used in another thread? Otherwise I anywhere within period is ok. > But to use the jog dials on my bigger lathe as another example, which run > in a slower 200 hertz thread, theres at least 40 LOC between the dial > and the data applied to motions jog inputs. For each dial. Then data from slower thread is used update is done within same periodicity in higher priority? Or jitter around? Or you do not know? > I see that addf can take a 3rd optional argument "location" ... "location" is execution order? A well defined execution order could be a solution. Then there a simple cases with output from one used in other, simple criss cross and hard to sort out feedback. _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
