LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ghost devices appearing in VISA nut not NI-MAX

Solved!
Go to solution

This is my first time using a NI USB O-scope and I have noticed that seemingly every time I run a VI a "new device" shows up in the I/O control VISA drop down..

 

But it is not a new device just a copy of the ONE SINGLE USB-5132 attached with an incrementing number.

 

Is VISA creating a new instance of this device every time I use it? Why?

GhostDevices.png

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 1 of 4
(2,337 Views)

Are you closing the VISA reference at the end of your program?

 

If you quit LabVIEW and restart are they still there?

 

mcduff

 

 

0 Kudos
Message 2 of 4
(2,327 Views)
Solution
Accepted by topic author RTSLVU

Well there goes your signature line.

 

NI SCOPE sessions (which use a VISA flavor underneath SPECIFICALLY IVI) persist while the calling vi remains in memory.   However, unlike most VISA implementations NI SCOPE sessions do not check for an open session by name and reuse it.   This in "Desired IVI behavior" because of the requirement for Open session string in IVI init.

 

CLOSE your IVI sessions with the appropriate driver close.vi.  And stop using the abort button.

 

And yes, those orphaned IVI sessions are consuming memory... tsk tsk.


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 4
(2,302 Views)

@JÞB wrote:

CLOSE your IVI sessions with the appropriate driver close.vi.  And stop using the abort button.


I knew that using the abort button was going to catch up with me some day. 😛


@JÞB wrote:

Well there goes your signature line.


There was no code to show, and it was NI Example code to begin with so it has the Ni-Scope close in it.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 4 of 4
(2,277 Views)