My teacher gave us a homework which includes 7 question and this is one of them.
DESIGN THE CIRCUIT WHICH CONVERTS 3 DIGIT BCD NUMBER TO BINARY USING 74184(BCD TO BINARY CONVERTER)
I couldn't understand what it means. Isn't the "74184" already a bcd to binary converter?
He didn't give any information about the "74184". I made some research and saw that I should use 6 of that converter to design a 3 digit converter but I couldn't understand clearly what should I do.

 

The data sheet shows you exactly how to hook up six of them to make a 3 BCD digit to 10 bit binary converter. What don't you understand clearly?

 

Welcome to AAC!

I made some research and saw that I should use 6 of that converter to design a 3 digit converter but I couldn't understand clearly what should I do.

If your research showed that it takes 6 to convert 3 BCD digits, it must have also showed you how to connect them.

The datasheet shows how to do 3 digits; plus 2 and 6 digits.

Is it supposed to be simulated in Proteus?
https://forum.allaboutcircuits.com/...igit-bcd-number-to-binary-using-74184.169238/

 

Welcome to AAC!
If your research showed that it takes 6 to convert 3 BCD digits, it must have also showed you how to connect them.

The datasheet shows how to do 3 digits; plus 2 and 6 digits.

Is it supposed to be simulated in Proteus?
https://forum.allaboutcircuits.com/...igit-bcd-number-to-binary-using-74184.169238/

No, just design. I have done this. Can you say if there's a mistake?

 

No, just design. I have done this. Can you say if there's a mistake?

Have you consulted the datasheet?

 

Have you consulted the datasheet?

I just saw it after when I did this. And I saw the schematic in a textbook which I found on the internet. They're nearly the same thing.

 

In logic design, "nearly the same" is usually another way of saying "not correct". Which is not to say that there can't be multiple ways to solve the same problem -- there often are.

Have you tried a couple of values to see if they work out? How about 888? or 511 and 512?

You are not always going to have someone to ask if your solution is right -- people hire engineers to solve their problems and if there was someone else that could just answer if that engineer's solution was right, guess who would have gotten hired in the first place? You need to develop the ability to test your own designs for correctness.

 

In logic design, "nearly the same" is usually another way of saying "not correct". Which is not to say that there can't be multiple ways to solve the same problem -- there often are.

Have you tried a couple of values to see if they work out? How about 888? or 511 and 512?

You are not always going to have someone to ask if your solution is right -- people hire engineers to solve their problems and if there was someone else that could just answer if that engineer's solution was right, guess who would have gotten hired in the first place? You need to develop the ability to test your own designs for correctness.

I believe there's a misunderstanding due to my weak English. I meant the images had very little differences visually. I added the two images and you'll understand what I meant to say. You are hundred percent right about the developing testing my own designs for correctness.The reason that I asked you about its correctness was I don't trust my knowledge about this course. I am trying to learn it. Thanks for your help.

 

How you learn to test your own designs for correctness is by testing your own designs for correctness. If you want confirmation, then what you need to do is describe what you did to test the correctness of your design and what you think it does (or does not) tell you. Then we can focus on helping you do better testing, if that's needed.

 

The reason that I asked you about its correctness was I don't trust my knowledge about this course. I am trying to learn it.

They look the same to me.

I don't see the point in just copying circuits from a datasheet. It's more educational for you to design the circuit to do the conversion. Texas Instruments implemented the converter using a ROM, but they explained the algorithm.

 

It was an interesting problem. I had implemented binary to BCD, but not BCD to binary.