Search found 43 matches

Straight to the point:

PIC16F690@8MHz (internal osc).
setup_timer_0(RTCC_INTERNAL|RTCC_DIV_8|RTCC_8_bit);

I'm using this to generate 1khz pwm:

#int_TIMER0
void TIMER0_isr(void) // 2 ...

All right, I understood your explanation, thanks.

This explains also why somewhere in the code a:

printf("%4Lu",x);

would give less compiled filesize than:

printf(&qu ...

Hi, using compiler 4.124 and in the code I have:

if (stage == 0) t1++; // stage fast 160ma
if (stage == 1) t2++; // stage slow 80ma
if (stage == 2) t3++; // 40ma
if ( ...

Have you tried to power up the display without the PIC attached to data lines? It should display an entire row of black squares.

Just a quick checklist:

_ make triple sure every pin of your PIC ...

Updates (I'm updating with the intent that this topic could be usefull for other reader in the future):

I have found what was slowing down everything:

printf(lcd_putc,"%3.2wV", val ...

Yes, you are perfectly right, instructions have to be executed by something/somewhere, they do not come up from thin air.

I was thinking at some solutions, lowering the software pwm, demux the nati ...

Updates.

I'm "somewhat" mapping the execution time of the PIC, result pretty much match the timings given in the guide section.

I was quite satisfied by just 445 int32 += int32*int32, ...

Update:

To get the execution time of some instruction, I've resorted to this way:

enable_interrupts(int_TIMER1);
leap=0;
set_timer1(0);
...

Glad you have worked out a solution that suits.

It might be quite 'informative', to just run this part of the code in MPLAB simulator, and time it. The division by 64, should only take perhaps a do ...

Oh my!

You were.. ARE right!

To tell the truth, before posting I tried a slower PWM, like having an int after a full count of timer0, and it was interrupting/overflowing correctly every 32ms.. b ...

Ok, I was reclutant to post this, but untill now I haven't found an explanation.

I'm using timer0 (or timer1), every overflow I just toggle the value of a pin, so I can generate a pwm signal, nothi ...

Consider the difference between floats and fixed point numbers. You can calculate integer millidegrees much faster than you can true floats, and use %w to put the decimal where it belongs for display ...

If val_temp is coming from an A/D reading your LM35 you probably aren't getting more than 12 bits, and in most applications 8 bits will do fine. Properly scaled 8 bits gives better than 0.5% resoluti ...

and some more comments:

*0.609327, would immediately be several times faster.
Now remembering the comment about binary divisions, multiply by 256
So:

printf(lcd_putc,"Batt:%3.1LwC ...

and some more comments:

Float's are _not_ the 'format of values from sensors'. Numbers arriving from sensors will always be integers

Best Wishes

Right, but I was viewing a sensor from end use ...