Help Required with Logic

[Dr C]

Further to my post, I've been doing some more reading around the forums and found this. It's an example of a 7 bit register (values from 0-127). Would be great to try and use something like this in the level. Basically, If I could represent the movement of the light as bit patterns and have the output wired to the correct selector inputs.

I really think you're going down the wrong path here. Using binary registers is a whole lot of extra complexity for an inferior result (the difficulty of catching partly misaligned rows etc - I assume that eventually, beyond your first version you are going to want to do that).

Producing the 3 bouncing light pattern isn't hard to achieve, either with a selector (and some OR gates) or a sequencer. Directly comparing the row of lights to the row immediately under it is also pretty doable. And completely eliminates the misaligned row issue. I'll whip up a demo circuit of this stuff tomorrow so you can see what I'm talking about.

[shane_danger]

I really think you're going down the wrong path here. Using binary registers is a whole lot of extra complexity for an inferior result (the difficulty of catching partly misaligned rows etc - I assume that eventually, beyond your first version you are going to want to do that).

Producing the 3 bouncing light pattern isn't hard to achieve, either with a selector (and some OR gates) or a sequencer.

Completely agree.

I didn't put too much time into this yet, but I made the first set of three lights that move back and forth and a second row that tells a third row how many matches there are.

I still think the sequencer is the way to go. You just line up the batteries on the sequencer and connect them to OR gates. Changing the speed is as easy as adjusting the seconds per bar on the sequencer. I'll probably finish it up tonight... I'd like to see how it compares to Dr. C

[Dr C]

OK, here we go. First the pattern generator: Pattern generator.jpg
Since shane_danger is using a sequencer, I've used a selector. It's similar to the circuit I gave before, but with a bunch of OR gates so 3 lights at a time will be lit instead of 1.

Now to compare the lights: Light comparator.jpg
For simplicity I've only put 2 lights in this row, not 7 (the green and blue gates are for lights 1 and 2 in the row, respectively).

How it works: when the yellow selector is in its initial state, the lights will be purely controlled by the pattern generator (orange microchip). When the button is pressed the selector will go into state 2, and those lights remain on only if the corresponding light in the previous row is also on. So this will take around 22 gates for each row of 7 lights, but it's pretty easy to wire up.

[osullivp]

I guess we're all in different time zones hence I've been experimenting with stuff without the benefits of the recent posts from Dr C and others...Didn't want you to think I've been ignoring advice! Just for the record, I'm based in London (GMT)...You'll be pleased to know I've dropped the idea of using a register :-) Here's what I've got so far: stacker_prototype_v2.jpg. Here's how it works: -

1. Each chip to the left hand side of the lights contains a 1,2, and 3 light pattern generator based on the selector based design that Dr C provided in an earlier post. The selectors are attached to a single set of 7 lights (per row) via OR gates. So I've got rid of the multiple sets of lights per row I was using previously...
2. Each pattern generator has 3 states a) on and moving b) on and static c) off and reset.
3. Whilst I have included all three pattern generators in each row (and hence incurred some wastage), I think this is cleaner.
4. I then have a separate chip along the bottom containing a 16 port selector (15 ports for the rows plus I port for global reset).
5. Each output is wired to a) the activate port of the current row and b) the on but stay static port of the previous row. Thus as the button is repeatedly pressed, the rows are stacked as in the image.
6. After all the rows are filled the final button press resets the whole set.

Of course, this only covers the pattern generator side of things and I'm yet to implement the light test. I have a few reflections on the design: -

1. There are a lot of wires! For example, each row has 3 pattern generators connected to the 7 lights via OR gates. Some of the OR gates have 4 or 5 inputs. Also, the controlling selector (along the bottom) has 15 ports which are attached to three sets of 15 circuit board nodes (representing the 3 states per row). Would be good to understand if there is a clever way to reduce this since there is quite a lot of lag when making adjustments (even though I've set all the chips to not show wires).
2. I think there is a slight bug in my reset logic. In addition to turning the chip for the row off, it is supposed to reset the row so that when it is activated again, it always starts on the right hand side. It does work but sometimes resets to the left rather than the right. I need to look into that...I don't think it's anything too big but will have to be implemented 15x3 times!
3. Having come from a Java programming background it's a real shock to be working at such a low (essentially bit) level!!!

Many thanks for all your support.

[BabyFace]

sometimes with logic it's something that you have to except that there might be a number of wires. but to reduce wires and the size of your MCs when they are closed. you can use a number of tags and tag sensors from outputs to inputs istead of wires.

[Dr C]

Now that PSN's back up, if you want to drop me a line there sometime I'd be happy to come and take a look at what you've built so far.

[osullivp]

Yes, good news that the service is back up. Hope it stays that way! Will look you up next time I'm on...

[sp0ngyraver]

sometimes with logic it's something that you have to except that there might be a number of wires. but to reduce wires and the size of your MCs when they are closed. you can use a number of tags and tag sensors from outputs to inputs istead of wires.

I love wireless gates, you can even eliminate OR gates by just having multiple switches turn on the same tag sensor. This is especially useful when you have 6+ inputs for one switch, the OR gates with too many inputs will cause a TON of lag in create mode. I use wireless switches whenever it is possible/practical.