LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Resource name not shown in labview

Hi all,

I am trying to connect the driver to the USB, but the resource name is empty, NI MAX can identify the USBdevice properly with its name.

I have reinstalled MAX two times and a compatible version is installed.

 

MehranAA_0-1629820583601.png

 

The usb device I want to connect is USB-62000H, and is seen in NI MAX:

 

MehranAA_1-1629820583619.png

 

 

thank you in advance J,

Mehran

0 Kudos
Message 1 of 10
(1,516 Views)

Do you have the correct type of I/O control to see the device? (Or even the correct control type from the IO pallete?) - If you can't see it in LabVIEW, you probably haven't got this correct yet.

- of course you haven't you've opened an I/O session to a DAQ card (USB-6002 is a DAQ device).
You want a DAQ session (and maybe a DAQ Assistant) - press <ctrl + space> then type "DAQ" and click on DAQ Assistant (in the block diagram and go from there.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 2 of 10
(1,491 Views)

The USB-62000H seems to be the Chroma 62000H power supply. Most likely the VISA sessions type for your constant is configured too specific for you to see the USB Instr resource.

 

Right click on the constant and then select "Select VISA Class->IO Sessions->Instr" which should allow you to select any VISA Instrument resource, or "Select VISA Class->IO Sessions->USB Instr" to let you only select USB Instrument resources.

Rolf Kalbermatter
My Blog
0 Kudos
Message 3 of 10
(1,479 Views)

Doh 😐 I had this ready before and thought I better check it was not a DAQ or something like that.
(Could be the wrong control type if a System session has been created too.)
VISA types.png

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 4 of 10
(1,474 Views)

Hi James,

 

As you saw the device is a Chroma power supply and not a DAQ.

0 Kudos
Message 5 of 10
(1,445 Views)

@MehranAA wrote:

Hi James,

 

As you saw the device is a Chroma power supply and not a DAQ.


Hi Mehran,


In which Rolf's post and my second post should have you sorted by now!

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 6 of 10
(1,442 Views)

@MehranAA wrote:

Hi James,

 

As you saw the device is a Chroma power supply and not a DAQ.


Did you get it to work with the recommendations James and I both posted? Or did you not have time to test? The difference in device that you tried to access is a minor oversight and in his defense I have to say that my first reaction was the same. Your problem description wasn't very specific and only mentioned the device name in the last sentence and its name is close enough to the NI DAQmx USB box that a casual glance could dismiss that as a typo.

 

It's understandable in a way. When a user comes here he has this "huge" problem with something. He has everything in his head and usually knows exactly (and sometimes not) what components are involved and thinks everybody else should know it too, since it is his one and only problem at the moment and the world of course can't have others at the same time. So he mentions whatever comes up in his mind assuming that everybody else magically must be able to fill in the blanks, since it is clearly all in his head and everybody else just must know these things too.

 

And the best part is of course, since LabVIEW is a graphical programming language, an image of the diagram tells a forum user everything he must know to see the problem (NOT)! But we can't see the configuration of that VISA constant and hence have to start to guess and propose all kinds of possible solutions. If you had attached the VI instead, all the guesswork would have been unnecessary. 

Rolf Kalbermatter
My Blog
0 Kudos
Message 7 of 10
(1,435 Views)

Hi James, Sorry I had a 2 post block on my account (first day of using this account :)). I meant that my description was not clear and later Rolf corrected it. My problem still is not solved, I will explain below with enough details this time (hopefully).

0 Kudos
Message 8 of 10
(1,416 Views)

Hi Rolf,

You are right, My explanation was not complete.

I tested yours and James solution, but the problem is not solved, in the IVI resource name, the .

When I create a "Visa resource name" constant, I can see my device (Chroma ATE DC power supply, 62150H), but the connection to the device driver does not match, (as it is a VISA class and the driver needs IVI class). Today I tried re-installing/updating all drivers (the IVI drivers provided by Chroma in NI website), but that did not help as well :(.

any ideas or suggestion what I am doing wrong or how I can fix this?

I am using LV2020.

and NI max is still showing the Chroma 62000H device, as it should.

I also contacted Chroma, maybe there is something I am missing that they might be able to help me with.

Anyways, I appreciate your help and will update here with the solution when I find it.

Best,

Mehran

0 Kudos
Message 9 of 10
(1,412 Views)

Hi Mehran,
You need to setup the IVI driver in MAX to see it appear in LabVIEW.
you have not configured the IVI driver, only the VISA driver.
you could use typecast to convert an IVI session to a VISA session but not the other way around.
you need to finish configuring MAX - scroll down in MAX to find the IVI instrument support (or if it's not installed, install it!)

(I haven't got NI IVI installed, so I can't help anymore, but I know that where the issue is - it's in MAX)

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 10 of 10
(1,407 Views)