I have made this circuit on Proteus, a simple BCD to 7-segment display:
But the segments for 6 and 9 are not completely lit. What could be the potential reasons? The decoder IC is CD4511 and a common cathode display.
I have made this circuit on Proteus, a simple BCD to 7-segment display:
But the segments for 6 and 9 are not completely lit. What could be the potential reasons? The decoder IC is CD4511 and a common cathode display.
The CD4511 decoder is working as intended, see page 4 of its datasheet shown below:
There are decoder-drivers like the MC14495 that have tails on the outputs but these are eye-wateringly expensive since they are vintage parts from back when.
You could possibly use something like a 4056 with a buffer to overcome its sub-mA current source limit. A latch would allow you to multiplex multiple displays off of a single 4056.
As Vir mentioned, the chip is working as designed. But you can get the desired results your looking for with additional logic. Thy this:

simulate this circuit – Schematic created using CircuitLab
Keel all the other connections the same. The caveat is you might lose some of the "fancy" features of the decoder. Or maybe not; I don't have time to check. Try running the simulation. If so, you can correct the situation with additional logic.
This is quite normal and matches the behavior of 7447 etc, as well.
If you need a real part that does the decoding function and provides “tails” on the 6 and 9 you could consider the 74HC247, which lcsc has in stock for small quantities, albeit from a less-known source. The LS version was more widely available. Those parts are designed to work with common-anode displays.
It’s far more usual these days to use an MCU to provide a decoded output, allowing complete freedom as to which segments are illuminated (for example you could decode to hex characters where the b is like the 6 in your decoder- or a pattern representing a symbol such as the degrees symbol). Just a few lines of code.
This is a US-American/British way to write this numbers.
The Datasheet gives you a representation of this encoding. In Europe and other parts of the world the people are using simply a bit different way of writing.
6looks likeband9looks likeq. If only one of these was the case and the user knew, then9and6wouldn't get confused even when they're upside down. That might be the origin of this font. Or saving energy. \$\endgroup\$