HP4275a LCR meter

[zhshli8691@163.com]

I use a adapt of gpib-usb to control 4275a,the system works correct when it works with 4156 by anther software,so i think the driver and config about the gpib-usb adapt is correct,but when i connected 4275a by a gpib line,it seems no responce.what problems it may?i use 4275a-labview7 driver in labview to control.Help me ,thanks

sunfish

2007.5.15.13.04

[zhshli8691@163.com]

the adapter model is 823574 usb/gpib Agilent product,PC system is winxp,we have installed ics to control Agilent 4156c.I find that an IO config software had installed.what happened?

[MissyS]

Hi,

I'm not sure what problem you are running into. What is the 4156 that you are using? What do you mean by "when i connected 4275a by a gpib line,it seems no responce"? How are you communicating with it other than GPIB? Is the adapter a NI GPIB-USB or an Agilent GPIB-USB? What commands are you sending to the device? Are you using the LabVIEW instrument driver? Are you getting an error back from one of these VIs? What error do you see and what function returns the error?

Regards,

[zhshli8691@163.com]

thanks for response.

I use agilent usb-gpib 82375a convertor,i want to control HP4275a LCR meter and i use labview 7.1,max3.1.I installed NI-visa2.6 and agilent i/o suite14.0(as secondary),after set the ni-visa option enable the tulip.dll,I can see the 4275a in max under DEVICE AND INTERFACE miscellaneous as "GPIB0::17::INSTR".I can use ni-visa interactive panel to control the 4275a,but when i use labview vi,as "gpib write" or "gpib read",it has no response.

I have realise that,ni-visa is not based on IEEE488.2,and cvi as"gpib write/read" in labview its own is based on IEEE488.2,so i can control instrument by ni-visa,and can't in labview.I must find some ivi driver support visa.

And now,i use the labview control as its own gpib write/read vis,it return an error:can't find the driver or instrument,code 0 .

I have tried using ibic,but it mention me can't find the device too,maybe because it an IEEE488.2 tool,and visa isn't support it.

i wonder:

1,Is the guess right ?

2,if it is right,I should find some ivi to support my 82357a or 4275a,where i can find these ivis?

thanks

sunfish

[Dennis_Knutson]

You've got it backwards. NI-VISA fully supports IEEE-488.2. The problem you are seeing is that VISA supports the IEEE.488.2 driver for the controller that you are using. The low level GPIB functions in LabVIEW and ibwrt/ibrd in mAX, are functions for the NI GPIB controller. Since you don't have an NI board, you can't use the NI functions. I doubt that there is an IVI driver for the instrument but if the driver you downloaded has the low level GPIB functions such as GPIB Write and GPIB Read, you should be able to just replace them with VISA Write and VISA Read.

So, by spending the same amount of money for a controller from Agilent that you would have spent for the controller from NI, you will have to spend a few hours modifying code. There's got to be a lesson there somewhere.

Message Edited by Dennis Knutson on 05-22-2007 08:26 PM

[zhshli8691@163.com]

So i should use  NI convertor,and i can use ibwri/ibrd by labview its own?

thanks for your help,i will try ni product next time,use agilent product really spead more time

but i still have interest my problem,and i am  confused

帖子被zhshli8691@163.com在05-22-2007 09:39 PM时编辑过了

[zhshli8691@163.com]

ibic is an IEEE488.2 tool,why i can use ni-visa interactive panel communicate but when i open 488.2gpib interactive panel,it shows a "missing card error",and in the dos panel,I input "ibfind gpib0" to initialize the instrument,but shows "edvr".

All these tell me IEEE488.2 can't recognize the convertor and the instrument on gpib.

[Dennis_Knutson]

I think it makes the most sense to use NI products especially if you are using NI software like LabVIEW or CVI. As long as you stick with VISA though, either will work just fine.

Hopefully, I explain away a little of the confusion. Each GPIB board from different vendors has different hardware and firmware. This means that the low level windows driver for each board is different. The low level windows driver for an NI board has the functions ibwrt, ibrd. etc. The low level windows driver for an Agilent board do not contain functions of that name. They have functions that do the same thing but are called something else. When you do a VISA Write or VISA Read, the VISA api passes a message to the low level windows driver to perform some action. It's the low level windows driver that then does the actual GPIB communication. The GPIB functions on the LabVIEW palette are written to interface directly with the NI low level windows driver. That driver does not exist on your computer. Only the low level driver from Agilent.

[zhshli8691@163.com]

I am a little understand.see this passage from ni net.

You do not need Agilent VISA to communicate with your Agilent GPIB to USB Converter. You do need the Agilent I/O Libraries because they provide a driver for the HP/Agilent interface, but NI-VISA can communicate with the device without Agilent-VISA. To see the 82357A in MAX, you must have NI-VISA version 2.5 or higher and you must enable the VISA Passport Editor with NiVISATulip.dll checked.

What U say is correct,but i think the low level control will done by agilent io libraries,it has the low level driver of HP/Agilent product.When i use labview to control as ibwrt/ibrd,it just talk to the driver,and the driver talk to the instrument.The problem is that,now i can't use these orders based IEEE488.2  to control instrument.Is there a way more conveniencely to use labview control them? 

[Dennis_Knutson]

I don't think I said it differently from what you are quoting. The Agilent I/O library will do the low level communication if you have an Agilent controller and NI's library will do the communication if you have their controller. VISA (NI's or Agilent's) doesn't care which low level driver is installed. That is why VISA is portable and why instrument drivers are now written with VISA functions. There is little that you can't do with VISA. What specific functions on the LabVIEW GPIB or GPIB 488.2 palettes do you wish to use? Have you looked for the VISA equivalent?