Elapsed Timer Demo

[Eng4444]

This might sound strange for some of you and stupid for others... but i'll say it again, i do not have any previous knowledge in all this...

i already asked how to make it work for PIC16876A with a 4 lines LCD.

i got : 1. Set the DEFINEs to match your hardware.

2. Add CMCON = 7 if using PORTA

3. compile and run.

i'm thankful for this.. but at that time, i didn't pay attention to what was written in the first post! :

" Note2: They are written for use as the only interrupt in the program. If you need to use other interrupts as well, the program will have to be modified before it will work. "

then, i opened the .zip file and found...4 files!

ASM_INTS.BAS
ELAPSED.BAS
TEST_ELAPSED_LCD.pbp
Tets_elapsed_ser.pbp

So what to do with all these......? where to download each of them?....

[Darrel Taylor]

Naaa. Don't bother.

Try Melanie's Olympic timer instead (cheers Darrel, you keally know how to make friends - Melanie). It doesn't have the ASM stuff to worry about.

Or Paul's clock that doesn't even need interrupts.

DT
<br>

[MSapper]

Just wanted to say thanks, works great on a 16F690.

I was going to modify your program a bit, I have an application which uses count down timers, but I thought I should check with you, I noticed a copyright on the code.

Thanks,
Mike

[Darrel Taylor]

Hi Mike,

Glad it's working.

No problem with the copyright.
You're free to use it any way you want. Well, except posting it somewhere saying you wrote it

[shahidali55]

Hi Darrel,
I tried making a LCD clock with calender with the elapsed timer code, but the clock runs nearly 2 seconds slow per day.
I've made some modifications to the Elapsed_INT.bas.txt file so attached that also with my code ...
I dont know how to fix this error...
What should i do?... try tweeking the TimerConst or something???

[Darrel Taylor]

Hi shahidali55,

"tweeking the TimerConst" won't help. 1 count either direction will change the timing by more than you are off. @ 4mhz, 1 count will change the time by about 4 seconds per day.

At 2 seconds per day, it works out to around 23 PPM (parts per million), which is within the normal 50 PPM tolerance of the crystal. Not to mention the +/- 100 PPM variance due to temperature.

To get closer than that, you'll need to calibrate the crystal frequency. You may be able to use a small Trimmer Capacitor in place of one of the capacitors on the crystal. The size needed depends on your crystal, but 0-20pf will probably work.

Other than that, you could simply add 1 second every 12 hours. But if you build more units, that could be problamatic since they won't all be the same.

Here's a couple links to some more crystal info:
http://www.circuitcellar.com/library...ujanos91/3.htm
http://ww1.microchip.com/downloads/e...tes/00588b.pdf
http://ww1.microchip.com/downloads/e...tes/00949a.pdf

[shahidali55]

I dont think the problem is with the oscillator.
I noticed that the time loss takes place every time the hours increase...
Could it be some flaw in the code execution?

[thirsty]

Hi Guys.

I'm writing a program to control a drag racing xmas tree and time the 1/4 mile but I need .0000 (ie thousandths) second accuracy.

Looking a the ASM routine I'm wondering if I can just change the 100Hz freq to 1KHz by triggering the interupt more often.

Will this work?

Thanks and Regards

Thirsty

[Darrel Taylor]

That should work.

But .0000 would be Ten Thousandths of a sec. That'll be harder.
<br>

[geckogrotto]

Using a 12F675 I am getting wsave position request beyond ram_end errors how do I fix this?

[Darrel Taylor]

Using a 12F675 I am getting wsave position request beyond ram_end errors how do I fix this?

Open the ASM_INTS.bas file and comment out the offending lines.
The 12F675 only has 2 banks of RAM.
<br>

[shahidali55]

Sorry for posting that same message again...
I was getting an error message...
The attachment wasn't uploading correctly...