NI Home
Cart Cart | Help
Hello Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI
You are here: 
NI Home > NI Developer Zone > NI Discussion Forums


Reply
Trusted Enthusiast
Albert.Geven
Posts: 3,152
0 Kudos

Re: Communication dropout with GPIB-USB-B

I agree with Jeff that Stanford has a bad record in GPIB compliancy.

 

greetings from the Netherlands
Proven Zealot
Jeff·Þ·Bohrer
Posts: 5,432
0 Kudos

Re: Communication dropout with GPIB-USB-B

Ouch. I just looked at the OPs alias. I hope we did not just stuff our feet in our mouths.
8-Ball Consulting advertising banner

Certified LabVIEW Consultant. The partner you can bank on when you're behind the 8-ball.
Trusted Enthusiast
Albert.Geven
Posts: 3,152

Re: Communication dropout with GPIB-USB-B

truth stays truth

greetings from the Netherlands
Member
Kevin@SRS
Posts: 6
0 Kudos

Re: Communication dropout with GPIB-USB-B

Only a small amount... :smileywink:

 

Actually I'd like to take a discussion about this off line from the forum and get your ideas about this. Please email me directly at jkm@thinksrs.com. thanks...

 

But again, my biggest problem is why is communication (& device ID) lost between the computer and a single instrument. The lost instrument can be Tek, Agilent or SRS. It isn't that the instrument misses some commands. The National Instruments driver completely looses it from the attached devices list. If you run NI Measurment & Automation Explorer, the lost instrument isn't in the list. To get it back you need to disconnect & reconnect the GPIB-USB pod from the computer.

 

Does the NI driver remove a device from its list if it can't communicate with it? Knowing this would help us debug the system.

Proven Zealot
Jeff·Þ·Bohrer
Posts: 5,432
0 Kudos

Re: Communication dropout with GPIB-USB-B

The next step is going to be figuring out what went wrong.  Are you familliar with the GPIB Analizer?  Do you Have a station you can run with conditional probes?

 

Can you Share the code or describe it in detail?

 

My GUESS (and my 8-ball has been known to be somewhat unreliable) is that on of the instruments is sticking a line or something where the next command can't go out, or the next device won't get addressed correctly.  If you can halt on this condition you'll be able to inspect the capture and maybe find the offending device/command/FW.

8-Ball Consulting advertising banner

Certified LabVIEW Consultant. The partner you can bank on when you're behind the 8-ball.
By using this web site, you accept the Terms of Use for this web site. Please read these Terms of Use carefully before using any part of this site. Please go here for information on ni.com's copyright infringement policy.
My Profile | Privacy | Legal | Contact NI © 2011 National Instruments Corporation. All rights reserved.    |    E-Mail this Page E-Mail this Page