And why not?

He's not using surface mount LEDs. SMT are the only RGB LEDs I've seen with 6 terminals.

 

Will it keep good time?

Touché.

Add a crystal and two more caps if that is a consideration. I think the TS mentioned a 555 based clock, but maybe that was a different thread.

Edited: I see he said 4060, which, like the PIC, can use an optional crystal.

 

I use an old free version of Eagle (4.13r1). The pull-up resistor can be 10k.

I'd use counter chips to make mod 60 and mod 12 counters.

For the minutes/seconds LEDs, I'd use the LSD counter and convert the outputs to decimal. For instance, using CD4029 as the counter (because I happen to have some) and CD4028 BCD to decimal decoder. That handles LEDs representing 0-9. Then I'd use the MSD counter with another CD4028 to decode 0-5 and use that to drive 6 banks of 10 LEDs.

For minutes (or seconds), 2 CD4029 and 2 CD4028.

Dennis, What do you think about using 4013 between 4017s to toggle signal?

 

What do you think about using 4013 between 4017s to toggle signal?

I wouldn't go down that path.

 

The problem is that one LED will always be on whenever a CD4017 is enabled. So you can't use the Q0 output when the counter isn't disabled.
It was how you labeled the LEDs.
RGB LEDs will complicate the circuit I posted. I could use a single current limiting resistor for all 60 LEDs. Plus I'm switching both the anode and cathodes of the LEDs. You can't do that with RGB LEDs.

What do you thing about using 4013 to toggle signal between 4017s?

 

I wouldn't go down that path.

Sorry, double posted. Why not?

 

Sorry, double posted. Why not?

No reason to respond I think I know why, going to try NAND gates.

 

single LED on is boring....

if i was going to do this, i would use MCU, something like ESP32 so it can use WiFi to get real time from the internet. the only other IC would be some sort of led multiplexer ic such as MAX7219 or whatever. then you can have not just precise clock that never drifts but also various effects... like instead of simple increment to next LED, how about comet zooming all around before stopping at the next led. or display inverted... or as pie chart... or whatever... or add photoresistor and you can have automatic dimming so that LED is not disturbing your sleep.

or... how about no multiplexer IC. just use addressable LEDs. then you can have any color you want...
and for those afraid of SMD, there are though hole variants like WS2812-F5 / WS2812-F8 , APA106, PL9823 ...

 

Sorry, double posted. Why not?

I think it's more appropriate to use counter chips (to implement mod 60 and mod 12 counters) to make a clock.

 

Will it keep good time?

It will keep good time if you use AC Line frequency for the time base.

 

In a nutshell 60 rgb leds, blue-seconds, green-Minutes, and red-hours.

I'm not sure you've considered all of the ramifications of using the same LEDs for hours, minutes, and seconds.

 

I'm not sure you've considered all of the ramifications of using the same LEDs for hours, minutes, and seconds.
View attachment 367358

And does the hours LED move along every 12 minutes? So that it completes a whole revolution of 60 LEDs in 12 hours?

 

Thanks again Dennis, I'll look into your idea!

But don't use Eagle.....use KiCAD.

just sayin....

 

I'm not sure you've considered all of the ramifications of using the same LEDs for hours, minutes, and seconds.
View attachment 367358

Yeah i get it. So at 12 o'clock the first led is red while leds cascade blue around the clock in seconds, when it reaches 12 oclock the red will turn violet for a second and second led will turn green. I get that at 12:05 the corresponding led will be yellow, and white for a second. My thought process is to use cd4060 for seconds/minutes/hours and 6 4017s for seconds, 6 4017s for minutes, and 2 4016s for hours if I can get them to work dammit. By the way dont let my user name fool you, Im a retired electrical contractor and it was a nickname my co-workers gave me.

 

Thanks for your input. Ultmalely I want to build a 12 hour clock with 60 rgb leds, blue -seconds,green -minutes, and red hours. Im old fashioned and retired, so no microproccessors please, Ive got a lot of time on my hands. I stumbbled on the idea when I unpacked my scope and was looking for a circuit to play with it on, then I ran into 4017s and was intantly enamored. Im going to be using CD4060s for my time base and 4013s attain the correct frequency. A lready have an oscillator runnig on my circuit thats running prfectly. The circuit I posted is to help me better learn the 4017 and if my idea is plausable Sorry to bore you with all this but hopefully you'll better understand where Im comming from. Thanks again.

Aside from the time base,decoding and driving the display are the big challenges, with vastly different levels of complexity and parts counts.

 

The beauty about electronic clock circuits, is that literally there are several dozens of circuit variants.
You already have received a wealth of suggestions. Thus the only thing I would add, is that you should definitely consider multiplexing your display, to keep the amount of wiring and discrete components to a sane level. The example in post #30 by DL234 is a good one.

 

My thought process is to use cd4060 for seconds/minutes/hours

You mean separate clocks for seconds, minutes, and hours instead of having seconds drive minutes, and minutes drive hours?

6 4017s for seconds, 6 4017s for minutes

It would be helpful if you showed a schematic or block diagram for this. If you drive the LEDs using the circuit in post #9, 6 isn't enough. If you multiplex them as I did in post #30, 3 should be sufficient. But, you can't do that because you want to use RGB LEDs.

BTW, how are they wired? Common anode? Common cathode?

2 4016s for hours if I can get them to work dammit

How can analog switches be used for hours?

 

Thus the only thing I would add, is that you should definitely consider multiplexing your display, to keep the amount of wiring and discrete components to a sane level. The example in post #30 by DL234 is a good one.

multiplexing is simple but regardless if using single IC like in post 48, or several ICs like in post 30, there is going to be a lot of traces to take care of. the lowest part count and simplest routing is to use addressable LEDs. then PCB layout becomes trivial:

 

the lowest part count and simplest routing is to use addressable LEDs.

As I suggested in post #39.

 

exactly...

keeping good time using crystal is ok though it will still drift a bit. to completely get rid of drift one can use internet time or atomic time receiver.
atomic clock receivers are not expensive but are antenna is directional. and since every household has internet, that is why i proposed using controller with WiFi built in. an overkill but low cost and low parts count...
plus plenty of muscle to do anything fancy for special occasions like birthdays, New Year, whatever...(heartthrob, comet, party mode...)