True, however teaching circuits without the "interference" of timing is usually easier.We'll get there eventually, have to start with the basics and work our way up.
True, however teaching circuits without the "interference" of timing is usually easier.We'll get there eventually, have to start with the basics and work our way up.
True, but for more advanced circuits it's preferable to utilize pulses rather than constant on and off. As such it was necessary this early in the piece to introduce timing.True, however teaching circuits without the "interference" of timing is usually easier.
I have another series that goes into the practical applications of logic, such as doors, gravity lifts, etc etc. This series is more for people who want to understand the theory behind it. The why things happen rather than just copy what i'm doing ta-da you've built it. For those that just want to learn how to build this or that, the other series is for them.I think you could save yourself a lot of extra words and video just by teaching people what each logic block does and then how to make a pulse limiter, an RSNOR memory cell, a clock circuit, and maybe a T flip-flop.
tl;dr
I do not know whether or not this one may be too high for this project of teaching the basiscs, but you should feature how to build an OR from NOTs and (N-)ANDs, and vice versa. This would in turn allow one to compress an RS-latch into 3 blocks(in cases of an inverted r input even 2 blocks).we're back with memory circuits!
I'd prefer XOR and odd parity gates over that, but whatever, not my game.who knows, maybe we'll just add in NOR and NAND blocks into the game.
Please we need this! Currently it take 4 blocks minimum to create an XOR, there is no reason this can't be made with as simple logic as all the other gates:I'd prefer XOR and odd parity gates over that, but whatever, not my game.
That is the definition of the odd-parity gate, if the one describing logic gates defined one.XOR activation: ConnectionsON% 2 == 1
Confused by what your point is here, 3+ input of XOR gate is standard defined as odd input high, Wikipedia:That is the definition of the odd-parity gate, if the one describing logic gates defined one.
When an odd-parity gate is defined, the XOR gate is defined by: NAND(Connections,ConnectionsON) & OR(Connection,ConnectionsON)
The reason being, that there are several ways to have the 2-input XOR, that produce different truth tables, when there are more than 2 inputs.
A | B | OR | NAND | OR & NAND
0 | 0 | 0 | 1 | 0
1 | 0 | 1 | 1 | 1
0 | 1 | 1 | 1 | 1
1 | 1 | 1 | 0 | 0A | B | n | n%2
0 | 0 | 0 | 0
1 | 0 | 1 | 1
0 | 1 | 1 | 1
1 | 1 | 2 | 0
In essence:Confused by what your point is here, 3+ input of XOR gate is standard defined as odd input high, Wikipedia:
"Strict reading of the definition of exclusive or, or observation of the IEC rectangular symbol, raises the question of correct behaviour with additional inputs. If a logic gate were to accept three or more inputs and produce a true output if exactly one of those inputs were true, then it would in effect be a one-hot detector (and indeed this is the case for only two inputs). However, it is rarely implemented this way in practice.
It is most common to regard subsequent inputs as being applied through a cascade of binary exclusive-or operations: the first two signals are fed into an XOR gate, then the output of that gate is fed into a second XOR gate together with the third signal, and so on for any remaining signals. The result is a circuit that outputs a 1 when the number of 1s at its inputs is odd, and a 0 when the number of incoming 1s is even. This makes it practically useful as a parity generator or a modulo-2 adder.
For example, the 74LVC1G386 microchip is advertised as a three-input logic gate, and implements a parity generator.[8]"
XOR gate - Wikipedia, the free encyclopedia
Also NAND(Connections,ConnectionsON) & OR(Connection,ConnectionsON) works in starmade right now, it is not true that it only works when odd parity is defined. This is how you make XORs right now, hence why I said " Currently it take 4 blocks minimum to create an XOR".
I'm still incredibly confused by what you are trying to convey. Yes, the top is a one hot detector, and the bottom is a odd parity gate, but what does that mean in the context of your original reply? Where you just stating facts or you trying to make an argument? I feel like the subject or preposition was lost in translation or something.
I'm still incredibly confused by what you are trying to convey. Yes, the top is a one hot detector, and the bottom is a odd parity gate, but what does that mean in the context of your original reply? Where you just stating facts or you trying to make an argument? I feel like the subject or preposition was lost in translation or something.
I've never seen XOR defined as high for not getting high inputs (but at least one, which is what I think you were saying). I'm not sure I see the practical application of a logic gate that makes sure that not all inputs are high, and at least one is high, however it wouldn't hurt to add that as well. I didn't realize this is what you were talking about because I didn't look closely at the truth table.My argument was not just adding an XOR, but adding several blocks, that behave like XOR with 2 inputs, but behave differently for more than 2 inputs, as XOR for 2 inputs can be defined in several different ways, that only differ, when expanded to more than 2 inputs. This will avoid people expecting different behaviour from an XOR with more than 2 inputs. [I personally define XOR forh N>2 as (n>0 & n<N) [n=number of active inputs, N=number of inputs], this definition however clashes with many other definitions of XOR for N>2]The top one is odd-parity, neither of both is a one-hot detector. The bottom one has the following truth table:
A B C | R
0 0 0 | 0
0 0 1 | 1
0 1 0 | 1
0 1 1 | 1
1 0 0 | 1
1 0 1 | 1
1 1 0 | 1
1 1 1 | 0
I don't use it very often, as most of my uses of XOR only have 2 inputs, thus making the extendable definition irrelevant. However, it can be used to detect whether or not a multi-bit integer is at a value, that may cause over or underflow[0-1=N; N+1=0 //N=(2^n)-1 //n...number of bits], so long as one does not care which case it is. In addition, it can be used to check whether or not an array of sensors all have the same output, by feeding all of them into the expanded 4gate, and negating the output of the extended gate. This 5Gate XNOR is essentially a check for equality of all inputs, regardless of their value.I've never seen XOR defined as high for not getting high inputs (but at least one, which is what I think you were saying). I'm not sure I see the practical application of a logic gate that makes sure that not all inputs are high, and at least one is high, however it wouldn't hurt to add that as well. I didn't realize this is what you were talking about because I didn't look closely at the truth table.
One hot is easy to add,
XOR odd parity activation: ConnectionsON% 2 == 1
XOR one hot activation: ConnectionsON == 1
Looking at google, it seems your interpretation of XOR is non existent, I've never encountered this definition at university, and people only mention the above two definitions, but I didn't realize this was the definition of what happens when you expand the four block XOR gate with (OR + NAND). It is still pretty simple to implement.
XOR 4GATE Expanded: (ConnnectionsON % Connections) != 0
I'd like to know what you use that one for.
I don't use it very often, as most of my uses of XOR only have 2 inputs, thus making the extendable definition irrelevant. However, it can be used to detect whether or not a multi-bit integer is at a value, that may cause over or underflow[0-1=N; N+1=0 //N=(2^n)-1 //n...number of bits], so long as one does not care which case it is. In addition, it can be used to check whether or not an array of sensors all have the same output, by feeding all of them into the expanded 4gate, and negating the output of the extended gate. This 5Gate XNOR is essentially a check for equality of all inputs, regardless of their value.