GPIB SR780 Possible Timing Issue?

[planb33]

Hi all,

I am trying to control a SR780 analyser, I have written some LV code that is nearly doing everything it's supposed to, span, windowing, coupling etc. However, I can't seem to turn on the averaging. The instrument just says "NoAvg" and then the code is in an endless loop (while loop, waiting for the number of averages to hit a specific value, which it never does). However, the rest of the code is known to be correct as it was all working until I noticed that another parameter wasn't being set which has now been fixed but thrown out the averaging.

I have attached my LV code (which is a bit messy now from all of the debugging, bunch of wait timers etc). 

Any help would be greatly appreciated.

[crossrulz]

Have you tried the LabVIEW driver?

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0473992E99DF2D6FE0440003BA7CCD...

[planb33]

Yes, this is the driver that I am using.

[Minions]

It appears that you could send the SCPI commands for averaging to the instrument. You will need to send these commands with their appropriate keys - (FAVG, FAVN, FAVM, or FAVT).

[tec5c]

Thanks for the reply.

Yes, these are the commands that I am using (contained in one the driver VI's)

[planb33]

Apologies, the above reply is from me just under a different account which I forgot that I had.

[planb33 · Accepted solution]

Update: I have fixed the above problem.

The issue was traced back to a mistake in the (NI Certified) driver. One of the VI's which allows you to enable/disable the two displays has a mistake, where enable=disable and vice versa. So by setting it to enable, it was actually disabling the displays... argh! The fix was to simple set it to disable.

Hopefully this information may help someone in the future.

[DahlmanR]

I was looking through the README for the driver, and saw the following: 

"To report issues or provide feedback about this instrument driver, please send an email to instrument.drivers@ni.com." 

Unfortunately I don't have the device to test it out, but I'd send along an email about what you're seeing, the version of the driver you're using, the specific device you're using, and the VI in question. 

R Dahlman