Hi, Tim
This problem normally occured when your VI constantly switch back and
forth to the user interface thread. Probably you have some VIs,
functions or operations, which running in the UI thread:
- Property Nodes
- Menu Control VIs
- VI Server
- Thread Unsafe CINs or DLLs.
Be sure, that all of
I am trying to run a deterministic VI (LV 7.0) which reads data from a
DSP and displays it in a graph. The VI has to read the data within a
certain time or the DSP overwrites the buffer. I find that the graph
stops reading (for about .25 sec) when I click on its title bar (or
that of any other
Try this: separate the acquisition and display into 2 VIs, and share
the data with a LV2-style global.
Use VI server to launch the acquisition VI, hiding the front panel.
Then display the data in your display VI by polling the contents of
the LV2-style global.
Just curious: what hardware and
Hi Ben. thanks for the feedback. I will try this when i get a chance.
I am talking to a Motorola 56300 Dsp in a Delta Tau Pmac Motion
Controller card, (PC and ISA versions) over DPRam. I am using a DLL
supplied by Delta Tau. I wrote a LV driver to poll the Pmac card and
retrieve the data.
The
I have ran into this during other time critical data acquisitions
within a loop using win2K and found that if I put a wait function in a
loop with 0mS it works just fine if I move the mouse.
Sorry cannot help more
Hi jhoskins. Thnaks for the feedback. I tried this, but it made no
difference. My VI loops every 37 msec, and takes about 12-13 msec to
read the data (2048 x i32 array). I am already using Wait until next
ms multiple , with a value of 37 msec, to get the required loop time
(which I calculatem
Hi
First question, is your dll call reentrant or running in the UI
thread? It needs to be reentrant.
Splitting it into to seperate VI's should help. What I would try is
to have one VI with one loop running in the User Interface thread
waiting for a queue. Once it receives the queue update the
Hi Dean. Thanks for the ideas. The VI was not re-entrant (since it is
called in only one place, and has only one data set), but I tried
making it plus its subvis re-entrant, as you suggested. No difference.
FYI, I have observed that the problem only occurs within the VIs
memory space - e.g. if I
