E4407B响应缓慢

想知道是否有其他人正在经历这种相同的行为。
我通过GPIB控制分析仪。
固件版本为14.06（最新）。
这就是我正在做的事情和我看到的事情。
* RST预设分析仪。
将中心频率设置为2MHz，跨度为50kHz，RBW为1kHz，并打开Marker Noise功能。
我将扫描设置为单一，打开平均，30次扫描，平均类型为视频。
我发送INIT;
开始平均，然后观察* OPC等待完成30次扫描。
从此时起，频谱分析仪需要3-10秒来处理每个GPIB事务。
在上述操作之后我想做的是进行标记最小搜索，然后关闭平均值，关闭标记噪声，然后重新开启连续扫描。
其中每个都通过GPIB作为单个命令完成到分析器，并在执行下一个命令之前执行3-10秒。
在我预设之前，分析仪将保持这种“缓慢”模式。
我在另一台有14.04固件的E4407B上尝试了这个，但没有看到这个问题。
但是，从14.04到14.06的固件更新包括对GPIB时序的改进，我发现GPIB命令随机出现语法问题，未终止的报头等问题与工作代码有关。
对14.06的更新已经纠正了这个问题，但现在我看到这个问题变慢了。
任何人都有类似的经历。
安捷伦有人可以解决这个问题吗
这是一个已知的问题？
会有固件修复吗？
任何解决方法（没有将30条迹线倾倒到PC并让它进行平均和标记噪声）？
感谢您的任何建议或帮助。
特洛伊。



     以下为原文

  Wondering if anyone else is experiencing this same behavior.  I am controlling the analyzer through GPIB.  Firmware version is 14.06 (most current).  Here is what I am doing and what I see happen.

*RST to preset the analyzer.
Set center freq to 2MHz, span to 50kHz, RBW to 1kHz, and turn on Marker Noise function.
I set sweep to single, turn on averaging, 30 sweeps, average type is video.   
I send INIT; to start averaging, then watch *OPC waiting for completion of the 30 sweeps.  

From this point on, the spectrum analyzer takes 3-10 seconds to process each GPIB transaction.  What I want to do after the above is do a marker min search, then turn off averaging, turn off marker noise, then turn continuous sweeping back on.  Each of these is done as a single command via GPIB to the analyzer and is taking 3-10 seconds to execute before the next command executes.  The analyzer will remain in this "sluggish" mode until I preset it.

I have tried this on another E4407B that has 14.04 firmware and do not see this problem.  However, the firmware update from 14.04 to 14.06 included improvements to GPIB timing and I was seeing issues with GPIB commands randomly having syntax problems, unterminated headers, etc with working code.  The update to 14.06 has corrected that issue, but now I am seeing this slow down.   

Anyone have a similar experience.  Can anyone from Agilent address this?  Is this a known issue?  Will there be a firmware fix for it?  Any work-arounds (without dumping 30 traces to the PC and letting it do the averaging and marker noise)?

Thanks for any suggestions or help.

Troy.