LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem of Labview communicate with Lock-in SR830

I wrote a program in Labview which can control the frequency of output signal from Lock-in SR830. Unfortunately, the lock in only executed the first command after open a Labview program,  and cannot change the frequency anymore.
I have checked the connections among my GPIB card, computer and lock in amplifier and did not find anything wrong. And there is no error shown in my Labview program. Could you suggest anything I can do in order to perform frequency change?
 
Thanks
 
 
0 Kudos
Message 1 of 4
(2,935 Views)
diamond7,

If I understand you correctly, it sounds like the LabVIEW code may not be correctly sending multiple commands to your instrument. When you run your LabVIEW code, you said that the first command is executed on the instrument you are controlling and that subsequent commands do not work. If you stop your code and re-run it, does the first command again get executed? Can you send multiple commands from a test panel in Measurement and Automation Explorer?

I ask because it sounds as if your code sends a command, but then does not provide the capability to send another command. Does the code get stuck in a loop? Have you tried watching the program run using highlight execution? This also may be an issue related to your instrument and what commands it expects to receive from the GPIB board. It may be an issue of the communication mechanisms over the GPIB bus. If you are unable to locate a bug in your code that limits the program to only 1 command, I would suggest posting your question to the Instrument Control Forum. I hope this helps!

Mike


Message Edited by Duffman Says: on 09-15-2006 01:46 PM

0 Kudos
Message 2 of 4
(2,919 Views)
Diamond7,

I also try to communicate with SR830 with Labview, but until now it doesn't work. Could please attach your vi to chek it.

Thanks

Laurent

0 Kudos
Message 3 of 4
(2,894 Views)
Thank you for your replies. I settled the problem. The problem is caused by the wrong setting of the gpib address for one of my lock-in amplifiers-- two of them shared the same address. Thank you.
 
 

Message Edited by diamond7 on 09-21-2006 07:27 AM

0 Kudos
Message 4 of 4
(2,888 Views)