Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
WinXP Clock Loses Time; Will Re-Sync Cause Problems?
James Polly
Member
08-17-2004 10:01 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
We've recently upgraded to LabView7.1, and have recently noticed that our system clock is losing time at a much greater rate than it has in the past. The clock can be seen hanging every few seconds in the "Date and Time Properties" view where the date and time options of the computer can be set.
I may be incorrect, but I believe the system is unable to keep proper time due to the CPU intensive nature of our data logging VI's. We've decreased the data sample rates and resolution, as well as the displayed plotting rates of our collected data. This hasn't helped the problem. The plot of our CPU performance against time can be seen in Windows Task Manager, and our performance demonstrates a saw-tooth like curve o
f CPU usage, periodically saturating at 100% for a few seconds.
I'm interested in knowing if there is anything I can do to get my system keeping time correctly without any other time program intervention.
If I must incorporate the use of another time synchronization program like Thinking Man Software's Dimension 4 v5.0, how much risk am I running by having this extraneous program resynchronizing my clock while I'm logging data and executing VI's with time dependent loops?
I may be incorrect, but I believe the system is unable to keep proper time due to the CPU intensive nature of our data logging VI's. We've decreased the data sample rates and resolution, as well as the displayed plotting rates of our collected data. This hasn't helped the problem. The plot of our CPU performance against time can be seen in Windows Task Manager, and our performance demonstrates a saw-tooth like curve o
f CPU usage, periodically saturating at 100% for a few seconds.
I'm interested in knowing if there is anything I can do to get my system keeping time correctly without any other time program intervention.
If I must incorporate the use of another time synchronization program like Thinking Man Software's Dimension 4 v5.0, how much risk am I running by having this extraneous program resynchronizing my clock while I'm logging data and executing VI's with time dependent loops?
DOC-doc
Active Participant
08-17-2004 10:09 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
It means that your VI uses all the ressources of your system.
This kind of phenomenon can occur when the system is overloaded with loops that are NOT timed.
If you time your loops (either with "timed loops" or "wait.vi" or "wait until next ms.vi")this should stop
This kind of phenomenon can occur when the system is overloaded with loops that are NOT timed.
If you time your loops (either with "timed loops" or "wait.vi" or "wait until next ms.vi")this should stop
