通过34972A进行快速频率测量PLC设置更改对R/S速度没有影响

为了简短起见，我尝试了多种设置组合，频率的最大读取速率约为每秒八（8）个读数（R / S）。
我的一般配置设置为：ROUT：MON：STATE OFF CONF：FREQ 10000,1，（@ 111）ROUT：MON（@ 111）ROUT：MON：STATE ON SENSE：FREQ：VOLT：RANG 10 SENSE：FREQ：RANG：
低200 SENSE：FREQ：APER 0.1 ROUT：CHAN：DEL 0，（@ 111）TRIG：COUNT 1在这种特殊情况下，我只对在单个通道（111）上进行频率测量感兴趣，配置为0.02 PLC，
4 1/2位分辨率。
我在VB6中执行VISA命令。
使用“ROUT：MON：DATA？”似乎可以获得最快的结果。
命令。
作为参考点，周围的代码到位，但“ROUT：MON：DATA？”
命令注释掉（未执行），例程报告读取速率为972 R / S，因此VB6代码不是瓶颈。
此外，我改变了睡眠延迟（默认为100毫秒）和/或消除了VISA错误检查，并且当表观读取速率增加时，读取缓冲区中重复数据的实时频率测量仍然在8中。
-9 R / S范围。
我还有34970A（GPIB）和34980A（GPIB），两者都提供了更快的频率测量（34980A是最快的）。
最后，将PLC设置（0.02到10）更改似乎对R / S速度没有影响，所有这些都始终在8-9 R / S范围内。
任何见解都会非常感激。
谢谢，比尔更新：我还尝试将TRIG：COUNT更改为20（内存中的20个读数，而不是1），但最终，读取20个读数所需的时间仍然是大约8-9 R / S
。编辑：bwalch于2016年1月22日下午1:22



     以下为原文

  To make a very long story short, I've tried multitude of combinations of settings, and the maximum read rate for Frequency is about eight (8) readings per second (R/S). My general configuration setting are:

ROUT:MON:STATE OFF
CONF:FREQ 10000,1, (@111)
ROUT:MON (@111)
ROUT:MON:STATE ON
SENSE:FREQ:VOLT:RANG 10
SENSE:FREQ:RANG:LOW 200
SENSE:FREQ:APER 0.1
ROUT:CHAN:DEL 0, (@111)
TRIG:COUNT 1

In this particular case, I'm only interested in taking frequency measurements on a single channel (111), configured for 0.02 PLC, 4 1/2 digit resolution. I'm executing VISA commands in VB6.

The fastest results seem to be obtained using the "ROUT:MON:DATA?" command. As a point of reference, with the surrounding code in place, but the "ROUT:MON:DATA?" command commented out (not executed), the routine reports a read rate of 972 R/S, so the VB6 code is not the bottleneck. Further, I went as far as changing the Sleep delays (100ms default) and/or eliminating VISA error checks, and while the apparent read rate increases, the real time frequency measurements, discounting repetitive data in the read buffer, is still in the 8-9 R/S range.

I also have the 34970A (GPIB) and the 34980A (GPIB), and both provide somewhat faster frequency measurements (the 34980A being the fastest).

Finally, changing the PLC settings, 0.02 to 10, seem to have no effect on the R/S speed, all consistently in the 8-9 R/S range.

Any insight would be MOST gratefully appreciated.

Thanks, Bill

Update: I also experimented changing the TRIG:COUNT to 20 (20 readings in memory, instead of 1), but in the end, the time it took to take 20 readings still came out to about 8-9 R/S.

Edited by: bwalch on Jan 22, 2016 1:22 PM