LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

works in "debug" but hangs otherwise

I'm running a VI which reads some data from the DAQ system and writes them
to a file (as well as to globals). It's running on a computer which
isn't actually hooked up to the DAQ hardware (the computer which has the
DAQ hardware is inside a cleanroom and we're doing some development work
on another computer outside). It froze the system when we tried to run
it, so we eliminated all reference to the DAQ system (substituted in
constants; we're just trying to get the "write-to-file" part to work).
Now, it still hangs if we run it normally, but it executes just fine if we
run it in debug mode. Does anybody have any ideas what might be going on?

Mike Shear
WPI '00
0 Kudos
Message 1 of 3
(2,492 Views)
Mike Shear wrote:

> I'm running a VI which reads some data from the DAQ system and writes them
> to a file (as well as to globals). It's running on a computer which
>
> Now, it still hangs if we run it normally, but it executes just fine if we
> run it in debug mode. Does anybody have any ideas what might be going on?
>

I am assuming (dangerous I know) that by debug mode you are referring to
highlighted execution (the lightbulb is on). If this is the case then you
either have
some timing problem (add some wait ms in the loops) or you are having
collisions with the globals. Check to make sure that you are writting and
reading
the globals at the correct time.
Kevin Kent
0 Kudos
Message 2 of 3
(2,492 Views)
Mike,

We had a similar problem show up in our vi's. In our case the
vi's had worked fine in LabVIEW 4.1 and then this problem cropped up
when we went to 5.0. The solution, and it might apply in your case,
was to change the wiring. We were flowing data to both a subvi and a
case statement, which is fine, however version 5.0 and later automat-
ically multithread and the case statement and subvi were going into
different threads. Solution was we forced the case statement and subVI
into the same thread by not splitting the wiring but flowing through the
case and then into the subVI. We were using a TCP/IP connection ID's
but I'd bet the same type of problem could exist with file refnums.

If it is the same problem, just don't split the data you're
sharing and flow fr
om a starting point(maybe where you do an open) all
the way through everything in your vi that shares that data to some
ending point.

Good luck!

Mike Shear wrote:
>
> I'm running a VI which reads some data from the DAQ system and writes them
> to a file (as well as to globals). It's running on a computer which
> isn't actually hooked up to the DAQ hardware (the computer which has the
> DAQ hardware is inside a cleanroom and we're doing some development work
> on another computer outside). It froze the system when we tried to run
> it, so we eliminated all reference to the DAQ system (substituted in
> constants; we're just trying to get the "write-to-file" part to work).
> Now, it still hangs if we run it normally, but it executes just fine if we
> run it in debug mode. Does anybody have any ideas what might be going on?
>
> Mike Shear
> WPI '00

--

Frank Lane
(205)961-4677
lanef@boris.msfc.nasa.gov
0 Kudos
Message 3 of 3
(2,252 Views)