LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 14 ocurred at GPIB write, labview cant add resource

Hi

 

I have a problem similar to that of baalbiss. I'm using a VI to control a Tektronix 2756p spectrum analyzer by GPIB. It works on one computer (LabView 8.6, MAX 4.7) and I've tried to make it work on another, but get the same error message as baalbiss. I can also communicate with the analyzer through MAX. It's seems the problem only occurs when writting to the instrument with LabView.

 

I've installed LabView 2010 (MAX 4.7.1) on the new computer and have had no problem loading the VI, I'm using to same machine and cables for the two computers, and I've tried connecting other GPIB controlled instruments to the new computer, with the same result: MAX will communicate with them, LabView will not.

 

Any help will be much appreciated!

0 Kudos
Message 11 of 14
(2,004 Views)

I read through the list, but couldn't find the answer for the problem.

 

I have exactly the same problem communicate with my instrument. I can talk to it through MAX, but see this error 14 when I run my LabView program.

 

Thanks,

 

 

0 Kudos
Message 12 of 14
(1,861 Views)

 

Hi

 

Now I'm controlling my instruments with other Desktop and they work correctly.

 

The computer has an xp windows may be the problem occurring with windows 7

 

   

Good luck Smiley Happy 

 

0 Kudos
Message 13 of 14
(1,855 Views)

Possible Cause: There are no GPIB devices attached to your GPIB controller. This can be because all of your instruments are turned off, one of your instruments is in error and is asserting a handshaking line, your GPIB cable is disconnected from your board, or your GPIB cable is broken.
Solutions:

  • Verify that all instruments are operating correctly, and that the ones you wish to communicate with are indeed powered-on.
  • Disconnect all instruments and connect them one at a time to determine if one instrument is causing the problem.
  • Check for loose or faulty cabling, and make sure that at least 2/3 of your instruments are powered-on (this is a requirement of the IEEE 488 specification).
  • If the timeout period is too short for the driver to send command bytes, increase the timeout period. 
Also, what versions of LV, drivers, MAX and Windows are you using?
0 Kudos
Message 14 of 14
(1,848 Views)