and the logic from the 10 second counter is the same as what you have (minus the extraneous components). I cascaded the counters differently, but your method should work (after you fix the floating in

u have (minus the extraneous components). I cascaded the

You need to examine what is the problem. You need to explain how it is able to fix the problem.
How can state 0110 appear before 0100? There are no "race" problems with 74192 that I am aware of in this situation.

i don't know , but there is a race problem ,can you provide some schematic solution's

 

i don't know , but there is a race problem ,can you provide some schematic solution's

What are the full part numbers of your ICs?

 

What are the full part numbers of your ICs?

4 from 74192 and 4 of 7447

 

4 from 74192 and 4 of 7447

There are about 20 different types of 7408 and 74192.
Read off the part numbers that are printed on the IC package, for example SN74LS08N.

 

There are about 20 different types of 7408 and 74192.
Read off the part numbers that are printed on the IC package, for example SN74LS08N.

DM74LS47 and SN74LS192 a thougt i can use anything in the simulation of Proteus this is what i used

 

i don't know , but there is a race problem ,can you provide some schematic solution's

Is this purely a simulator problem? Or are you seeing the problem on an actual breadboard?

The counters are synchronous, so there are no race/glitch issues.

 

DM74LS47 and SN74LS192 a thougt i can use anything in the simulation of Proteus

It doesn't make a difference for simulation.

 

Are you actually testing this on a breadboard?
What is the source of CLOCK?
Do you have 0.1μF and 10μF power supply decoupling capacitors on your breadboard?

 

Are you actually testing this on a breadboard?
What is the source of CLOCK?
Do you have 0.1μF and 10μF power supply decoupling capacitors on your breadboard?

no i onley use the stimulation

 

no i onley use the stimulation

Then the only conclusion I can make is that the simulation is wrong.

 

no i onley use the stimulation

Fix the floating input problem and remove the unnecessary resistors and capacitors. Then Proteus will have good data to work with.

This circuit is essentially the same as yours except I cascaded the counters the way they were designed to be cascaded:

You're stuck with using the symbols provided by Proteus. My simulator didn't have that component, so I made my own and positioned I/O's where they made more sense for counters and clocks.

A commercial counter it does have is dumb:

 

Fix the floating input problem and remove the unnecessary resistors and capacitors. Then Proteus will have good data to work with.

This circuit is essentially the same as yours except I cascaded the counters the way they were designed to be cascaded:
View attachment 318305
You're stuck with using the symbols provided by Proteus. My simulator didn't have that component, so I made my own and positioned I/O's where they made more sense for counters and clocks.

A commercial counter it does have is dumb:
View attachment 318308

what is the pins number for BO and CO

 

Then the only conclusion I can make is that the simulation is wrong.

am going to change the type of the the ic becouse i think there is deffrent types

 

hello

co is carry over
bo is borrow over
read the datasheet what the pins do.

bertus

 

hello

co is carry over
bo is borrow over
read the datasheet what the pins do.

bertus

thnx

 

what is the pins number for BO and CO

Proteus is using TCU and TCD, also referred to as CO and BO by Motorola.

 

Proteus is using TCU and TCD, also referred to as CO and BO by Motorola.
View attachment 318311

i did this connection at first then second counter start counting until 40 secounds but the and gate was correct and than when i connect the munits counter with the and gate it turn 1 one the 40 seconds , but the seconds keep counting unitl they reech 60 then turn 00 ,but also when i connect the up pin from the munits counter bitwine the the gate and the resistor and the capacetor it deast count at all i dont understand whats the problem with it and i dont thik its a cascad probleme

 

but the seconds keep counting unitl they reech 60 then turn 00

You shouldn't be able to see a count of 60 on the seconds counter.

Disconnect the AND gate on the 10 seconds counter and reconnect. Maybe you made edits that confused Proteus. I have had this problem with MultisimBlue and DigitalWorls. It only happened once on DigitalWorks, but numerous times with MultisimBlue. It seemed to forget that things were connected and I got into the habit of grabbing components and moving them around to make sure the wires were still connected. Don't have to worry about that now because MultisimBlue is no longer available.

 

because they evil

Do you have to do the simulation on a fifty-year-old computer?

 

Your simulator is not giving the correct result. Mine counts 00 to 59 correctly.