Measurement Studio for VC++

cancel
Showing results for 
Search instead for 
Did you mean: 

test instrument unresponsive

Dear Sir: 

 

       I am programming in C language using Visual Studio C++.

 

      My problem is one test instrument fails to elicit a response to the standard NI programs and codes.    The test instrument is a TEK 784D oscilloscope.

 

      I own lots of test instruments with GPIB connectors and when I run the standard NI programs, all the other test instruments responded.

 

             Using MAX:   Search for instruments function yielded no response from the  test instrument.

 

            NI SPY reports: Find Listen error when only the test instrument in question was enable on the bus.

 

 

     I compiled the National Instruments code programs that are part of the NI C programming tutorial package such as:

 

FindInstruments.C.

 

     Which I thought might find a working remedy for me but this attempt failed.

 

       My tektonix oscilloscope 784D still did not respond.   I have all the necessary o-scope GPIB options installed on the instrument.  I am fairly certain that this scope is compliant with regard to the 488.2 standard.

 

       I would like to know why the oscilloscope did not respond.   It is as if the GPIB cable was connected to an open.

 

The  FindInstruments.C  NI program should have made any test instrument specific language requirements inserted into the code unnecessary.

 

        Can you tell me why the TEK scope is having difficulty getting connected?

 

 

      

 

      

0 Kudos
Message 1 of 16
(7,102 Views)

A few debugging suggestions:

-Re-install the NI-488.2 driver to make sure that the files weren't corrupted

-Check the Windows Control Panel>>Device Manager for the device to see if your computer is recognizing the connection outside of the Measurement & Automation Explorer

-Make sure the port and cable are not defective by changing ports/cables or changing the device you connect to that you have had success connecting to previously on this system (assuming you have in fact connected any other devices on this current system)

Ian M.
National Instruments
0 Kudos
Message 2 of 16
(7,085 Views)

Dear Sir:

 

      Thank you for your reply.   

 

      Is it possible that, with regard to the latest test instruments that are currently sold on the market, are updated NI drivers required when new test instruments are distributed to the public?   Has this ever been the case, or this is generally not probable due to test instrument requirements which seek "backward compatibilty" with old protocols or standards?     

 

      Although test instrument language is specific to test instrument, is GPIB board connectivity guaranteed with regard 488.2 compliance?  In other words, as long as a test instrument is advertised to be IEEE 488.2 compliant, GPIB connectivity is guaranteed - MAX should detect the test instrument as long as it is advertised as being GPIB compliant.   Is this the case?

 

      I thought that it might be helpful for you to know that is not a new install.   I have been using this system for years, using other test instruments, and all my test instruments and cables have been mixed around into different computer GPIB ports and into other test instrument ports and I have had no connectivity problems.  

 

     

0 Kudos
Message 3 of 16
(7,081 Views)

Generally speaking any time you use third party devices (using GPIB or any other connection), you can directly access the drivers necessary for using that instrument via ni.com/idnet and searching for your device. The following is the link to the page that corresponds to your device specifically.

 

http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=149

 

In regards to your other questions, it is possible that even though an instrument contains GPIB board connectivity and is 488.2 compliant that our software won't recognize it. But if your device manager in Windows is not recognizing it then there might be other issues. You can also use the GPIB Troubleshooting Utility in the start programs.

Ian M.
National Instruments
0 Kudos
Message 4 of 16
(7,064 Views)

Dear Sir:

 

     I believe the GPIB Troubleshooting Utility that you were referring to only tests for the correct installation of the GPIB board.   As I told you before, since my other test instruments can work with the board, the GPIB card installation appears to be OK.  I used the GPIB Configuration Utility to test my system again anyway (to comply with your request) and, again, all the tests passed.

 

     With regard to the link that you sent me, before I download and install the drivers, can you please answer these questions: 

 

      Why does my computer say I have these software packages installed on my system:

 

CVI Run-Time                        9.0.0.356

LabVIEW Run-Time                    8.2.1

NI-PAL Software                     2.5.2

LabVIEW Run-Time                    8.6.0

 

but when I click on those icons nothing happens?   The relevance of this question is with regard to your suggestion that I download the 784D drivers.   Also,  the drivers in the link that you pointed me to require this additional software:

 

 NI-VISA 4.6
IVI Compliance Package 4.2

 

Will I have to purhcase these items?

 

More important, with regard to the problem at hand;  what are the requirements for MAX to be able to see GPIB connected devices?    I understand the find-listen polling methods and other methods which facilitate connectivity.   What are the fundamental requirements for MAX to see a GPIB test instrument?  I know MAX needs to know the "primary address" of the test instrument, what else does MAX need to know?

 

 

0 Kudos
Message 5 of 16
(7,058 Views)

The Run-Time engines that you mentioned are programs that are needed in order to run LabVIEW deployed executables and isn't a tool for development. The device drivers for NI-VISA and IVI Compliance are free and will not cause you any more costs to you than the time to download them. You are correct in that the Measurement & Automation Explorer needs a primary address. Hope that this helps answer your questions and you are able to make use of the driver downloads to connect with your device.

Ian M.
National Instruments
0 Kudos
Message 6 of 16
(7,043 Views)

The driver downloads turned out to be mutually exclusive installs.  

 

If you installed one, the other would not install. 

 

In any case, the download and install did not work.  

 

Would it be helpful to you if I could provide you with GPIB analyzer data?

0 Kudos
Message 7 of 16
(7,035 Views)

The drivers should not be in conflict as they should not be downloaded separately. When you downloaded the drivers did you download them from the specific page for the Tektronix TDS784D? You can find it on ni.com/idnet by searching for the oscilloscope. However, the following is the link that you need for this issue.

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9698659CE034080020E748...

It is a single driver download and has been tested for using the Tektronix TDS784D.

Ian M.
National Instruments
0 Kudos
Message 8 of 16
(7,030 Views)

The download wasn't the problem.

 

It was the installation.   If you installed one and then tried to install the other - you couldn't.  You weren't given the option of installing the other driver once the other one was installed.   The message left by the window informed you that -  no further updates were necessary.  The install box was greyed out. 

 

By the way, the reason why this happened may be due to the fact that the install defaulted to my C: drive when I wanted to install the drivers on another drive.  What happened was, the install took up so much memory that my C: drive that it disabled my operating system shutdown and other features..  This resulted in a real disaster for me.    I had to restructure the entire drive and I was forced to un-install the drivers.     

 

I am a little bit curious about what you were trying to do.   One driver is for LabWindows and the other driver is a Labview driver.    If these drivers were intended to be called by MAX please reply and let me know.

 

Also, can you tell me how the initial "VISA" and "COMPLIANCE" install software comes into play as a solution?  As I recall, I had to install this first, and only then was it possible to install the other 2 drivers that you pointed me to.  You had mentioned that install earlier in the post.

 

 

0 Kudos
Message 9 of 16
(7,026 Views)

I would say the main problem here is you are not able to see your device in MAX.  Please make sure you have followed the proper instructions for connecting a GPIB instrument as found here:

http://www.ni.com/gettingstarted/setuphardware/instrumentcontrol/gpibconnect.htm

 

Other things to try:

1) Use another GPIB cable

2) Connect to another computer, see if this problem persists

3) Check to see if the device is showing up in Windows Device Manager

 

Hope this helps!

 

Patrick W.
Applications Engineer
National Instruments
0 Kudos
Message 10 of 16
(7,020 Views)