完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
扫一扫,分享给好友
我在N5224A上使用Opt 118一直在玩FIFO和FASTCW命令。从读取帮助文件来看,似乎我无法使用FIFO进行频率扫描。
Golfnut似乎认为有快速扫描选项,但我不知道他是如何得出这个结论的。 如果我退出并接受FASTCW测量,并且每个外部触发器测量一个频率,则结果不如恒星。 我做了一个实验,我能达到的最快触发率约为30赫兹。 任何更快,数据都不会出现在FIFO计数中。 这听起来是对的吗? 另外,我可以在此模式下获得更正的S21(或S12)数据吗? 老实说,30赫兹对我来说有点慢。 我需要以大约200万个天线方向测量数据。 30 Hz转换为大约19小时来测量一个频率。 所以我有效地将我的设备捆绑了一整天。 对我来说绝对最低限度是测量2个频段中的3个频率。 所以现在我要长达6天。 我的下一个实验是看看我能做多快的CALC:DATA? 命令。 也许这可能比30赫兹更快。 虽然我不知道如何知道何时准确地获取数据和测量时间。 粗暴的黑客是轮询状态寄存器。 一旦我得到第一个数据就绪信号,我就会启动一个计时器。 如果我在已知的时间内没有获得足够的数据准备,那么我就知道我已经放弃了一个触发器。 以上来自于谷歌翻译 以下为原文 I've been playing with the FIFO and FASTCW commands on my N5224A with Opt 118. From reading the help file, it doesn't appear that I can do a frequency sweep with the FIFO. Golfnut seems to think there is a fast sweep option, but I don't know how he arrives at this conclusion. If I back off and settle for a FASTCW measurement, and measure one frequency per external trigger, the results are less than stellar. I did an experiment and the fastest trigger rate I could achieve was about 30 Hz. Any faster, and the data doesn't show up in the FIFO count. Does this sound about right? Also, can I get corrected S21 (or S12) data in this mode? Honestly, 30 Hz is a little slow for me. I need to measure data at roughly 2 million antenna orientations. 30 Hz translates to about 19 hours to measure one frequency. So I'm effectively tying up my equipment for a full day per frequency. And an absolute bare minimum for me is to measure 3 frequencies in 2 bands. So now I'm up to 6 days. My next experiment is to see how fast I can do CALC:DATA? commands. Maybe that can be quicker than 30 Hz. Though I'm not sure how to know when to grab the data and measure timing accurately. A crude hack is to poll status registers. Once I get the first data ready signal, I'll start a timer. If I don't get enough data readies in a known amount of time, then I'll know I've dropped a trigger. |
|
相关推荐
29个回答
|
|
> COM行为有趣。 是的,我们知道并且它将被修复。 但是,我没有看到它在9.90.05的最新固件中已经修复。 我会问。 fifo计数应该是每个PAIR,而不是值。 我们可能需要研究一下。 通过COM与千兆位LAN进行数据传输的粗略近似值约为:350μS+0.17μS/点对。 因此,对于1500个数据点对,传输该数据的总时间仍然小于1ms; 在此期间天线可以自行重新定位。 以上来自于谷歌翻译 以下为原文 >COM acts funny. Yes, we know that and it will be fixed. However, I do not see it as being fixed yet in the latest firmware of 9.90.05. I will ask. The fifo count should be per PAIR, not value. We may have to look into that. A rough approximation of the data transfer via COM with gigabit LAN is about: 350 µS + 0.17 µS/point-pair. So with 1500 data point pairs, the total time to transfer that data is still less than 1ms; during which time the antenna could be repositioning itself. |
|
|
|
我正在研究为什么2M是极限。 如果我们能够做得更大(我认为我们可以做到),我们就会这样做。 我认为这个限制很随意。 即使您不使用快速组,也不需要在行结束时从FIFO中获取数据。 您只需要让PNA有更多时间为下一次触发做好准备。 数据可以堆积在fifo中。 你不能让它溢出来。 并且您可以在获取数据时取出数据。 查询计数,取出那么多数据,然后再次查询,取出数据等...... FIFO为4GB,单个参数为500 Mpoints。 如果你有两个参数,它是250M点等...计数是复杂的点。 如果您正在测量一个参数,则每个计数将有两个浮点数(实数,虚数)。 如果要测量两个参数,则每个计数将有四个浮点数,每个点有2个复数(实数,虚数)。 组和FASTCW模式之间应该没有任何区别。 您是否有可能在其中一种模式中设置多个参数? 顺便说一下,我的例子使用了COM NumberOfGroups,但我正在测试最新的内部固件,修复了这个bug。 如果要使用COM,则必须使用ScpiStringParser。 以上来自于谷歌翻译 以下为原文 I am looking into why 2M is the limit. If we can make it larger (I think we can), we will do so. I think the limit is pretty arbitrary. Even if you don't use fast groups, you don't need to get the data out of the FIFO at the end of a row. You just need to let the PNA have more time to become ready for the next trigger. The data can pile up in the fifo. You just can't let it overflow. And you can take data out while the data is being acquired. Query the count, take out that much data, then query again, and take out the data, etc... The FIFO is 4GB, which is 500 Mpoints for a single parameter. If you have two parameters, it is 250Mpoints, etc... The count is in complex points. If you are measuring one parameter, each count will have two floats (real,imaginary). If you are measuring two parameters, each count will have four floats, 2 complex number per point (real,imaginary). There should not be any difference between groups and FASTCW mode. Is there any chance you had more than one parameter set up in one of the modes? BTW, my example used COM NumberOfGroups, but I was testing on the latest internal firmware, where the bug is fixed. You will have to use the ScpiStringParser if you want to use COM. |
|
|
|
我写的不清楚。 以下是该段的重写:计数在复杂的数据对中。 如果您正在测量一个参数,并且扫描10个点,则计数将为10,但是将有20个浮点数必须被检索; 每点一个复杂的对。 如果您正在测量两个参数,并且扫描10个点,则计数将为20,但是将有40个浮点数必须被检索; 每点2个复杂对。 我尝试了fastCW和频率扫描,我得到了正确的计数。 以上来自于谷歌翻译 以下为原文 What I wrote was not clear. Here is a rewrite of that paragraph: The count is in complex data pairs. If you are measuring one parameter, and a sweep of 10 points, the count will be 10, but there will be 20 floats that have to be retrieved; one complex pair per point. If you are measuring two parameters, and a sweep of 10 points, the count will be 20, but there will be 40 floats that have to be retrieved; 2 complex pairs per point. I tried both fastCW and a frequency sweep, and I get the correct count. |
|
|
|
>我尝试了fastCW和频率扫描,我得到了正确的计数。 那可能是。 老实说,FastCW模式让我很困惑。 我可能会设置错误的东西。 使用NumberOfGroups对我来说真正关键是让外部触发器的速度达到很好的速度。 在一行结束时抓取数据是一个好主意,因为我必须阻止电机转向。 这是抓取数据的好时机,应优化整体扫描时间。 在x-y扫描的中间抓取数据有一些辅助的好处。 或者,我可以重新发送External Trigger / NumberOfGroups命令以将更多数据填充到FIFO中吗? 感谢您迄今为止的所有帮助。 我非常沮丧,非常兴奋。 以上来自于谷歌翻译 以下为原文 > I tried both fastCW and a frequency sweep, and I get the correct count. That could be. Honestly, FastCW mode confuses me. And it's probable that I set something up wrong. Using NumberOfGroups was really the key for me to get the speed of external trigger up to a good rate. Grabbing data at the end of a row is a good idea because I have to stop the motors to turn around anyway. This is a good time to grab data, and should optimize overall scan time. There are ancillary benefits to grabbing data in the the middle of a x-y scan. Alternatively, could I just resend the External Trigger/NumberOfGroups commands to stuff more data into the FIFO? Thanks for all of your help so far. I went from very discourage to very excited. |
|
|
|
>>或者,我可以重新发送External Trigger / NumberOfGroups命令以将更多数据填入FIFO吗? >是的,您可以再次发送命令并将数据保留在FIFO中。 数据将保留在FIFO中,直到您明确清除它或取出数据。 你需要确保它不会溢出。 我认为你真正需要重新发送的唯一命令是sens:swe:模式组,如果你使用的是scpi。 PNA继续使用组计数和触发设置。 以上来自于谷歌翻译 以下为原文 > > Alternatively, could I just resend the External Trigger/NumberOfGroups commands to stuff more data into the FIFO? > Yes, you can just send the commands again and leave the data in the FIFO. The data will remain in the FIFO until you explicitly clear it, or take the data out. You do need to make sure that it doesn't overflow. I think the only command you really need to resend is sens:swe:mode groups if you are using scpi. The PNA keeps using the group count and trigger settings. |
|
|
|
>我非常沮丧,非常兴奋。 这可能表明你需要获得生命! ;-)但严重的是,如果您对FIFO或其他最佳实践有任何更具体的问题,您可能应该给我们发电子邮件。 这个线程有点长,但它可能对处于同样困境的其他人有用。 您可以直接发送电子邮件至:john_vallelunga -at- agilent.com。 尼尔斯和我相距仅175英尺,无论如何我都可以使用这项运动。 以上来自于谷歌翻译 以下为原文 >I went from very discourage to very excited. This is possibly indicative of you needing to get a life! ;-) But seriously, if you have any more specific questions on FIFO or other best practices, you should probably just email us. This thread is getting a bit long, but it may be of use to others in the same predicament. You can email me directly at: john_vallelunga -at- agilent.com. Niels and I sit only 175 feet apart and I could use the exercise anyway. |
|
|
|
> {quote:title = jvall写道:} {quote}>但是说真的,如果你对FIFO或其他最佳实践有任何更具体的问题,你应该给我们发电子邮件。 这个线程有点长,但它可能对处于同样困境的其他人有用。 我觉得这个主题非常有趣。 我甚至不拥有PNA,但阅读其中的一些东西对我来说非常有用,显然它对于拥有类似硬件的人来说可能更有用。 戴夫 以上来自于谷歌翻译 以下为原文 > {quote:title=jvall wrote:}{quote} > But seriously, if you have any more specific questions on FIFO or other best practices, you should probably just email us. This thread is getting a bit long, but it may be of use to others in the same predicament. I think the thread is quite interesting. I don't even own a PNA, but reading some of this stuff was quite useful to me, and obviously it's likely to be more useful to someone with similar hardware. Dave |
|
|
|
好的,我们可以继续在这里发帖......我不介意。 通过电子邮件回复会更快,因为我们不会整天坐在这个论坛上查看更新。 bfris,有一点我不清楚。 您是要对1500个位置中的每一个进行扫描,还是每个增量的数据点数为1500? 如果每个增量都有扫描,你有多少频率?... 11,101,1001,???? 如果您有具有101个频率点的2.25M扫描,那么这是2.25M * 101 * 2(每点值)* 4(每个值的字节数),总共大约18亿字节的数据。 这是很多数据! FIFO缓冲区最多可容纳50亿字节,因此您可能不希望每次扫描超过250个点。 这样,您可以等到整个扫描完成后再读取数据。 当然,您也可以持续阅读它。 以上来自于谷歌翻译 以下为原文 Okay, we can keep posting here...I don't mind. Responses would be faster via email because we don't sit around checking this forum for updates all day. bfris, There is one thing I am not clear on. Are you going to take a sweep for each of the 1500 positions or was 1500 the number of data points per increment? If there is a sweep for each increment, how many frequencies did you have in mind?...11, 101, 1001, ???? If you have 2.25M sweeps with 101 freq points then that is 2.25M * 101 * 2 (values per point) * 4 (bytes per value) for a total of about 1.8 billion bytes of data. That is a lot of data! The FIFO buffer can hold up to 5 billion bytes, so you probably don't want to exceed much more than about 250 points per sweep. This way you could wait until the entire scan is complete before reading the data. Of course, you could also just read it out on an ongoing basis also. |
|
|
|
哇。 这个帖子确实具有了自己的生命。 >你打算为1500个职位中的每个职位进行一次扫描。 。 。 这些术语在我在网络分析器中所做的事情和我在物理世界中所做的事情之间变得混乱。 所以我有一些电机可以将我的射频探头移动到x-y网格中,网格点高达1500 x 1500(总网格点数为2.25 M)。 对于每个网格点,我想在网络分析仪上进行S21频率扫描。 对于频率扫描,我认为11点或更少应该足以满足我想要的数据覆盖范围。 将它计算为字节,它将是(1500 x 1500)x(11个频率)x(每个点2个值)x(每个值4个字节)= 198 MB这比4 GB的FIFO要多得多。 因此,在我不得不担心溢出之前,我实际上可以执行几次x-y扫描并将数据推入FIFO中。 关于NumberOfGroups的2M限制(GROUP:COUNT)。 放宽限制会很好,但似乎网络分析器内部的错误检查可能很麻烦。 并非所有使用NumberOfGroups的人都会关心FIFO。 就此而言,并非每个设置频率扫描点数的人都关心FIFO。 以上来自于谷歌翻译 以下为原文 Wow. This thread has really taken on a life of its own. > Are you going to take a sweep for each of the 1500 positions . . . The terms get confusing between what I'm doing in the Network Analyzer and what I'm doing in the physical world. So I have some motors that are going to move my RF probe in an x-y grid of up to 1500 x 1500 grid points (total 2.25 M grid points). For each grid point, I want do a S21 frequency sweep on the network analyzer. For the frequency sweep, I'm thinking 11 points or less should more than enough for the data coverage I want. Working it out to bytes, it will be (1500 x 1500) x (11 frequencies) x (2 values per point) x (4 bytes per value) = 198 MB Which is a lot lest than 4 GB of FIFO. So I could actually perform several x-y scans and shove the data in the FIFO before I have to worry about overflow. Regarding the 2M limit on NumberOfGroups (GROUP:COUNT). It would be nice to ease the restriction, but it seems like the error checking inside the Network Analyzer could be cumbersome. Not everyone who uses NumberOfGroups is going to care about FIFO. For that matter, not everyone who sets the number of points in a frequency sweep cares about the FIFO. |
|
|
|
看起来我可以将群数限制提高到10,000,000。 这是一个非常微不足道的变化。 它将在下一个客户版本A.09.90.06中发布,可能在10月份。 如果您需要更早的内容,我们可以为您提供内部Z版本试用版,直到A版本可用。 以上来自于谷歌翻译 以下为原文 It looks like I can bump the group count limit to10,000,000. This was a very trivial change. It will come out in the next customer release, A.09.90.06, probably in October sometime. If you need something earlier, we can get you an internal Z release to tryout until the A release is available. |
|
|
|
只有小组成员才能发言,加入小组>>
2082 浏览 1 评论
1846 浏览 1 评论
1700 浏览 5 评论
2563 浏览 3 评论
将设备连接到PC并通过asic格式读取数据然后我的网络分析仪挂起
1547 浏览 4 评论
关于Keysight x1149 Boundary Scan Analyzer
349浏览 0评论
1385浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
261浏览 0评论
2248浏览 0评论
1102浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-3-29 07:17 , Processed in 0.907247 second(s), Total 53, Slave 47 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 深圳华秋电子有限公司
电子发烧友 (电路图) 粤公网安备 44030402000349 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号