ME OLVIDE DELA FOTO

Glad it works.

You can also use 100 ohm resistors instead of 220 ohms for the displays, as they only light up 1/10 of the time.

To see the difference, you should reprogram the original display scan generator with C11.

Remember when I wrote that you should have used CC displays?

You're making the same mistake as back then: the output of {7 segment display A} is inverted compared to when you use {7 segment display C}.

Illuminating segment 'a' is equivalent to 1111110 for CA displays and 00000001 for CC displays.

If you use the AND 1 instruction, that's correct for CC displays, but you should invert '1' for CA displays.

You can also indicate that you're using CC displays and invert the outputs as I did in your example, while still using CA displays.

I also removed 4 times {MOV display 0xFF}

I have not tested it in real, that upto you.

Good luck

I tested that and everything works fine. I don't even know what your problem is because I don't see anything wrong in that photo.
If you have a problem, describe it so I don't have to guess.

My setup uses CA displays and a 20MHz crystal. You'll need the latter if you want to multiplex displays, as LDmicro uses a duty cycle, which significantly slows down program execution.

But always use #PORTx if you want to multiplex displays; it's >20 times faster and prevents shadowing in the segments.

I used your program and only changed the crystal frequency from 16MHz to 20MHz.

So you need to use a different crystal or resonator at 20MHz.

Why is the crystal frequency in your program set to 16MHz?
I always start from the data that is provided to me.

The reason you see those mirror images is because there's a delay between the processing of two or more lines, and if you use sensitive modern LEDs, you'll see that.

You can find several threads on this forum about that problem.
In 2015, I once posted a program that partially solved the problem, but with today's much more sensitive LEDs, you'll see it again.

Cause: the display is turned on while the data (a...g) from the previous display is still on the outputs, and because there are several lines in between, it takes a while, but you can still see it.

There's nothing you can do about that, except use a PIC with a 32MHz clock or use #PORTx.

#PORTx was a huge relief when Ihor programmed it; you can now use more than 10 displays without seeing those symptoms.