DT Elapsed Timer Question

[richard]

so is it likely to expect the elapsed timer to corrupt some of this processing or acquisition?

not really , i2c command is software timed but a synchronous process so not overly disturbed if pic is master.
eprom write command disables interrupts anyway so unaffected.
adc should be ok too conversion is done in hardware, acquisition time may be affected but not in a bad way [aq time is a minimum EXTRA WON'T HURT]
edit , I should qualify that statement with "unless you are doing some advanced sampling eg .like a fft "

its a trade off for elapsed timer accuracy with async processes worst affected

[richard]

if all you want is time keeping ,then a long var can used as an elapsed millisecondx10 counter and updated in an asm isr say every 10ms
for practically no overhead. its then pretty simple math to convert to H:M:S when needed for display

[rocket_troy]

Yeah, it's basically to generate a time stamp in say (1/10 sec resolution) for the data being sensed and packaged. The entire duration of the acquisition period won't be any more than 5 minutes and I'm quite happy to post process a single number into something more meaningful also. So, it sounds like I'll need to learn some assembly interrupt service routines Thanks again for the great advice - much appreciated!

[richard]

you may get some ideas here
http://support.melabs.com/forum/picb...ond-pass/page2

where I failed to convince longpole on the merits of timestamps over elapsed_int
I think there is a 24 bit asm version somewhere too but I can't find it .

[rocket_troy]

Richard,
so, the last link: take the stopwatch example (from a layperson's perspective), I can't see significant difference in overhead between say this and the elapsed timer example but I'm probably missing something? Like, am I correct in concluding there's a awful lot going on for when an interrupt is triggered like saving system variables and whatnot, or as in your stopwatch code, both the timer1 and timer3 interrupts call a PBP subroutine with assembler commands within and because of this, the system variables don't require backup and restoring after each interrupt activation? Apologies for what might be dumb questions, I'm trying to get my head around this.

Troy

[richard]

I can't see significant difference in overhead between say this and the elapsed timer example

correct there is not much overhead difference when pbp interrupts are used , main point was to show that time accuracy using time stamps is easy versus trying to fudge clock counts
so that elapsed_int could be used without modification and also to show that conversion to h:m:s is not too difficult

the main difference between asm and pbp interrupts is whats entailed in ReEnterPBP.bas code . its up to the user to determine if the application can tolerate the overhead or a more efficient method need be developed

[rocket_troy]

So, if I was to make an interrupt routine that only incremented a... say 16 bit variable - say 3 or 4 lines of assembler and that's all it did - would I be risking too much to not back up the system variables?