To answer some more questions, denouncing is not required, but I’d probably only try it if I used an MCU, otherwise it would be too hard-coded. Displaying the output is also not required, but hey, maybe one day I’ll want an RGB controller that lights up when you hit the buttons...
I wrote out the 16 states and made it into a circuit, but perhaps I did it wrong because it just lead to oscillation. I think it’s because the next state doesn’t depend on the current state of A’ B’, otherwise there’s no way to tell when a button has just been pressed. I think the next state depends on the last button that was held down before both were pressed together.If that sounds a little imprecise, it’s exactly what ronsimpson/kjeldgaards circuit gives. I was actually successful in getting a mostly working solution starting with this as a base, however it oscillates when both buttons are pressed simultaneously.
I think if I go back and use the ronsimpson circuit as the output for the extra columns in the truth table, I can get the right answer.
I wrote out the 16 states and made it into a circuit, but perhaps I did it wrong because it just lead to oscillation. I think it’s because the next state doesn’t depend on the current state of A’ B’, otherwise there’s no way to tell when a button has just been pressed. I think the next state depends on the last button that was held down before both were pressed together.If that sounds a little imprecise, it’s exactly what ronsimpson/kjeldgaards circuit gives. I was actually successful in getting a mostly working solution starting with this as a base, however it oscillates when both buttons are pressed simultaneously.
I think if I go back and use the ronsimpson circuit as the output for the extra columns in the truth table, I can get the right answer.