HI, I hope somebody can help me with this one.
I'm trying to control a FLUKE 5700A calibrator with a NI PCI-GPIB board and LabVIEW 8.5. When I perform a scan for instruments operation in MAX (v 4.3.0) I get the following result: too many listeners on GPIB (I tried with other equipment [hp 34401a] and it was detected). I checked the PCI-GPIB installation and configuration and it passed all test.
Now, the Fluke 5700A is a 1990 model, the operator manual says it is fully programmable for use on the IEEE 488.1 standard and that the interface is also design in compliance with supplemental standard IEEE 488.2 (also the *IDN? command is listed in the command list). The FLUKE 5700A software revision are: Main J and Inguard A, if it mean something to somebody.
The FLUKE 5700A GPIB address is set to 4 (factory default) and it is the only equipment connected to the GPIB bus.
To communicate with this equipment I'm using the certified LabVIEW driver downloaded from NI Instrument driver network. To help debug I just use the Initialize.vi connected to the Close.vi (with ID Query and Reset set to the default TRUE value), I run the application and use NI-Spy to record the talk/listen exchange. From the recorded result I observe a timeout after every VISA READ attempt.
When I run the application the ADDR indicator of the Fluke display do not lit (or blink once very quickly) so it seem that the command is not addressed to the equipment (note that when I'm using GPIB::3::4::INSTR the ADDR indicator is ON but I still have a VISA READ timeout).
One thing I observed: I right clicked on the "VISA Resource Name" terminal of the Initialize.vi and select "create control". Now when go to the front panel and look at this control it is populated with all GPIB addresses with "4" as a secondary address (e.g. GPIB::1::4::INSTR, GPIB::2::4::INSTR, .. , GPIB::30::4::INSTR) which seems to explain the "too many listeners on gpib" message that I got in MAX (see attached Visa resource name,jpg).
I changed the GPIB address on the FLUKE 5700A to "5" and repeated the "create control" operation, after that the VISA Resource Name control was populated with all GPIB addresses with "5" as a secondary address.
Anybody with an idea to solve this?
Thanks
Ben