Re: nervous about command timing

On Thu, 30.09.04, Michael Thomas <Michael.Thomas_at_dynetics.com> wrote:

> timing is all wrong.  The time taken to run x scans should be
> x*scan_begin_arg, right?  There are x scans delayed to take place every
> scan_begin_arg ns.  But the execution time of my program does not seem to
> depend on x at all, and seems to track scan_begin_arg in us, not ns.  What's
> going on?

It is more like

total_time = nr_of_scans*time_for_scan
where
time_for_scan = scan_begin_arg + NUM_CHANS*convert_arg

hth,
Nils

-- 
Institut fuer Schweisstechnik und Fuegetechnik (ISF)      Pontstrasse 49
der RWTH Aachen                                           D-52062 Aachen

ISF - Welding and Joining Institute          fon:  +49 (0)241 / 80-96274
RWTH - Aachen University                     fax:  +49 (0)241 / 80-92170

Received on 2004-10-04Z11:52:16