LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

program time not stable

Yes I tried it with your last example. No improvement and no errors.

I thought about he same, that the computer clock is not stable.

Thanks a lot for your help. I talked to my boss and he said I should by the more expensive power supply with a build in pulse module, but let me know if you have another idea for the problem.
0 Kudos
Message 11 of 17
(936 Views)
One thing...do you guess that the CPU speed is not accurate enough or the speed how Windows handle the program is not accurate?
0 Kudos
Message 12 of 17
(928 Views)
It would be more Windows related..
 
However.... if you wanted to try a more exotic trick, there is something you could try.. 
 
Are you using a multi-core PC and Labview 8.5? 
 
RayR
0 Kudos
Message 13 of 17
(911 Views)
I have a Intel Core 2 Duo processor and LabVIEW 8.5.1
0 Kudos
Message 14 of 17
(905 Views)
The other technique I'm thinking of consists of having two loops (two execution threads) where one thread is concerned with turning OFF the power supply and the other one to turn it ON.  Each execution thread would be tied to a CPU core and a notifier would tell the other thread when it can execute.  Each loop would execute one iteration and wait until the other loop sends a notification to proceed.  The delay would be between sending the command to the instrument and before sending the notification.
 
I'll look for the discussion on this topic.
 
RayR
0 Kudos
Message 15 of 17
(896 Views)
Hey,

It was a good idea and try with the duel core processor, but the problem is, that the computer on which the program should run has no duel core processor.
Is there any other idea to provent this problem?

thanks
0 Kudos
Message 16 of 17
(863 Views)

Timing precision with Windows is not easy...

I'll have to think about that..

0 Kudos
Message 17 of 17
(845 Views)