SSD flickers too much. How to fix the flickering?

The SSD in this project flickers too much. How to fix it?

For stable scan frequency, you'll refresh the multiplex display in an interrupt routine, independent of the other program actions.

Yes. I did that but it did not work. I used a 1 ms Timer interrupt and then placed all the SSD code inside interrupt routine but it did not work.

Please show how to use the timer, i.e., what timer interrupt should I use? There are delays in SSD code. Is it ok if I place SSD code with delays inside interrupt routine?

I did like this but it is still flickering. See attached file.

Is it ok if I place SSD code with delays inside interrupt routine?

Click to expand...

Delays in interrupt routines are a no no. You'll want to advance the scan position one digit on each timer tick and don't linger around in the interrupt code.

This is a really basic embedded programming concept, used in all microcontroller powered devices with multiplexed displays since decades. I presume you can figure it out by thinking a bit about the problem.

You'll want to advance the scan position one digit on each timer tick

Click to expand...

Yes, but how much should be the timer interrupt value? 500 us?

Yes, but how much should be the timer interrupt value? 500 us?

Click to expand...

Not really critical, I think. For faster scan rates, you probably want to modify the control sequence: disable the segments, switch the digit driver, enable the new digit code, to avoid crosstalk on undriven segments.

@FvM

Here is my interrupt code but it is not working. Still have the flickering. I tried, 1ms, 1.5ms, 2ms, 3ms for timer interrupt, but still it flickers.

Do you mean flickering in real hardware or in simulation?

Yes. It was flickering in Proteus and also Hardware. I fixed it. It is now working fine. I will post the code soon.

There's a problem with time consuming code for digit value calculation between digit activation and segment switching.

I didn't understand. Explain clearly. Here is new simulation. If Time/Temperature button is pressed it shows either Time or Temperature.

I didn't understand. Explain clearly.

Click to expand...

Explain what? I guess you fixed the problem by blanking the segment outputs before switching the digit, as already suggested in post #6.

It would be better to have complete simulations with *.cof and source code that can be debugged at source level, as in your previous posts.

I can't post the code FvM. I am sending the link to the project files through PM. Check PM.

To clarify, here's a segment of your code:

case 2:
PORTD = 0; // I added FvM's first suggestion here, which I assume you've already done...
PORTB = 0x02;
// ...because without it, the previous digit #1 will be output to #2 and cause flicker for as long as it takes to perform...
PORTD = CA[sec/10]; // ...this, of which the division in particular may be relatively slow
break;

Each digit needs to be lit at least 100x per second, or more, to appear constant to the human viewing it.

However, the actual digits displayed don't change 100x per second. Thus FvM's 2nd suggestion to move the math, like divisions, outside the ISR; and compute them at a slower rate, or only as frequently as needed. Let's say you defined a second array CB, and did this in your main code loop, or perhaps using a timer:

CB[2]=CA[sec/10]; // precompute digit #2

Now the ISR can set that digit by doing only a simple lookup:

PORTD = CB[2]; // instead of CA[sec/10]

And since each digit is now handled the same from the ISR's point of view, the switch structure can also be eliminated, saving even more time.

Now while you may not actually need to minimize time spent in your ISR for this particular project, in others you will - so doing stuff like this is good practice.

Thank you very much. I will try it and let you know.