Thanks for at least bothering to read the whole thing haha. I'm guessing by "the other AND input" you're referring to that gate below? That's a NOT gate, which takes only one input. If that's not what you were saying, would you mind clarifying a bit?
Comment has been collapsed.
My bad. It was a NOT. After reading I checked the pics and saw the AND in the chip so I totally forgot.
Gee I don't know where the problem is. The only idea I have is the delay, but I don't agree with you about your explanation: if B is 1 and you switch it to 0, B will propagate to AND and to NOT. Say this works in steps (I don't know if that's the case, I guess it is), first propagation AND gets B and NOT gets B. But AND requires the two inputs, and during that "step", even though current output for the NOT is (current B)', the second port for the AND is still receiving the old NOT value that was 0. So at that moment, you would get a 1, and after propagating in the next cycle the NOT you would get B and B'.
Comment has been collapsed.
While not being sure if that's the way propagation delay works, that's exactly how I thought of it but I'm still coming to the same conclusion.
Let's say, in the first cycle, AND gets B (or "0") and NOT gets B ("0") at the same time, just like you said.
At this moment, the port of the AND gate that's connected directly to the button has the value of B that is "0", but the NOT gate is still outputing the old signal B' that was "0" so after the first cycle, the AND gate has a "0" from the button and another "0" from the NOT gate, so 0 AND 0 = 0 is the output after the first cycle (of course if we're delaying all of the gates, the output value of AND would also be delayed but let's assume it's not since we're just using that value to trigger something and not putting it through other gates). The NOT gate still sends the old value "0", but that's still a value the AND gate can manipulate, and as long as one of the inputs of an AND gate is "0", the output should be "0" (I think this is the part we couldn't agree with each other).
Now in the second cycle, the NOT gate processes the current B value that is "0", and sends the AND gate the value "1", and the other port of the AND gate connected to the button remains the same since the change there was complete in the first cycle, so we get 0 AND 1 = 0.
I don't know, I am not studying electronics or anything, and I might have mistakes in my way of thinking.
Comment has been collapsed.
I'm sorry, my explanation was wrong and you're correct: no matter what, when toggling the button off the AND has to output 0.
Have you tried keeping E pressed (the toggle only button) and checking if this problem lasts during the whole time? I remember having some problems with that.
Comment has been collapsed.
I have, it doesn't really change anything.
Oh well, maybe I should make an account on the Wiremod forums and ask the question there. If I get an answer over there I'll write here in case anyone wants to know what the problem was. Feel free to comment here if you have an idea or a question to ask.
Comment has been collapsed.
Can we start by asking what do you want to do? i dont understand what is the use of doing what you are doing, i might be mistaken but what you are doing will always give a 1? Aka= Push button, no matter if 0 or 1 it then gets inverted so the and always gets a 1 no matter what... there are easier ways to send a 1 i dont understand.
Comment has been collapsed.
I was building a toggle (I know there's already a gate for that but I was just making my own), and one part of the whole mechanism wasn't working properly so I did a little debugging and I simplified the problem to that thing in the picture. It is currently not serving any other purpose. I'm just trying to figure out why it's not working the way you would expect, it should always give out the value 0 but it's not. There might be an easier way to do than what I'm doing of course, but I'm just trying to understand what the problem is here.
Comment has been collapsed.
I finally got an answer in the Wiremod forums. It's not about gate delay or anything. Apparently, in Wiremod everything has to be done one at a time, so whatever you do, one input of the AND gate changes its value before the other one can, and whichever gate gets wired to the button first has the priority. In this case, apparently I first wired the NOT gate to the button, and then the AND gate. So the NOT gate was the first gate to be affected by the change, so when its output was changed to "1", the signal that went straight to the AND gate from the button would still be "1", so 1 AND 1 = 1.
In case anyone wants to see the whole discussion:
Comment has been collapsed.
16,298 Comments - Last post 34 minutes ago by MLD
82 Comments - Last post 4 hours ago by WaxWorm
56 Comments - Last post 6 hours ago by Carenard
1,811 Comments - Last post 7 hours ago by ngoclong19
72 Comments - Last post 9 hours ago by Reidor
545 Comments - Last post 11 hours ago by UltraMaster
41 Comments - Last post 11 hours ago by ViToos
116 Comments - Last post 5 minutes ago by xurc
8 Comments - Last post 22 minutes ago by StrangeAsAngels
48 Comments - Last post 27 minutes ago by ManlyMeatMan
17 Comments - Last post 49 minutes ago by someonequeer
92 Comments - Last post 1 hour ago by Axelflox
72 Comments - Last post 1 hour ago by eeev
9,531 Comments - Last post 1 hour ago by NoYeti
Okay, here's something that's been driving me crazy. I've been working on something with gates and stuff and realized something wasn't working right. Then I figured out where the problem was but I still don't know what's causing it. I've quickly put together something to demonstrate the issue:
http://i47.tinypic.com/t4tr48.jpg
So I have a toggle button, with values "1" for on and "0" for off. The button is connected to an AND gate and a NOT gate which in turn outputs it's value to the AND gate. So basically what the AND gate should be outputting is " B AND B' ", where B is the value of the button and B' is the inverse of B. The problem is it should only output the value "0", however, when turning off the button, for a very brief moment, the AND gate outputs "1". You can't see this using a screen because it happens very quickly so I used a prop spawner. This second screenshot shows the watermelon spawned by the spawner just after the button is pressed:
http://i45.tinypic.com/33dzgir.jpg
At first I thought it was the gate delay but if that was the case when the button is turned off you would expect B' to switch to "1" a little later than B to switch "0", so it would still output "0". Any ideas on why this might be happening?
Comment has been collapsed.