From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SubVI DAQ

Hi! I'm building a data acquisition system using LabVIEW and an old
ATMIO16E2 card. It is basically a collection of subvi's, each of which can
and may be run independently. The main vi just controls the priority and
timing of these subvi's and displays important inputs. Each subvi contains
daq vi's (some of the daq vi's, eg wave acqui, are common to more than one
subvi). They are all intermediate vi's and the iteration and clear terminals
are controlled from the main vi. The problem is that the main program
executes once with expected values from each subvi but then all acquisition
go to zero. This is obviously a problem with daq vi initialisation. I tried
re-initialising each daq vi on every subvi call and that works fine, but too
slowly for my l
iking. I was wondering whether it was a problem with
re-entrancy (because of common vi's in separate sub vi's). Is there any way
of solving it without saving each daq vi under another name? Is it possible
to keep subvis open after the first call, hence making re-initialisation
unnecessary? Any help would be appreciated.

Leon
0 Kudos
Message 1 of 1
(2,994 Views)