E8257D当软件试图运行高频段调整时失败

嗨 - 我们的支持团队需要您提供一些信息。
附带参考工具。
•是否可以发送Install.log文件C： Program Files  Agilent TME  Output  Install.log•是否可以发送应用程序的ErrorLog.txt文件C： Documents and Settings  All Users  Application Data  Agilent Technologies  Test
管理环境输出 ErrorLog.txt•您是否可以创建并发送失败/中止的测试的Jedix.jdr文件？
您需要在运行Jedix Recorder的情况下重新运行测试。
此IO日志可以帮助我们查看测试中发生错误的位置。
（参见附件）•UUT的型号和型号是什么？
序列号和选项？
*如果您可以创建TME报告并发送它，显示建议的此信息。*•失败PLA调整是什么意思？
测试是否以“失败”状态中止或完成？
谢谢 - 编辑：tabbott于2014年4月23日上午11:43
自述文件 - JEDIX安装和使用说明 - External.pdf227.9 KB



     以下为原文

  Hi -

Our support team will require some information from you.  Referenced tools are attached.  


•     Can you send the Install.log file C:Program FilesAgilent TMEOutputInstall.log

•     Can you send the Application's ErrorLog.txt file C:Documents and SettingsAll UsersApplication DataAgilent TechnologiesTest Management EnvironmentOutputErrorLog.txt

•     Can you create and send a Jedix.jdr file of the test that failed/aborted?    You will need to re-run the test with the Jedix Recorder running. This IO log can help us to see where in the test the error is occurring.  (See process- attached)

•     What are the UUT's Model & Serial number and Options?  *If you can create a TME report and send it showing this info that is recommended.* 

•     What do you mean by Failing the PLA adjustment?  Is the test aborting or completing with a “fail” status?


Thank you -

Edited by: tabbott on Apr 23, 2014 11:43 AM

附件

• JediX_Setup.zip825.6 KB
  
• ReadMe - JEDIX Install and Usage Notes - External.pdf227.9 KB
  

我已经包含了安装日志，错误文件，故障日志，内部IO记录器的跟踪日志以及包含故障，序列和选项的图片。
它总是出现失败状态。
再次感谢您的帮助！



     以下为原文

  I've included Install log, error files, tme failure log, the trace log from the internal IO logger, and pictures with failures, serial, and options. 

It always comes up with fail status. Thank you again for the help!

附件

• E8257D.zip176.9 KB
  

嗨帕特里克，以下是我的支持团队的回复：*从错误.log文件中我可以看到使用了E9304A（STD）功率传感器，测试需要一个E9304A H19传感器。
请验证客户是否使用了正确的传感器（E9304A H19），并且他已在TME数据库中为ETE'Powerensor LowFreq1'映射了正确的传感器。
有时这些问题是在映射错误的模型传感器时引起的。*问候 -



     以下为原文

  Hi Patrick,

Here is the response from my support team:

*From the error .log file I can see the E9304A (STD) power sensor is used, the test requires an E9304A H19 sensor.   Please verify that the customer is using the correct sensor (E9304A H19) and that he has mapped the correct sensor for ETE ‘PowerSensor LowFreq1’  in the TME database.  Sometimes these issues are caused when wrong model sensor is mapped.* 

Regards -

嗨帕特里克，更多来自我的支持团队......另外，我们使用DIAG命令点击电子衰减器，同时将功率水平保持在0dB，这样就可以确保测试期间功率水平下降的原因。
此外，在您映射了正确的功率传感器后，请让客户按此顺序再次运行调整：•ALC动态校准•低频功率平坦度•高频带功率平坦度然后，如果高频功率平坦度测试再次失败。
请发送这些数据文件。
•您能否向我发送调整数据文件：C： Documents and Settings  All Users  Application Data  Agilent Technologies  Test Management Environment  App_Name  ModelSerial.txt（TME 3.xw / XP）•能否请您发送给我
调整数据文件：C： ProgramData  Agilent Technologies  Test Management Environment  Output  App_Name  ModelSerial.txt（TME 3.xw / Win 7）问候 -



     以下为原文

  Hi Patrick,

More from my support team...

Also, we are clicking in the Electronic Attenuator using DIAG commands while keep the power level at 0dB, so that why the power level is dropping during the test. 

Additionally, please have the customer run the adjustments again in this order, after you have the correct Power Sensors mapped:

•     ALC Dynamic Calibration
•     Low Band Power Flatness
•     High Band Power Flatness

Then, if the High Band Power Flatness test fails again. Please send these data files. 

•     Can you please send me the Adjustment Data file: C:Documents and SettingsAll UsersApplication DataAgilent TechnologiesTest Management EnvironmentApp_NameModelSerial.txt  (TME 3.x w/XP)
 
•     Can you please send me the Adjustment Data file:  C:ProgramDataAgilent TechnologiesTest Management EnvironmentOutputApp_NameModelSerial.txt  (TME 3.x w/Win 7)

Regards -

这种特殊的发生器只能通过高频测试功率平坦度测试（42 GHz以上）。
当高频段校准失败时，我尝试使用低频段来查看是否存在任何错误。
我目前正在为此目的获得e9304a-h19，但该项目并不真正需要它。
我查看了三次尝试的高频段调整，它们都在同一个地方失败了。
我已将所有三个文件都包含在文件中。编辑：Patrick S于2014年4月23日下午10:28



     以下为原文

  This particular generator only fails the high band test power flatness test (above 42 GHz). When the high band calibration failed, I then tried low band to see if there was any errors in that as well. I currently am getting a e9304a-h19 for this purpose, but the item doesn't really need it. I looked through the three attempted high band adjustments and they all fail in the same place. I've included all three files in the file.

Edited by: Patrick S on Apr 23, 2014 10:28 PM

附件

• Adjustment.zip22.3 KB
  

嗨帕特里克 - 来自我的支持团队......通过检查已知的好盒子阵列与客户单元，客户盒确实在RF路径上显示硬件问题。
在45.2GHZ时，客户单元具有额外的4dB衰减，在此高频率下，任何不正确的连接都可能导致这种情况。
见附件 -



     以下为原文

  Hi Patrick -

From my support team...

The customer box does show hardware issues on the RF path by checking the known good box arrays versus the customer unit. At 45.2GHZ, the customer unit has extra 4dB attenuations, at this high frequency, any improper connections can cause this. 

See attachment -

附件

• E8257D forum .docx143.7 KB
  

嗨帕特里克 - 更多来自支持......在查看调整数据并测试我们自己的单位之后。
我们认为这可能是硬件问题？
顺便说一句，客户提到“我手工操作类似的东西，并没有看到任何严重下降。”他实际上无法手动进行相同的测量。
当我们开始调整时，我们将固件所应用的所有校正数据归零以用于功率平坦度。
因此，在调整期间，客户只能看到平直度校正的实际总测量值。
当校准完成失败时，原始校准数据将恢复，然后应用于客户尝试进行的任何测量。
我希望这有帮助。



     以下为原文

  Hi Patrick -

And more from support...

After looking at the adjustment data and testing one our own units.  We believe that this may be a hardware issue?  

By the way, the customer mentions that “I've run something similar by hand and have not seen any drops that badly.”  He can’t actually do the same measurement by hand.  When we start the adjustment, we zero out all the correction data being applied by the firmware for Power Flatness.  During the adjustment is therefore the only time the customer could see the actual total measured value for the flatness correction.  When the calibration finishes with a failure, the original calibration data is restored and then applied for any measurements the customer tries to make.

I hope this helps.