Hello!
Don’t worry, were here to help.
Rest assured we do our best to make sure
every post has a good response.
Whether
we post it or double check information provided by other community members we
read nearly all discussion forum posts.
Additionally for better support from the community make sure you post
your question to the appropriate board.
In this case, you appear to be doing some data acquisition.
To open your question to a larger community
of DAQ users you might also consider posting your question in the
Counter/Timer board.
That being said, I found about 3 or 4 examples of “Measure
Period VI” in our example finder.
It
might help if you clarify which exact example you are referring to in this
case.
If you are using the “Measure
Pulse-Width or Period” VI that appears in the Data Acquistion->Counter palette,
there is an optional input at the top of the VI titled “time limit” – from the
help of the VI:
“
time limit is the period to wait for a
valid measurement. If
time limit is
-1.0 (default), the time limit is set to five s or four
times the range of the counter at the selected
timebase
(4*16,777,216/
timebase) for the DAQ-STC, whichever is larger.”
If you are not using this VI and have a more general
question, you will have to probably make a programming decision somewhere in
your code as to whether you want to continue waiting or break from some sub
VI.
The first think you’ll need to know
is which exact sub-VI is ‘stalled’.
Have
you enabled “highlight execution” in LabVIEW while viewing the block diagram to
see what VI is ‘hung’?
To enable
highlight execution click on the “light bulb” at the top of the menu bar.
As mentioned before – were happy to help!
Please let us know if you can provide us with
any additional information on the problem.
Travis M
LabVIEW R&D
National Instruments
You are off by about a factor of 100.