05-14-2013 09:01 PM
My LabVIEW program hangs up on one of my Read GPIB steps which causes the active light to go out. From there I get no usable data. Any ideas?
05-15-2013 03:07 AM
05-15-2013 05:45 AM
I am taking a homodyne laser measurement. My problem seems to be between an o-scope, the GPIB, and a LabVIEW program. I have reloaded the newest driver code for the GPIB. I doublechecked that I am using the proper interface cables. I have viewed the LabVIEW block diagram while it was running and noticed that it gets hung up on one of the steps where it is supposed to read the GPIB. It is on that step, the GPIB active light goes out and I get start getting errors and unusable data. My assumption is that one of the blocks is not working in LabVIEW but I do not like to assume things.
05-15-2013 12:21 PM
Is that the first action on gpib for that instrument?
If yes: is the address of the instrument correct? probably yes. So is the command correct for that instrument?
if not check this.
I have the feeling it is a wrong command, or the instrument is not in a state to return data.
05-15-2013 12:27 PM
Thank you for that advice. It is the third action, but second read. I will open up the block within the block of my inhereted program. I will double check the commands from there. Thank you again for the advice.
05-22-2013 09:53 PM
I have attached the vi in this email if you want to look at it.
05-24-2013 04:37 PM
Hi
just a few remarks that come up on a late Friday evening
Why are you using the gpib functions,
I'm stuck to VISA because it has more to offer for other busses also.
The only thing we need gpib for is the low level acces like GET (group execute trigger) that is not available in visa.
And I don't understand why you set the file position instead of just adding to the file.
05-24-2013 08:06 PM
I am sorry. I thought that was the code. I am picking up the project from someone else. That is why I am using a GPIB. I will looking into just using a VISA. The instruments being monitored are the O-scope and Lock-in.