Single event data logger wth LCD

[med2007]

Too right 10 seconds is for test purposes.
I have tried your code skimask and it does do something..however a bit strange, is there a way of posting scope waveforms on this forum? I think my scope will produce either jpg or bitmap, I'll check it out.
Rgds
Mike

[skimask]

Too right 10 seconds is for test purposes.
I have tried your code skimask and it does do something..however a bit strange, is there a way of posting scope waveforms on this forum? I think my scope will produce either jpg or bitmap, I'll check it out.
Rgds
Mike

I'm guessing here...'cause I don't see ALL of your code...just a couple of ideas...

You're probably seeing jitter caused by ON INTERRUPT.

The ON INTERRUPT is probably being triggered at different points in the code and might have a different amount of clock cycles before it actually gets into the interrupt code.
The number of cycles it takes to get to the interrupt code might be different between the 'dummy = dummy + 1' part and the 'goto main' part.

WDT on? If it is, might be timing out causing the PIC to reset, resetting all the variables, therefore screwing up the timing overall.

EDIT: Forgot to mention that using DT's Fast Interrupt routines would most likely solve any interrupt latency issues.

[med2007]

Thanks for that I'll check it out...meantime is it allowed to have a GOTO inside a subroutine to exit that routine before the RETURN?

Or can I just say IF so-and-so THEN RETURN?

Rgds
Mike

[skimask]

Thanks for that I'll check it out...meantime is it allowed to have a GOTO inside a subroutine to exit that routine before the RETURN?
Or can I just say IF so-and-so THEN RETURN?
Rgds
Mike

It's allowed and it'll compiled, but it'll probably bite you in the rear later on 'cause you'll probably end up with a stack overflow that you'll have a hard time tracing.

The second option works just fine, the IF/THEN-RETURN type thing that is...