Re: time in us in OnTimer

Just forget about it. If you have such tight timing requirements, add a
hardware timer to your device, to generate interrupts at required times.
Even in that case you may not have opportunity to respond in time.

"Tio Cactus" <tomjey@xxxxx> wrote in message
news:1157527657.192532.272390@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Joseph M. Newcomer napisal(a):
If you need something that precise, build an external embedded system.
Counting in
microseconds is pretty meaningless in a value as large as you specified
(I can't tell what
you intended because of the odd use of commas) but you if are asking for
something to
happen 4,560,120,320 microseconds apart, or about once every 76 hours.
So accuracy to a
microsecond is almost certainly irrelevant.

Furthermore, the best you could *possibly* hope for would be 1000
microseconds resolution,
and you are more likely to consider yourself fortunate beyond belief if
you could get
anything accurate to within 15,000 microseconds, so again counting
anything to
microseconds is pretty pointless.

Youcould use QueryPerformanceCounter for very tiny measurements, which
means that you
could time intervals of as little as a few hundred nanoseconds, with a
variance of
hundreds of milliseconds (seriously!). So what are you *really* trying
to do?
joe


In Specification of transmission which I'm writing occur tiny interval
of time e.g. Tss (means the time which is required for a host to poll
one peripheral device) Tss= 43 us
Some other period are 55us or 320us. E.g program sometimes must wait
55us to start next action. The device which program simulates require
tiny measurements. Is some way to get this ??



.

Relevant Pages

  • Re: time in us in OnTimer
    ... happen 4,560,120,320 microseconds apart, or about once every 76 hours. ... could time intervals of as little as a few hundred nanoseconds, ... of time e.g. Tss (means the time which is required for a host to poll ...
    (microsoft.public.vc.mfc)
  • Re: time in us in OnTimer
    ... microseconds is pretty meaningless in a value as large as you specified (I can't tell what ... happen 4,560,120,320 microseconds apart, or about once every 76 hours. ... anything accurate to within 15,000 microseconds, so again counting anything to ... could time intervals of as little as a few hundred nanoseconds, ...
    (microsoft.public.vc.mfc)