Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA: (Hex 0xBFFF0015) but is responding to *IDN?

I am using NI 488.2 GBIP controller

Whenever i try to commmunicate with the device it shows timeout error

While using Instrumentation and automation mode it responds to *IDN? but whenever I try any other command it again shows the same problem

When I try to open GBIP analyser it prompts GBIP+ analyser not connected

 

0 Kudos
Message 1 of 9
(4,884 Views)

You are not providing enough information. What is the make and model of the instrument? What is a command (other than *IDN?) that you have tried? I hope you are not expecting a response when you issue a command that does not end with '?'.

 

Also, the analyzer function is only available for '+' type controllers - ie PCI-GPIB+. Use NI-Spy to monitor communication.

0 Kudos
Message 2 of 9
(4,881 Views)

The instrument connected to the sysem is Agilent 4156C semiconductor analyzer

I am not getting anything on NI spy as well.

I am not able to understand that analyzer mode is only for +type cards

Can zou let me know how can I get data from Agilent analyzer to labview using PCI-GBIP

I am new to GPIB so please bear with me 

0 Kudos
Message 3 of 9
(4,842 Views)

other command whcih i am providing is

FORM:DATA ASC; SOUR:FUNC  SIN; SENS:DATA? 

for whcih it shows timeout error 

0 Kudos
Message 4 of 9
(4,840 Views)
I've never used that instrument but I suspect it just isn't in a state that will return a measurement. You could try the driver.
0 Kudos
Message 5 of 9
(4,827 Views)

how   to install the driver

i am quite new to this area please help 

0 Kudos
Message 6 of 9
(4,822 Views)
For the LabVIEW part, place the unzipped folder in your instr.lib folder. You'll also have to get the dll from Agilent.
0 Kudos
Message 7 of 9
(4,820 Views)
do i need to place the dll in the same directory
0 Kudos
Message 8 of 9
(4,816 Views)
No, you don't have to. The Agilent installer will probably place it in some default location and the LabVIEW wrapper will probably expect it there but you can place the dll anywhere you want and tell the LabVIEW functions where you have placed it. This is no different than any other LabVIEW VI with a Call Library function Node.
0 Kudos
Message 9 of 9
(4,814 Views)