完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
您好,我们在自动测试系统中使用N9030A(50GHz)非常重,它采用8565语言模式。
这是过去3个月的无褶边操作,直到它昨晚产生错误弹出窗口。 它发生在中间的过夜测量中,因此停止测量。 当它发生时,所有用户界面都被冻结,唯一可用的按钮是电源关闭开关。 当我重新打开它时,没有记录错误历史记录但幸运的是我写下了弹出窗口消息,即。 断言失败:Abort = Quit,Retry = Debug,Ignore = Continue。 由物理服务器捕获的Agilent.SAPhysics.sweptBuckets.SweptBucketsAlgorithm抛出的错误:对象引用未设置为对象的实例。 在ThreadHelper.ThreadStart的ExecutionContext.Run(ExcutionContext excutionContext,ContextCallback,Object State)的ExecutionContext.Run(ExcutionContext excutionContext,ContextCallback,Object State,Boolean IgnoreSynCtx)的ThreadHelper.Threadstart.Context(Object State)中的PhysicsServer.ProcessThread()处( )目前,我们只是希望将来不再发生这种情况,因为可靠的自动化冗长测量(超过24小时)对我们的目的至关重要。 谢谢。 史蒂夫 以上来自于谷歌翻译 以下为原文 Hello, We use N9030A (50GHz) in our automated test system quite heavily and it is in 8565 language mode. It was frill free operation for the past 3 month until it generated an error pop up window last night. It happend middle of over night measurement and the measurement halted for that reason. When it happed, all the user interface had been frozen and the only available button was the power off switch. When I turn it back on, there was no error history recorded but luckily I have written down the pop up window messages, which is. Assertion Failed: Abort=Quit, Retry=Debug, Ignore=Continue. Error thrown by Agilent.SAPhysics.sweptBuckets.SweptBucketsAlgorithm caught by physics server:Object refrence not set to an instance of an object. at PhysicsServer.ProcessThread() at ThreadHelper.Threadstart.Context(Object State) at ExecutionContext.Run(ExcutionContext excutionContext, ContextCallback, Object State, Boolean IgnoreSynCtx) at ExecutionContext.Run(ExcutionContext excutionContext, ContextCallback, Object State) at ThreadHelper.ThreadStart() At the moment, we are just hoping it does not happen again in the future as the reliable automated lengthy measurement (well over 24 hours) is vital for our purpose. Thank you. Steve |
|
相关推荐
4个回答
|
|
嗨Steve - 请发送PXA仪器*序列号*和* S / W Revision *。
要轻松找到此信息,请在仪器前面板上按:* System,Show,System *。 从左上角开始的第4和第5个入口是您想要看的地方。 S / W版本应该类似于A.08.54错误消息非常通用,因此我们无法告诉您此时出现错误消息的原因。 SW修订版和仪器序列号将有所帮助,因为我们可以查看已解决的问题与SW修订版相关。 问候 - 以上来自于谷歌翻译 以下为原文 Hi Steve - Please send the PXA instrument *Serial Number* and the *S/W Revision*. To easily find this information , on the instrument front panel press: *System, Show, System*. 4th and 5th entry from the top on the left hand side is where you want to look. S/W revision should be something like A.08.54 The error message is pretty generic, so we cannot tell you why the error message occurred at this time. The SW Revision and instrument serial number will help, since we can look at problems resolved verses SW revision. Regards - |
|
|
|
醉狼工作室 发表于 2019-10-14 11:29 嗨,序列号:US513550193软件版本:A.08.54我们进行了另一次隔夜测量,它似乎是O.K. (没有错误)谢谢。 史蒂夫 以上来自于谷歌翻译 以下为原文 Hi, Serial Number: US513550193 Software Rev: A.08.54 We took another over-night meaurement and it seems to be O.K. (no errors) Thank you. Steve |
|
|
|
只是为了更新。 在经过两个月完美无瑕的手术后,昨晚发生了同样的错误。 看起来分析仪没有响应'完成'? 'TS'命令后查询。 以上来自于谷歌翻译 以下为原文 Just for an update. This exact same error occured last night after two month of flawless operation. It looks like analyzer doesn't responds 'DONE?' query after 'TS' command. |
|
|
|
嗨,史蒂夫 - 要解决这个非常间歇性的问题,您需要从仪器中提取一些日志文件并通过电子邮件发送给安捷伦。 我会私下给你发一个电子邮件地址。 此时不要从A.08.54更新仪器SW。 我发现了856X兼容性代码的错误,更新会导致更多问题! 我们需要知道:1。错误出现的确切时间2. SA和系统事件日志的副本3. AlignHistory.txt文件的副本SA事件日志很大,但事情发生时会有时间戳。 但我们需要知道错误何时出现在屏幕上,以便我们可以将失败时间与报告的事件进行匹配。 对齐历史也是如此。 我们可能会发现仪器在您的程序获取数据的同时启动了自动对齐。 以下是如何获取Align History.txt:启动我的计算机校准(E :) Align Data Storage Alignment History.txt请参阅附加的获取SA和系统事件日志的过程。 问候 - 以上来自于谷歌翻译 以下为原文 Hi Steve - To troubleshoot this very intermittent problem, you will need to pull some log files from the instrument and e-mail them to Agilent. I'll send you an email address privately. At this point do not update the instrument SW from A.08.54. I have found a bug with the 856X compatibility code, and updating will cause more problems!! We need to know: 1. The exact time the error appeared 2. A copy of the SA and system Event Logs 3. A copy of the AlignHistory.txt file The SA Event Log is large, but there are time stamps when things happened. But we need to know when the error appeared on screen so we can match fail time with events that were reported. Same is true for the alignment history. We may find that the instrument launched an auto align at the same time your program was obtaining data. Here is how to obtain the Align History.txt: Start My Computer Calibration(E:) Align Data Storage Alignment History.txt See attached process for obtaining the SA and System Event logs. Regards - 附件 |
|
|
|
只有小组成员才能发言,加入小组>>
1201 浏览 0 评论
2338 浏览 1 评论
2139 浏览 1 评论
2012 浏览 5 评论
2887 浏览 3 评论
937浏览 1评论
关于Keysight x1149 Boundary Scan Analyzer
687浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
789浏览 0评论
1202浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-11 02:30 , Processed in 1.361472 second(s), Total 82, Slave 66 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号