On Thursday 27 April 2017 17:44:59 andy pugh wrote: > On 27 April 2017 at 21:21, Gene Heskett <[email protected]> wrote: > > What have I done wrong? > > You might need to feed lut5timex.out to lut5timex.in2 to make the lut5 > logic state-aware.
In my mind, the state that counts is the state of the oneshot, called timex, which must be true, and its visible on the scope, going true as timex is fired by the edge => or connection from the pushbutton release. But nothing comes out of the lut5 even though the scope is telling me the truth table is satisfied. I think I was reading it right. The only way to get a display in the time frame of all this is to use the jog thread for the scopes timebase, but its possible for it to miss something that doesn't last a hundredth of a second or more. > You might also be able to roll the edge detectors > into the lut5 this way I had the encoder inputs as part of it which almost worked, but retriggered anytime the dial was touched while losing a count doing it. I had the oneshot triggering on the falling edge, which probably accounted for the one count loss. Since the pushbutton is asynch, I had to put the edge in to get one pulse only at button release. I'm going to "sleep on it" maybe I can see it tomorrow. Thanks Andy. 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) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
