How can I fix this error code -1300..

[Dennis_Knutson]

That explains the error you got from the LV driver. The first thing it does is send the ID? string to get the type of instrument. There's a few more things you can try. Check or replace the GPIB cable. Try a different instrument and see if you can communicate with it. If that works then you know your cable and GPIB board are OK. Check the address setting on the instrument. Try different commands to program the instrument. Contact Agilent or check the manual to see if there's any dip switches/front panel buttons/menu options on the instrument that need to be set.

[labview7-new_user]

Hi Dennis.. thank you for your Help. I have no problem of other instruments. The HP6629A take a command such as (ID?) not "*IDN?" command when I click query button. you have any hint or any suggestion that I can fix this problem? thanks

[Dennis_Knutson]

I'm confused. You said earlier "but there is no respond when I click query button . I type ID? into the sending string box." and now you say that it did respond to "ID?". The "*IDN?" is there because that has been the standard command for quite a number of years. The 6629 is pretty old and I know it requires "ID?". If it does respond, what is the exact response that you get? Failure to respond at all to a valid command with other instruments working okay seems to point to a bad GPIB interface on the 6629.

[labview7-new_user]

Dennis.. sorry for the confusion. the exact response I get is "HP6629A" when I type the string command "ID?" into string box. is this mean I have a bad GPIB cable or somthing else?
Best regards

[Dennis_Knutson]

What it means is that I see no reason for 662xA Example.vi not to work. With the correct VISA Session and Instrument Model selected to 6629A, you should be able to set the instrument to valid parameters. There is a subVI called 662xA ID Query. Try running that all by itself. It should return a value of 3 as the model type.

[labview7-new_user]

Hi Dennis..there is no problem when I run the subVI 662xA ID query. there is a problem if you are running the Example VI and getting start Vi., Please view my
screen shoot attachment 6629A example VI. Don't you think software related? I don't know what cause the error code:-1300
Regards

[Dennis_Knutson]

Well I feel stupid. You have no error. In the error out cluster, the status is false (the green checkmark). It appears that every time the subVI 662xA Error Query is run, it puts a value of -1300 into the code indicator and always puts something into the source text box. In your case, it reports No Error. The subVI can be modifed or you can just safely ignore the error code and message. You should only be concerned if the status Boolean is true.

[labview7-new_user]

Hi Dennis, thank you for your help.one more simple question, I try to download 662Xa intrument driver from NI.Some software is required to download to use this intrument such as IVI. I am new user to labview.
I download this intrument before. why it is required this time? should I remove the previous 662ax and download this one with IVI software. please give me some suggestion. thanks

[Dennis_Knutson]

It's not required unless you want to use the IVI driver instead of the one you already have. IVI stands for Interchangable Virtual Instrument. The IVI Foundation (www.vivfoundation.org)was formed several years ago to address the problem of having programs written for specific instruments and then having to replace that instrument for a different model or from a different manufacturer. Especially in the case for a different manufacturer, the test program would have to modified. Certain classes of instruments (scopes, dmm, power supplies, etc.) were defined and a common set of functions were determined. When you call into an IVI driver,
that common set of functions gets translated into the specific commands for a particular instrument. So, if you use the IVI class drivers in LabVIEW for a power supply from Agilent and want to start using one from someone else, you install the IVI driver from the different manufacturer, tell MAX you want to use that new driver, and you're done. No modification to your LabVIEW program is required. For some users, this is an enormous benefit. Personally, I don't use it much now because few of the instruments I use have an IVI class specification and the IVI Foundation has been very slow in defining and releasing new ones. There are also LabVIEW techniques to make interchangeable drivers without depending on IVI. Another downside to the LabVIEW programmer is that you can't modify the driver. An IVI driver is written in LabWindows/CVI so you would have to buy that and learn C programming to make any changes. My personal preference is to have a native LabVIEW driver if available and use th
e IVI driver only when time doesn't permit me to create one in LabVIEW.

So, it kind of depends on your preferences and future plans. You can go here for more information on IVI.