01-03-2007 03:44 PM
01-04-2007 07:57 AM - edited 01-04-2007 07:57 AM
Message Edited by mvr on 01-04-2007 07:58 AM
01-04-2007 09:56 AM
Thanks for the explaination, I did take a look and it is good. However, what the differences if I call t_start = Timer() to start & t_stop = Timer()? Is it better or worse comparing with using Async. timer (regardless the Timer is never stop)?
Many thanks
01-04-2007 11:20 AM - edited 01-04-2007 11:20 AM
Message Edited by mvr on 01-04-2007 11:23 AM
01-04-2007 12:24 PM
Thanks again,
1. I did use Timer() without using User Interface and it works!
2. I aslo try clock() as you suggested, it is also work!
*) What happen if I use the program 24-hour operation? Can the clock() be over-lap? What you suggest (between the two)?
Note: In CVI8.0 Library/ANSI_C ... why it does not include all ansi_c functions (ie: Timer(), clock() ...) ?
Thanks again
01-04-2007 12:37 PM
clock() can be used for multiple days, I think the rollover for clock is around 49 days. For handling really long time periods you can look at the ansi time() or other c functions may be more useful. See this link for a list: http://www-ccs.ucsd.edu/c/time.html
#include <ansi_c.h> should get you access to all the ansi c functions from CVI. Timer() is not an ansi function it is a CVI function.
01-04-2007 01:12 PM