Ok, may I please ask what am I missing? Because I cant quite understand how to do it.

 

Ok, may I please ask what am I missing? Because I cant quite understand how to do it.

What happens when your first counter counts up to 7? Is that what you want it to do?

 

What happens when your first counter counts up to 7? Is that what you want it to do?

You mean the 1's? It resets at 7, which it isn't supposed to do until 777. The 10's resets at 7 also every time, not at 777

 

You mean the 1's? It resets at 7

Because that's how you wired it. When that counter counts to 7, you have it do a load (presumably of 0 because you have all of the clear inputs wired to a switch).

 

Ok Im not quite sure on whether I should use the load or the clear in order to make the 1's reset at 9

 

Ok Im not quite sure on whether I should use the load or the clear in order to make the 1's reset at 9

You can use either. My point is that you keep refusing to post a schematic of the complete circuit or the portion that we're discussing.

You've made an obvious mistake and, for some reason, it's not easy to make you see it.

 

OK I uploaded the schematic again. And this is the full schematic. The only section I left out is the connection to the 7 segment display

I think I'm supposed to link all three counters in a way that would allow the 1's and 10's to count up to 9 and 99 respectively until the count reaches 777. But I'm not sure how.

 

this is the full schematic. The only section I left out is the connection to the 7 segment display

It's still not complete. You're decoding 7 on the units counter and using that to execute a load. You must have the load inputs all tied LOW for that to work.

So look at the logic for the first counter. What happens when the counter reaches 7? You say you want the counters to reset to 0 when the count reaches 777, but that isn't what you wired.

EDIT: About your style...

We don't use "humps" with connection dots and using "humps" has gone out of style. If they're still teaching this at your school, that's another reason to look for something better.

 

Ok I think Im almost there. I removed the NAND gates from the loads of each counter and instead used an OR gate to connect the 3 NAND first and then connected that OR gate to the load of each counter. The result of this is that I got the count to reset at 779, meaning that only the 1's is now preventing me from resetting at 777.

 

Ok I think Im almost there.

Schematic??

I removed the NAND gates from the loads of each counter

The NAND gates never made sense. You were decoding 7, but the output of the NAND would be a LOW and load is active high.

 

Ok I think Im almost there. I removed the NAND gates from the loads of each counter and instead used an OR gate to connect the 3 NAND first and then connected that OR gate to the load of each counter. The result of this is that I got the count to reset at 779, meaning that only the 1's is now preventing me from resetting at 777.

Why did you use an OR gate? Please explain your logic in using that logic?

 

You want to decode the value "777" and do something if that condition is met. That is different than decoding a "7" on each digit and doing something when that is met per digit.

To make it reset to 0 and start counting over again, you can either use clear or load with the inputs all pulled low.
/mike

 

You want to decode the value "777" and do something if that condition is met. That is different than decoding a "7" on each digit and doing something when that is met per digit.

To make it reset to 0 and start counting over again, you can either use clear or load with the inputs all pulled low.
/mike

I was implying the same thing in my last post. To paraphrase @n1ist, doing something per digit, when each digit is equal to 7, is different than doing something when all digits are equal to 7.