Expanding Timer1 counting range

[sycluap]

Not that I can't think out of the box, but I've asked around and tried whatever is possible, to display counting in LCD, not to display in LCD, to display only the final value, etc, but i still can't manage to get the timer to display in 1ms timing interval. I know that the PIC can continue counting by itself, but, even I try to make it display only the final value, but it still can't display the accurate readings.

Sorry for asking questions that might consider too easy for some others, but I am totally new in this. I need the timer to measure the human response time.

MY CODE:

'MAIN PROGRAM
'------------
ResetTimer:
GoSub SetReg
LCDOUT $FE, 1
Timer1H = 0
Timer1L = 0
MicroThousandths = 0
Thousandths = 0
Hundredths =0
Seconds = 0

Main:
LCDOUT $FE, $80, "Test Mode 1"
'LCDOUT $FE, $C0, "Visual Response Test"
If ButStart = 1 Then goto StartTimer
Goto Main

StartTimer:
LCDOUT $Fe, 1
LCDOUT $FE, $80, "Calculating..."
T1CON.0=1

Looping:
While PIR1.0=0
Wend
PIR1.0=0
Thousandths=Thousandths+1
If Thousandths>9 Then
Thousandths=0
Hundredths=Hundredths+1

If Hundredths>99 Then
Hundredths=0
Seconds=Seconds+1
Endif
Endif

If ButStop = 1 Then goto StopTimer
Goto Looping

StopTimer:
T1CON.0 = 0
LCDOUT $Fe, 1
GoSub GetValue

DisplayResult:
LCDOUT $FE, $80, "Time Elapsed"
LCDOUT $FE,$C0, dec2 Seconds, ".", dec2 Hundredths, ":", dec Thousandths
If ButStart = 1 Then goto StartTimer
If ButReset = 1 Then goto ResetTimer
goto DisplayResult


'SUBROUTINES
'===========
'Get value from Timer1 Register
'------------------------------
GetValue:
Timer1H=TMR1H
Timer1L=TMR1L
Return

'Reset Timer1 Register to Start from 1ms interval
'-----------------------------------------
SetReg:
TMR1H = $FC
TMR1L = $18
Return

Now, what is wrong with my codes? Correct me please.

[skimask]

Not that I can't think out of the box......

Big hints for you back in post's #5 and #7.

[skimask]

I think you're way over-doing this in the first place.
So, what you want is a program to start counting when you hit one button, and stop counting when you hit a second button, and display the time interval between the 2 right?

some generic code (you fill in the crap with real code)

'Set up all variables, registers, timers, etc... No interrupts

'display start message

'wait for start button to be hit, if it's not hit, don't jump back to the lcdout display command

'takes time to display and might miss a button push in the meanwhile

'if the button is hit, reset tmr1 to zero and start the timer

'start a loop

'display the current count (which will take longer than 1ms, but the next bunch will take care of that, again, the problem with displaying stuff during a tight count is that you will miss the exact time that a button is pushed and the count could possibly be off by 1 or 2 ms)

'if the tmr1 value is above 1000, add 1 to the ms counter and subtract 1000 from tmr1 (3 from tmr1h and 232 from tmr1l, or subtract 4 from tmr1h and add 24 to a subcounter to cover the extra 24us.  when that subcounter exceeds 1000, add another one to the ms counter

'check the stop button
'if the stop button is not pushed, jump back to the loop
'if the stop button is pushed, immediately save the tmr1 count, do the 'over 1000' math to keep the ms count and us count, and display the total

No, not real code, an outline as a guide.

Interrupts are nice, and DT interrupts and the Olympic timer are all you need, but apparently it's not enough to have almost 100% pre-written code made just for you.

This code is based on the fact that you keep timer1 BELOW a certain value and keep track of it as it counts UP. That way if you miss a count or two, you can always recheck it (i.e. tmr1 is 3000, you've missed 3ms, no biggie, just subtract 1000 from it 3 times and you're back on track). I built an OBD2 reader that's based off this to drive my virtual odometer, integrates time and speed. In the process of reading the OBD2 message, I miss a count here and there. No problem, just let the counter increase in the background and cover it up later. The intervals are short enough that I get a nice accurate reading (within 1/10 mile over a 263 mile drive 2 weeks ago) and long enough that the timer won't overflow in between readings.
Make any sense yet?

[sycluap]

Thanks for the guide. I have clearer idea now. Sorry for OVERDOING it. But at least Mr.Skimask and Mr.Acetronics is willing to help me out. Thanks.

[dw_picbasic]

Hello sycluap,
In your code, where you have initiate time counting:

Looping:
While PIR1.0=0
Wend


It appears that you are allowing the timer1 to overflow and then checking to see if the button has been released. This leads me to assume that you don't care if the button is released during the time Timer1 takes to reach rollover.
If this is the case, then is the use of Timer1 really necessary?
If you don't need resolution under a uSec then you might consider using the PBP3 "pauseus" command to create the 1 uSec.
1) Start button is pressed
2) pauseus 1 (delay 1uSec)
3) count0 = count0 + 1
4) if count0 = 65535 then count1 = count1 + 1; count0 = 0
5) check button ( if still pressed loop again)

In this case, you can capture ( minimum 1 uSec - maximum 4294 seconds).
For the math, just use count1 value as a multiplier of 65535
So, then if count1 = 40 you have (65535*40) = 2.6214 seconds accumulated in count1
and then you just add count0 value to that to get the total.


for loop1 = 1 to count1
for loop2 = 1 to 5
micro_sec = micro_sec + 13107
while micro_sec > 999
milli_sec = milli_sec + 1
micro_sec = micro_sec -1000
wend
while milli_sec > 999
sec = sec + 1
milli_sec = milli_sec - 1000
wend
next
next
Lcdout $fe, 1, #sec,":",#milli_sec,":",#micro_sec