GPIB-USB issue

[DanMad]

Hello,

I am using Labview 2016 and windows 10. I have a problem using a GPIB-USB-2 adapter from ines. I have installed its driver and windows recognises it in the "device administrator".

If I try to connect to the GPIB via labview it does not work, and give an error (see screen shot attached). What should I do to let Labview see my GPIB-USB device?

Thanks for the help

[CataM]

Does MAX recognize the GPIB ? 

In order to get more meaningful information about the error, right click the error out front panel indicator and select Explain Error.

Remember that the 488.2 driver has to be installed in order to be able to work with GPIBs. Open MAX and under the Software "pallet" you can check whether or not you have the already mentioned driver.

[DanMad]

Hello,

I partially solved the problem. A driver of the GPIB-USB adapter was missing. Now I have a different problem. When I write to the GPIB, there is no problem. The problem is when performing the read operation. No error is reported, but nothing is read, just spaces. I tried several combinations of functions but all give the same result. Attached you can find the code I am using.

Thanks for the help.

PS. Max does not see the GPIB, but the NI-VISA interactive control does. It gives the same problem of empty read.

[Minions]

Is there a reason that it needs to look so complicated to control an instrument?  Do you need to use the base primitives?  If you have NI-VISA loaded, you should be able to use these which are cleaner and a little more simplistic.

[DanMad]

Hi,

I was using those vi just because I did not know there were others.. 🙂

Thanks for the test vi using VISA. I tried running them but it still gets only spaces. It gives also an error code: "1073676294". Attached there is a screenshot of the output.

I tried all the VISA resources that are present in the I/O menu. GPIB0::5::INSTR (in the screenshot) is the only one that does not give time-out error.

[Minions]

The next question is, "Are you sure that the instrument with which you want to communicate can handle the '*IDN?\n" query string?  What is the instrument part number and brief description at GPIB address 5?

[DanMad]

Hi,

That is a very good question. The instrument is a pic-and-place machine from Naples Coombe. How can I know if the machine can handle the IDN query? I tried also other standard query and also tried to send random strings to maybe generate an error message, but nothing changed.

About your second question:

"What is the instrument part number and brief description at GPIB address 5?"

How can I get that information? I thought the only way to get that was the IDN query.

[crossrulz]

---

@DanMad wrote:

How can I know if the machine can handle the IDN query?

---

RTFM (Read the manual).

[Minions · Accepted solution]

Dan,

Seeing how your device does not respond to "*IDN?\n" try these queries below and see if you get a response from your instrument. NOTE: the \n is the newline character (aka Line feed) and not the two characters "\" and "n".

ID?\n

If that doesn't garner a response from your instrument, then try

U0X\r\n

If neither of those gives you a response (error responses do not count here), then your setup probably needs to be reviewed.

[DanMad]

Hi Minions,

thanks for the fast reply. I Tried the commands you suggested. I used the LabView constants for carriage return and line feed to be sure everything is correct. I am attaching the code for reference. I get no answer from the device and so I will proceed checking the hardware for issues. Thanks again for the help.