On 21.11.18 18:37, Nicklas Karlsson wrote: > > 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? > > The configuration is essentially a netlist. First step would be to > list the nets. Then if there are noo loops it would be a simple tree > with the output as the root for each tree.
The specified problem - avoiding a one-loop delay in communicating any output to its corresponding inputs - is infinitely simpler than that. The solution requires only that the output for each input precede the input in the addf sequence. As already described upthread, that is also relatively straightforward to check. All it needs is a list of loop-prior outputs, grown as each addf is encountered, and a check that each addf's inputs are all named in that list. Any exception is a one-loop delay, and can immediately be signalled as such. If sample files with netlists and addfs could be posted, then half a page of awk can do the job, I believe. Erik _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
