LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Keithley 6517B GPIB Write Error 7

Hello,

 

I have a Keithley 6517B running and communicating with PC through GPIB. The program was initially running fine, and giving the current-noise signal against applied voltage (as programmed). But now when I run the program , it is giving an error that arises at the 6517 Reset/Preset.vi -

 

Error 7 occurred at GPIB Write in Keithley 6517A Reset / Preset.vi

 

How do I get rid of this error. I don't understand how suddenly an error arised when I changed nothing in the program or settings of the keithley. The keithley is configured at GPIB address 27.

 

I am attaching the main program and the sub.VI llb file .

 

Now when I run the main program, the graph does not show any current or noise signal, but it shows a straight line plotted along '0' along the x-axis (that is, against time or voltage)

 

Please help.

Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
Download All
0 Kudos
Message 1 of 11
(4,354 Views)

Error 7 indicates that the GPIB interface is not present.  If you look in MAX is it listed?  What kind of GPIB interface are you using?

0 Kudos
Message 2 of 11
(4,337 Views)

Also, are there any other devices on the same interface? Can you communicate with them? Can you send something simple like an *IDN? command and get a response?

 

My suspicion is that there's a problem with the interface itself -- which is what DAD is getting at with his questions.,

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 3 of 11
(4,325 Views)

Dear DAD and MikePorter,

 

Yes, the GPIB interface is detected on MAX. It shows device is working properly and also the *idn? Query check is working fine. I am using a NI-GPIB USB cable for communication: https://www.ni.com/en-us/shop/model/gpib-usb-hs.html

 

There is no other device connected via the GPIB except the keithley. Infact there are no other GPIB connected to this PC.

 

Why do I still get error 7? Please help.

Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
0 Kudos
Message 4 of 11
(4,315 Views)

Can you send the identify command from LV?

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 5 of 11
(4,307 Views)

What do you mean by identify command? DO you mean the Query check? ..Then its *idn?

 

Please see attachments for error screenshots from LV

Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
Download All
0 Kudos
Message 6 of 11
(4,301 Views)

Again, does the *IDN? querry work in MAX?  Do you have the right GPIB address?  Have you enabled the GPIB communication on the instrument?


Nevermind.  I just found your MAX screenshot.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 7 of 11
(4,292 Views)

OK, can I see your LV code? If you can send the identify command from MAX and that works, something is wrong in the LV world.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 8 of 11
(4,257 Views)

WOW.  How does the Instrument Driver Network claim that as a Plug-n-play Project technology driver?  OK The driver is a llb probably written in LabVIEW 2.0 with seriously old (read as Outdated) style issues.  Yes folks, that really is a LV2 style global in there! Smiley Tongue "Error Query Global.vi"

 

There seams to be a large inconsistancy about how the driver handles EOI and initialization of GPIB communications.  (In fact the documentation often mentions VXISmiley Surprised)

 

IMHO this driver needs a rewrite and update to VISA

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 9 of 11
(4,240 Views)

Hello Mike,

 

I was on leave hence the late reply. I have attached the entire LV main vi with the sub VIs llb file to the very first message on this post. I have attached them again to this message.Do you mean something else?

Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
Download All
0 Kudos
Message 10 of 11
(4,209 Views)