完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
还有其他人看过这个特殊的bug吗?
我一直难以将数据导出到文件中,因此我一直在让Datalogger软件自动导出。 回顾一下导出文件,我开始注意到数据中存在一些不连续性; 经过仔细研究,我意识到DATA是正确的,但是tiMESTAMPS出了故障。 例如,以下内容出现在我的数据的第一列中,正好按此顺序排列(强调我在非顺序部分添加):2014年2月13日12:17:59:270 2/13/2014 12: 18:00:470 2/13/2014 12:18:00:670 2/13/2014 12:18:00:870 2/13/2014 12:18:01:070 2/13/2014 12:18: 01:270 2/13/2014 12:17:59:470 2/13/2014 12:17:59:670 2/13/2014 12:17:59:870 2/13/2014 12:18:00: 070 2/13/2014 12:18:00:270 * 2/13/2014 12:17:58:273 * * 2/13/2014 12:17:58:473 * * 2/13/2014 12:17 :58:670 * * 2/13/2014 12:17:58:870 * * 2/13/2014 12:17:59:070 * 2/13/2014 12:18:01:470 2/13/2014 12:18:01:670 2/13/2014 12:18:01:870 2/13/2014 12:18:02:070我使用34980A和34924A多路复用器,运行最新的固件,IO库和 截至3月3日的数据记录器版本。 谢谢! 克拉克约翰逊ArjoHuntleigh圣安东尼奥,德克萨斯州 以上来自于谷歌翻译 以下为原文 Has anyone else seen this particular bug? I have been having difficulty exporting data to a file, so I've been letting the Datalogger software auto-export. Looking back over the export files, I've begun to notice some discontinuities in the data; upon closer examination, I realized that the DATA was correct, but the TIMESTAMPS were out of order. For example, the following appeared in the first column of my data, in exactly this order (emphasis added by me on the non-sequential portion): 2/13/2014 12:17:59:270 2/13/2014 12:18:00:470 2/13/2014 12:18:00:670 2/13/2014 12:18:00:870 2/13/2014 12:18:01:070 2/13/2014 12:18:01:270 2/13/2014 12:17:59:470 2/13/2014 12:17:59:670 2/13/2014 12:17:59:870 2/13/2014 12:18:00:070 2/13/2014 12:18:00:270 *2/13/2014 12:17:58:273* *2/13/2014 12:17:58:473* *2/13/2014 12:17:58:670* *2/13/2014 12:17:58:870* *2/13/2014 12:17:59:070* 2/13/2014 12:18:01:470 2/13/2014 12:18:01:670 2/13/2014 12:18:01:870 2/13/2014 12:18:02:070 I am using a 34980A with a 34924A multiplexer, running the latest firmware, IO Libraries, and Datalogger versions as of 03 March. Thanks! Clark Johnson ArjoHuntleigh San Antonio, TX |
|
相关推荐
2个回答
|
|
这是我第一次听说34980A。
我们在34970A / 72A上看到它并发现它是一个固件错误。 这是固定的。 仪器是相关的,因此34980A固件中可能存在相同的错误。 我将为此提交一份缺陷报告,并尝试尽快修复。 以上来自于谷歌翻译 以下为原文 This is the first time I've heard about this for the 34980A. We saw it on the 34970A/72A and discovered that it was a firmware bug. This was fixed. The instruments are related, so it is likely the same bug is in the 34980A firmware. I will submit a defect report for this and try to get it fixed as soon as possible. |
|
|
|
我无法通过Datalogger Pro每隔1秒在34925A FET多路复用器上扫描5个通道进行重现,超过10K扫描。
我忘了询问你是使用专业版还是免费版。 请寄给我Datalogger应用程序的包文件,以便我可以复制它。 发送至gem_support@agilent.com。 以上来自于谷歌翻译 以下为原文 I was not able to reproduce this with Datalogger Pro scanning 5 channels on a 34925A FET mux every 1 second for over 10K scans. I forgot to ask if you were using Pro or the free version. Please send me a package file of your Datalogger application so I can duplicate it. Send it to gem_support@agilent.com. |
|
|
|
只有小组成员才能发言,加入小组>>
1213 浏览 0 评论
2344 浏览 1 评论
2147 浏览 1 评论
2017 浏览 5 评论
2897 浏览 3 评论
948浏览 1评论
关于Keysight x1149 Boundary Scan Analyzer
691浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
793浏览 0评论
1213浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-17 16:20 , Processed in 1.428231 second(s), Total 81, Slave 64 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号