Timeline for Moore "01010" sequence detector
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 8, 2022 at 4:02 | answer | added | Pictsit | timeline score: 1 | |
Jun 23, 2018 at 18:32 | comment | added | Piyush Varshney | From state s6 with input 1 it will go to state s5 and not to s1......As sequence is 01010 | |
May 27, 2016 at 14:53 | vote | accept | PotatoBox | ||
May 25, 2016 at 22:22 | answer | added | PotatoBox | timeline score: 2 | |
May 25, 2016 at 17:10 | history | edited | W5VO | CC BY-SA 3.0 |
added 113 characters in body
|
May 25, 2016 at 17:08 | comment | added | W5VO | I think your input pattern is still playing tricks on you - I haven't seen a case where it isn't working correctly yet. Your first '0' on the input doesn't get latched because there isn't a positive edge for the flip-flop to clock on at t=0. Try not changing your data on a positive edge, it will be less visually confusing. | |
May 25, 2016 at 16:30 | comment | added | PotatoBox | I tweaked a little my input sequence and it looks like this: click. So my machine detects '01010101' combination. I'm not sure where's the error, state table (since it detects a little longer sequence than it should)? I also added output markers to every flip-flop, just to see the internal state. | |
May 25, 2016 at 13:52 | comment | added | W5VO |
Your input signal looks like it is 0011001100 , which definitely shouldn't activate the output.
|
|
May 25, 2016 at 8:47 | history | edited | PotatoBox | CC BY-SA 3.0 |
added 810 characters in body
|
May 25, 2016 at 8:20 | comment | added | PotatoBox | I'm more concerned about my K-tables, but I'll wire it and attach screenshot in a minute. | |
May 25, 2016 at 8:14 | comment | added | PlasmaHH | So you are asking if what you produced in xilinx is correct? Well, I am sure we can judge if it is without looking at it. Hint: It is not correct. Case closed. | |
May 25, 2016 at 8:10 | history | asked | PotatoBox | CC BY-SA 3.0 |