LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

execute other code during wait

I have a strange problem. I have a number of loops running all at once, all of which have wait times. Most of the time, my loops run independently of each other with no problems, but there are a few that hold things up when they are running and I do not understand why.
 
These loops are very similar. They all run every 100 ms, they all use DBitIn.VI, and they all create a partial lock up condition until:
A) the condition being checked is filled or
B) the loop times out.
 
The weirdest part of the problem is that the system is partially responsive. It responds to changes from other inputs and it responds to changes in my tab control on the main page, but it does not respond to button-triggered changes in my hidden full-screen tab control.
 
I've attached a small VI that has just the troublesome loop. I have tried using both waits and wait until next ms multiple, with no difference. You will not have the Global Variables used. My code is far too large to post here, and I have been unable to duplicate the problem in a small shell VI.
0 Kudos
Message 1 of 2
(2,429 Views)
  1. What does DBitIn.VI do, exaclty? Who wrote it? How does it talk to the instrument (Serial, GPIB, NI-DAQ, third party DLL, etc.)
  2. Why don't you use its error out terminal, it might tell you something.
  3. What is the priority level of DBitIn.VI? Is it reentrant? What is the execution system?

How many loops do you actually have?

 

0 Kudos
Message 2 of 2
(2,423 Views)