LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

not responding

I could easily covert the timed loops to whle loop to see if the problem goes away.  I was kind of wondering about the DAQmx create timing source block.  I have intentionally put the resurve hardware command in line with the analog input and digital output tasks.  However, this is not an option with the timing source block and it is using a counter off of the same hardware.  If the timing source did not get initialized prior to the attempted execution of the first timed loop, would this be a problem?  I guess the loop would not do anything until the timing source initiallized.  Interesting idea about the LabView version.  I used to use version 7 but can't remember if there was any correlation between the problem and the version switch.
0 Kudos
Message 11 of 14
(786 Views)
I can get the problem to go away by switching to the built-in timing source. Since it looks like you set the counter to 1kHz and that's the same as the built-in, you may not see any difference. I've never used the timed loop with a DAQ board timing source so I don't know why it doesn't work. All I can do here is run a simulated DAQ device and I don't think simulated mode will work at all for an external timing source.
0 Kudos
Message 12 of 14
(781 Views)
Interesting!!!  I started using the DAQ board timing source because one of the vi's I was working on required a 10kHz sample rate.  It seemed easy to set up so I kept using it even with the slower sample rate.  I will have to give that one a try.  Thanks!
0 Kudos
Message 13 of 14
(775 Views)
Just an interesting discovery.  I put the create timing source, AI and DO setup blocks withing a sequence structure prior to any other commands.  This solved the problem.  Program runs fine every time.  I appreciate the efforts of everyone that tried to help me.  I just wanted to share what I found.  Have a happy holiday to all !
0 Kudos
Message 14 of 14
(729 Views)