GPIB connectivity

[noobie_programmer]

Dear CrossRulz;

     Thank you for your reply.

     The drivers that you had pointed me utilize an enormous amount of memory and I believe they were designed for use with LabWindows and Labview.

      I just bought a copy of Labview and I am awaiting a copy in the mail.   However, the computer I use for GPIB apps would not be able to be install Labview.

      The drivers, alone, for the TEK scope occupied so much memory in my hard drive that Windows could not properly shut down.  

      I tend to think there must be a legacy driver fully compatible for MAX and the TEK scope which is available and does not occupy as much memory.    

[Dennis_Knutson]

As noted on the download page, the driver is for .NET, C, LabVIEW, LabWindows, etc. The disk cost for me and only selecting LabVIEW is 50MB so I don't quite understand your issue there. The non-IVI LabVIEW is of course, much smaller. Still won't do you any good until you can see the instrument in MAX.

[noobie_programmer]

These two drivers were installed onto my PC.

1) National Instruments IVI specific drivers

2) IVI Shared Components 2.2.1

About the download suggestion - there were 3 possible downloads.    The "compliance" driver is required (one of three).

The link that lists the two drivers results in a installation condition whereby only one driver can be installed.  The installation of one driver will mutually exclude the other driver.    The mutual exclusion is not due to the lack of memory on my C: drive.  I deleted enough memory for the drivers to be instaled without any complications.  

A note about the mutually exclusive driver install.  If you install either driver, the installation program will overwrite the other driver (if it is already installed)  and use the same name for the driver (the driver name is not unique).

   The Labview driver was installed on my machine.

    The error message I receive is:

MAX:  No test instrument detected

NI SPY:  iberr = EBUS(14)

     I believe that, perhaps, there is some other legacy driver which will be a working solution.  

I am currently corresponding with Tektronix, maybe, they will send me a solution.

Note:   About my prior references to the Tektronix programming manual.   Tektronix tech support made a mistake and released to me the programming manual for the 784C oscilloscope, not the 784D oscilloscope.  I just discovered that today.    When they wrote me and pointed me to a download link to the 784D scope, I took their word for it.    Although,   I do not believe the difference  in manuals will make much of a difference.

    If possible, can you find some legacy program or code that was used to establish connectivity.

[noobie_programmer]

I have uploaded a screenshot of all the software that MAX sees.  Maybe someone can detect if I am missing software.

[Dennis_Knutson]

I forgot that you would need the compliance package.

All of that is irrelevant, though. None of the instrument drivers will work since you cannot detect the instrument. That is solely a function of the 488.2 driver and the instrument. Your version is not the latest but if you can detect other instruments, then I still say the problem is with tek.

[noobie_programmer]

If you look at the *.jpeg file, I believe that I do have a compliance package installed.  Is this the one that you were referring to?

By the way, I definitely agree with you, I believe that it is the TEK scope that needs some work.     I recently corresponded with Tektronix and they pointed me to another driver to download to establish connectivity.  

Sometimes, it is just the "luck of the draw."  Somtimes you run into some really great people at tech support and sometimes you don't.    And sometimes, which is in my case, I ran into a really great and helpful tech support person who helped me with one issue but, unfortunately, was not on the mark with regard on another issue (the GPIB connectivity issue).    Oh, well, "live and let live."  I am currently very happy with Tektronix tech support because another helpful tech support person pointed me to a  free 30 day trial download of WAVESTAR.    I am really happy.

[Dennis_Knutson]

The compliance package is correct. When you mentioned the size of the install, I forgot that you also needed that. You can probably uninstall all of that unless you want to use the driver for something other than LabVIEW. IVI is a layer on top of VISA which is a layer on top of IEEE-488.

Good luck getting it to work.