LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

niDMM Read Multi Point.vi times out - niDMM Abort.vi hangs

Hi all,

I've got a weird problem.
In my app there are multiple calls to two NI-PXI4070 DMMS to acquire multipoint measurements (some 50 calls per run and between 500 to 15k points per measurement). Sometimes during almost every run a call to 'niDMM Read Multi Point.vi' returns a timeout error, allthough I have set the timeout value to much more than what was required for the specific measurement. In order to handle this, I'v included a call to 'niDMM Abort.vi' whenever a timeout occured. But this calls hangs forever.

Trying to stop this vi opens a window stating '..resetting your vi..'. But it needs at least more than several hours to finish :-((. If I kill LV I get a BSOD claiming that there where locked pages. This indicates to me that the call to 'niDMM Read Multi Point.vi' was not aborted.

What can I do?

The german support request page seems not to work and Munich has a holiday today.

Greetings from Germany!
--
Uwe Frenz
0 Kudos
Message 1 of 4
(2,860 Views)
Dear Uwe,

unfortunatally I found only one englisch discussion forum entry about this topic.
You will find the entry on the following link:
http://forums.ni.com/ni/board/message?board.id=320&message.id=23&requireLogin=False

Please post the VI in the forum so I want to take a look on it.

Best regards.

SebastianN
NI Germany
0 Kudos
Message 2 of 4
(2,842 Views)
Sebastian,

I'll do that.

But to keep this thread informed, the DMM-related part of my app is build on the example 'acquire & graph multiple samples.vi'.
Just replace the direct wires 'IVI-session' between the different subVIs with read/write to a global.

The whole app initialises my DMMs and creates a session for each of 'em first. Than it initiates several different processes that do their measurements (of course the access to the DMMs is rerstricted using named semaphores). When all those processes are done, the DMM sessions are closed.

I have a service request with SRQ: 227007.
Until now I seemes to run into even deeper trouble by upgrading all relared SW to the newest availabel.
0 Kudos
Message 3 of 4
(2,838 Views)
ps:
The whole app is much to big to be posted here. Not to tell that this is valuabel work ...
0 Kudos
Message 4 of 4
(2,836 Views)