GPIB-USB-B device driver recognized, but R/W failure and computer crash in MAX

[richardgarner]

I had been using a GPIB-USB-B successfully for many months (w/Dell GX270 computer, Windows XP).  However, one day suddenly I could not read or write to my instruments.  Upon investigating I find the following: GPIB-USB-B is still recognized, enabled and working properly (according to control panel>>hardware>>device drivers  and also according to the troubleshooting wizard of Measurement & Automation Explorer).  However, when I try to test by opening "devices and interfaces" in Measurement & Automation Explorer, the computer hangs and I have to reboot.  I tested on a second computer of the same brand and that computer hangs as well, but in a different fashion. I tested on a third computer (different brand, but still with Windows XP), and it works fine.  I can't read or write using either Labview 6i or using the interactive DOS program.   I am using NI 488.2 version 2.2 and Measurement & Automation Explorer version 3.0.2.3005.  I can open and write to GPIB.INI.  Device driver is NIPALUSB.SYS from March 2004.  On the two Dell computers on which Measurement and Automation Explorer causes hangups, I recently installed new monitors on each (same type).  Also, recently started using a new USB memory stick type on both.  Can't imagine in my wildest dreams that these would have an effect (but, this is Windows afterall).

[Robert M]

In these cases it's hard to know what the real cause is.  I would recommend uninstalling NI-488.2, MAX, and NI-VISA, then upgrading the BIOS to the latest version released by Dell, then reinstalling the latest versions of our drivers: NI-488.2 2.4 and NI-VISA 3.6 (which will install the latest versions of MAX and NI-PAL).  

Any ideas what else might have changed on your system to cause things to stop working as they were?

[Csaba]

HI,

"Also, recently started using a new USB memory stick type on both.  Can't imagine in my wildest dreams that these would have an effect (but, this is Windows afterall)."

- It might be the problem. I have had problems where the USB port seems to be "overloaded". Especially on IBM (Levono) computers. A LaCie USB-PCI card solved it!

Regards

Csaba

[richardgarner]

Thank you for your reply.  Unfortunately, I don't think it's the memory stick (or other stuff on the USB, including keyboard -- but haven't tried mouse).  As for the memory stick, I unintalled the driver.  For the other devices, I took everything out, one at a time. 

I have an additional piece of information

however -- I get the same kind of crashing of the machine when the GPIB-USB-B is not connected.  That is, when I run MAX and then

click on "devices and neighborhood" to get a list of GPIB devices, the computer sits there for a few seconds, then the screen goes blank for a few seconds.  Then, the upper (about 1/10) of the screen's pixels start randomly coming on as white.  I can't seem to CTRL-ALT-DEL out

of this mess.  In fact, nothing I have tried causes the computer to get out of this state.  I simply turn off and turn on again. 

In any case, I get the same thing with the GPIB-USB-B connected.  Also, when I try to run a Labview program that communicates with

an oscilloscope I get an error about connecting to device or driver.  It's as if it never even gets to the point of trying to get to the instrument on

the GPIB.  By the way, I have been using this same computer with this GPIB-USB-B

for over a year with no problems.  I have uninstalled and re-installed NI488.2 (along with MAX) several times now.  I have not

re-installed Labview.  I don't know if it is worth doing this.  Finally, in the troubleshooting wizard, the GPIB-USB-B is found and it tells

me that the device is working.

[richardgarner]

Thank you for your reply.  Unfortunately, I don't think it's the memory stick (or other stuff on the USB, including keyboard -- but haven't tried mouse).  As for the memory stick, I unintalled the driver.  For the other devices, I took everything out, one at a time. 

I have an additional piece of information

however -- I get the same kind of crashing of the machine when the GPIB-USB-B is not connected.  That is, when I run MAX and then

click on "devices and neighborhood" to get a list of GPIB devices, the computer sits there for a few seconds, then the screen goes blank for a few seconds.  Then, the upper (about 1/10) of the screen's pixels start randomly coming on as white.  I can't seem to CTRL-ALT-DEL out

of this mess.  In fact, nothing I have tried causes the computer to get out of this state.  I simply turn off and turn on again. 

In any case, I get the same thing with the GPIB-USB-B connected.  Also, when I try to run a Labview program that communicates with

an oscilloscope I get an error about connecting to device or driver.  It's as if it never even gets to the point of trying to get to the instrument on

the GPIB.  By the way, I have been using this same computer with this GPIB-USB-B

for over a year with no problems.  I have uninstalled and re-installed NI488.2 (along with MAX) several times now.  I have not

re-installed Labview.  I don't know if it is worth doing this.  Finally, in the troubleshooting wizard, the GPIB-USB-B is found and it tells

me that the device is working.

[Robert M]

It sounds like the problem is beyond the GPIB-USB-B and is related to a corrupted install of the driver software.  If you have already uninstalled and reinstalled the drivers and are still seeing this same problem, then something in the install has been corrupted and/or the drivers and driver software are not being completely uninstalled.  Your best bet is to reformat the hard drive, reinstall the OS and start fresh.  I know it's a pain, but in the long run it will save you time over trying to find out exactly what happened and where things were corrupted.

[richardgarner]

Well, with all due respect, this I believe falls into the realm of "disproportionate response."  Plus, not something I really want to do.  One of the reasons is because I'm not sure it will solve the problem.  The problem started occuring on a nearly identical computer.  But, it is not happening on a third computer which is more significantly different. 

I'm not sure what you mean when you say the install has been corrupted.  That couldn't mean the CD from which I am installing, since it is read-only.  Is that then something related to the operating system?  With regard to not completely uninstalling, I have been using Windows' "remove software" routine in the control panel.  Does National Instruments have something more substantial?  Or, is there a way of checking the completeness of the uninstall?  When I uninstall, the driver is gone and MAX is gone. 

[Collin M]

Hate to jump into the middle of this but I have had something similar happen on more than one occasion. Can you go to the MAX directory on your system, typically C:\Program Files\National Instruments\MAX\Data, and delete all the files in that directory? There are probably a couple files that can't be deleted and that is ok. When you are finished reboot and open MAX again.

[richardgarner]

It's okay to jump in.  The more the merrier.  I tried your suggestion, but with no success. Didn't change anything upon reinstalling (and rebooting). 

I downloaded the latest version of NI488.2 and MAX.  Now using version 3.1.1 of MAX.  Had success initially in that the machine does not automatically crash when I run MAX.  However,....   upon first installing, MAX would actually list the GPIB-USB as a device.  However, upon scanning for intruments, it did nothing (i.e., just sat there).  Then, after that, I got out of MAX and back in.  Then, when I tried clicking on Devices and Interfaces, program would crash (but fortunately not computer -- got that ubiquitous error "NIMAX has encountered a problem and will close.  Sorry for the inconvenience".  In fact, this happens no matter what I click on in the list (e.g., Data Neighborhood, PXI (of which I have none), Scales, etc.).

And... when I unintall and install again, same thing happens.   Basically, I believe something is getting corrupted in that machine and I can't figure out what it is.  The machine is not on any network.  I try to keep it as pristine as possible.  It just takes data in my lab and I do some data analysis (with Labview and other programs).  Have some ADC boards, and a PCI expansion box, but have had all these things for many years and have not experienced any problems.  This is becoming a real headache.  All I really want to do with the GPIB is get data out of an oscilloscope. 

[richardgarner]

I have updated information which is related to your suggestion -- which had a positive effect (but there was more to it than that).  I copied the MAX directory (C:\Program Files\National Instruments\MAX) from a computer where I knew everything worked, to the problem computer.  It seemed to at least set things back to the beginning.  That is, I was able to get into MAX and click on "devices & interfaces" without the program crashing.  Unfortunately,

it did not completely solve the problem.  After doing this once, and MAX not finding an interface, the program would subsequently crash every time I clicked on "devices & interfaces".  However, I at least had a fix to get the thing back to square one (equivalent to the FIRST TIME loading of NI488.2 and MAX).

In any case, I subsequently discovered that when some instruments on some GPIB addresses were connected and turned on, I would get problems.  However, some other instruments on particular addresses would work.  So, I took one instrument (a Tektronix TDS754) and simply went through all the addresses one at a time. Disconnected all other instruments.  The scope worked on most addresses (not all) the first time through.  Then all addresses on the next time through.  Then added some more instruments.  All was okay until I added one particular instrument (Stanford Research delay generator).  This not only did not work, but also caused everything to revert back to the drawing board.  However, with this instrument alone, it didn't work but didn't cause reversion back to drawing board. 

In any case, I think the problem is a combination of a couple of things that are related to what you and some others have said here.  First, the USB is getting loaded down if I have a particular type of instrument, or too many instruments.  Second, once I get an error, MAX seems to get corrupted to the point where I can't even reload.  I have to copy over something that is remaining (don't know what) -- even if I delete the MAX directory.  I have to actually write over the MAX directory.

So, my solution will be to go back to the old "tried and true" GPIB-PCI board that I had been using for years.  I will use this GPIB-USB for the occasional portable things that I do.

Thank you to everyone who offered advice. 

Moral: beware of the GPIB-USB.  Also, MAX does things that are totally unknown (at least to me).