HP 8903B USB GPIB not Work

[GasGas]

By the way, I need help.

I received today after many months the Agilent 82357 GPIB USB adapter to be able to connect my HP8903B Audio Analyzer to the computer so that I can use Pete Millet software. Next to the adapter came a CD-ROM containing the Agilent IO Libraries Suite Version 15.5 software. I installed this CD-ROM on 2 different computers, one with Windows 7.0 and another with 8.1 Pro. On the computer with Windows 7.0, the Agilent VEE Pro 9.2 software was installed and on the computer running Windows 8.1 the software with VEE Pro 9.3 . On both computers, I get the same error message when opening the Pete Millet software:

https://www.dropbox.com/s/ftg5b9rbuhrtrdp/Sem%20t%C3%ADtulo.jpg?dl=0

Using the HP 8903 SPCL configuration, I have verified that the HPIB port number is 28, the same as I used to configure the Agilent VEER Pro 9.2 and 9.3 software.
 
I also checked the internal dips switches on the HP 8903, and they are configured as follows:

https://www.dropbox.com/s/0qm3tna5ifjv3h1/20180313_190849_resized.jpg?dl=0

This is the 8903 information in function 21.0 (HPIB)

https://www.dropbox.com/s/wiycp6g0lxyzbpo/20180313_204240_resized.jpg?dl=0

I believe the configuration of the HP 8903 is right, why can anyone help me with this problem? I was trying all day and I could not.

Thank you in advance.

[coromonadalix]

hum that was discussed here, theres lot of fake usb adapters around,  there a thread here about that ... maybe you got one ??

[GasGas]

How could you be sure? I have an HP 66332A power supply that also has HPIB. Is it possible to test this adapter on this power supply using another test program?

[Stray Electron]

  Absolutely. Get the programming manual for the power supply and give it a go. Most of them are very straight forward to program and to query from.  But if your adapter came from China I think it's safe to say that 1) it's a fake, 2) it's bad.   There is a LONG thread on this forum about the Chinese copies of the HP USB to HPIB adapters.  Usually they work but I wouldn't take bets as to how long they'll last.

[GasGas]

Could you help me in this task of testing the adapter with my power supply? I have absolutely no programming knowledge at all, my idea was to use the Pete Millet software with the 8903B, figuring I would be able to do it.

[Johnny10]

Have you read this thread on DIY Audio?

http://www.diyaudio.com/forums/equipment-and-tools/208692-hp-8903b-hpib-gpib-read.html

Sometimes it is a lot of trouble getting the software to recognize the 8903B

I use his software with NI PCI card Win7 64bit.

[GasGas]

Yes, I already read this topic and even in it I checked the issue of the internal configuration keys on 8903. My knowledge in this part is very small and I need the help of the users of this forum to get the software to work or at least to know if the interface USB GPIB is faulty.

[Johnny10]

Have you used NiMAx to talk to 8903

Sure the dip switches are correct?

[GasGas]

Sorry, but what is NiMAx? Any software?

Regarding the GPIB address, I am 100% sure that it is 28. Exactly as in the attachment.


Please check the link that I sent the photo with the position of the dips switches.

[Johnny10]

Device name should be "Audio_Analyzer"

[Johnny10]

I can't get to the back of my unit to check but if you just enter 21.1 and HIt SPCL button .

[GasGas]

Device name should be "Audio_Analyzer"

I am not able to change / include a new name in the software IO Libraries, only in RunTime this is possible. At what location of the IO Libraries software is it possible to change or include the name of the audio analyzer?

[GasGas]

I can't get to the back of my unit to check but if you just enter 21.1 and HIt SPCL button .

can you please send a photo of the display of your 8903 then use the option 21.1 SPCL?

so I can confirm that the dip switches on my 8903 are correctly configured.

[Tony_G]

21.1 SPCL will tell you what the current GPIB address of the 8903B is. Pete's software expect that the unit will be at 1428. The 14 indicates that the GPIB adapter is a National Instruments one (they're configurable but the defaults show this). If you're using an 82357B and the Keysight IO Library Suite then your adapter will be 7.

For example, my 8903B is at address 8. So to access it using a default NI card the address is 1408 and the default Keysight adapter is 708.

There should be an instrument manager app installed that you can configure things with - The details are located at the bottom of this page:

http://www.pmillett.com/hp_8903_software.htm

Running that app you should be able to assign the appropriate address to the audio_analyzer variable.

TonyG

[LazyJack]

There are some pitfalls getting this instrument work. Watch this: https://youtu.be/_FtJh3N4FK0

[GasGas]

Yes, i have a 82357B.

I made some progress, found out how to change the device name for Audio Analyzer in the IO Libraries software, but I still have not been able to do the same.

I will leave some prints on the screen with the IO Libraries configuration, hoping they can help me by informing me where I am wrong.

https://www.dropbox.com/s/gv9mfjr0930xavf/20180314_081754_resized.jpg?dl=0

https://www.dropbox.com/s/em8hryeyazas4wf/20180314_081820_resized.jpg?dl=0

https://www.dropbox.com/s/dpkn93mw9qyv5hc/20180314_081938_resized.jpg?dl=0

https://www.dropbox.com/s/wo48535tu8qlsnq/20180314_081959_resized.jpg?dl=0

[Tony_G]

Quick comments from the images I looked at:

1. You're changing the alias for the device not setting the variable value
2. The GPIB Primary address should be the one the instrument is set (21.1 SPCL will show this)
3. GPIB Secondary address should just be 0

For #1, there will be an app installed when you installed the VEE Runtime called "IO Explorer" - Run this and you'll see the "Instrument Manager":



Right Click the configuration and select "Add Instruments":



Fill in the dialog that pops up appropriately:



You should now be good to use the intrument named "Audio_Analyzer" in VEE Apps.

TonyG

[GasGas]

I changed the configuration, I guess I did it the way you did, but it still does not work.

Please check the image.

https://www.dropbox.com/s/4ktcob5mzjnsfwh/Sem%20t%C3%ADtulo.png?dl=0

[Tony_G]

Couple of things:

1. Is the address of the unit actually 28? You none of your images show the address screen from the 8903B - type 21.1 and then the SPCL key.
2. Can you communicate with it using the Keysight interactive IO tool?

TonyG

[GasGas]

I'm sending photos from the HP8903 panel in SPCL 21.1.

https://www.dropbox.com/s/0p6qwqmfufcjro5/20180314_173737_resized.jpg?dl=0

I believe there is no communication in the IO Libraries application, please check the image below.

https://www.dropbox.com/s/kx0n877u30m9l1e/Sem%20t%C3%ADtulo%201.png?dl=0

[Tony_G]

Ok give me a few minutes as I just got home and I don't have the Keysight IO Libraries stuff running on my machine (I moved over to NI adapters).

I'll run up a VM and get some screen shots.

TonyG

[GasGas]

Thank you so Much!

[Tony_G]

Ok I just set this up and I noticed that the name "Audio_Analyzer" wasn't correct.

If you run, say FR_v2_B.vxe then you'll see this:



From that image you can see that VEE is looking for an instrument called "Audio Analyzer" - Note the space not an underscore between Audio & Analyzer

So go into the IO Configuration tool in the start menu:



This window will come up:



Right click "My Configuration" and then "Add Instruments"



Enter the instrument information - You'll use 28 instead of 8 in the address and set the name to "Audio Analyzer". Click OK:



It should look like this now (with the right GPIB Address):



Now this bit is Important - You need to click the save icon to save this configuration:



And now you can run the VXE:



TonyG

[Johnny10]

I see the naming convention is correct for the Agilent version; " Audio Analyzer "
In my version of NI MAX I needed to enter Audio_Analyzer"

Don't remember why but I had problems using the Agilent version and since I was using a NI PCI Board I went with NI.

Pete Millet programs work perfect for me.

Good Job Tony_G

[Tony_G]

I see the naming convention is correct for the Agilent version; " Audio Analyzer "
In my version of NI MAX I needed to enter Audio_Analyzer"

Don't remember why but I had problems using the Agilent version and since I was using a NI PCI Board I went with NI.

Pete Millet programs work perfect for me.

Good Job Tony_G

Thanks - Just to provide some insight into the environment on this, I'm running a NI GPIB-ENET/100 in my rack with the other racks being connected via an 37204A extenders. This causes all GPIB addresses to be asserted so you can't scan for instruments unfortunately (you need to set them up one by one).

I spun up a VM for this on Win7, installed the NI 488.2 and NI VISA libraries and configured them to use my GPIB-ENET (this is another great reason for it, I can access all this T&M gear over the net and from VMs). I tested that and then installed the Keysight IO Libraries 2018.2 (latest one in any case if that isn't the correct version). That goes down as the secondary VISA and I tested that it worked using the Keysight Interactive IO (to a 3325B, the 8903B seemed to confuse the utility with its EOL sequence - I could see the OD/OA but the util wouldn't hit it).

Then I setup the VEE Runtime and configured the instrument. So I'm not sure if there is something that the Keysight stuff brings to the table in this case but using the name without the underscore did pop a warning that it wasn't standard: I just ignored that.

TonyG