U848xA传感器和平均值

我正在尝试在手动设置滤波器长度时进行测量，并在连接到N1914A功率计时使用U848xA USB功率传感器。
到目前为止，没有运气。
U848xA传感器表现出与其他传感器不同的行为 - 我想知道这是否是功率计的缺陷，或者这是USB传感器固有的能力。
（手册似乎并不表示他们不能这样做，所以...... ???）为了重现这种情况，我有一个'标准'功率传感器连接到N1914A的通道A（f / w A2）
.01.10 - 2014年9月），在这种情况下，它是一个E9304A，一个U8488A连接到通道C.它们没有连接任何信号 - 在这种情况下并不重要。
以下是我发送到功率计的SCPI命令：* * RST * INIT1：CONT ON（自动从空闲转换到等待触发）* INIT3：CONT ON * SENS1：AVER：COUN 100（或大约2.5秒）
50ms /样本）* SENS3：AVER：COUN 100 * TRIG1：SOUR BUS * TRIG3：SOUR BUS * * TRG请注意，在* RST之后，平均状态默认为On（SENSx：AVER：STAT ON）和自动触发延迟默认值
打开（TRIGx：DEL：AUTO ON）。
如果要利用触发延迟和滤波器长度来平均读数，也不能使用立即触发。
发送* TRG命令后，通道A在预期的2.5秒后更新。
同样，FETCH1？
命令将阻塞直到2.5秒完成，然后返回值。
但是，带有USB传感器的通道C永远不会更新，还有一个FETCH3？
命令只是超时。
（我也尝试过安装在传感器上的f / w修订版A.01.01，A.01.06和A.01.08，但所有人的行为都是一样的。）所以，这听起来像是有缺陷的行为，但我想知道
如果有其他人对此有想法。编辑：Francis Small于2015年6月19日下午4:54



     以下为原文

  I'm trying to make measurements while manually setting the filter length and using the U848xA USB power sensors when connected to a N1914A power meter. So far, no luck. The U848xA sensors are exhibiting different behavior than other sensors - I'm wondering if this is a defect in the power meter, or if this is something the USB sensors are inherently capable of. (The manuals don't seem to indicate that they can't do this, so... ???)

To recreate the situation, I have a 'standard' power sensor connected to Channel A of the N1914A (f/w A2.01.10 - Sep 2014), in this case it's a E9304A, and a U8488A connected to Channel C. They aren't hooked up to any signals - not that it really matters in this case.  Here are the SCPI commands I then send to the power meter:

* *RST
* INIT1:CONT ON (automatically transition from idle to waiting-for-trigger)
* INIT3:CONT ON
* SENS1:AVER:COUN 100 (or about 2.5 sec at 50ms/sample)
* SENS3:AVER:COUN 100
* TRIG1:SOUR BUS
* TRIG3:SOUR BUS
* *TRG

Note that, after *RST, averaging state defaults to On (SENSx:AVER:STAT ON) and auto trigger delay defaults to on (TRIGx:DEL:AUTO ON). You also can't use the immediate trigger if you want to make use of the trigger delay and filter length to average the reading.

After sending the *TRG command, Channel A updates after the expected 2.5 sec. Likewise, a FETCH1? command will block until the 2.5 sec have completed, then return the value. However, Channel C with the USB sensor never updates, and a FETCH3? command simply times out. (I have also tried this with f/w revisions A.01.01, A.01.06, and A.01.08 installed in the sensor but the behavior is the same for all.)

So, it sounds like defective behavior to me, but I wondered if anyone else had ideas about this.

Edited by: Francis Small on Jun 19, 2015 4:54 PM