完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
您好,我一直试图找出如何使用PNA-X A.09.42.12固件获取特定通道的列表跟踪编号(屏幕上带有'Tr'注释)。
我试过'CALC:PAR:MNUM?' 命令,但它似乎只返回该通道号的最高跟踪号。 我想要的是如果我为特定的通道号创建多个多个跟踪,我想知道整个跟踪('Tr注释)数字列表,即使这些跟踪在不同的窗口中,因为它们绑定到同一个通道。 请注意,这些跟踪可能是由程序创建并手动手动创建的组合,因此跟踪名称可能不同。 所以我不能使用'CALC:PAR:CAT:EXT?',因为跟踪名称的不确定性。 这就是为什么我依赖于跟踪Tr注释编号。 任何解决方案将不胜感激。 谢谢,rok 以上来自于谷歌翻译 以下为原文 Hello, I've been trying to figure out how to get a list trace numbers (with the 'Tr' annotation on screen) for a particular channel, using the PNA-X A.09.42.12 firmware. I tried the 'CALC:PAR:MNUM?' command, but it seems to only return the highest trace number for that channel number. What I want is if I created multiple multiple traces for a particular channel number, I want to know the entire trace ('Tr annotation) number list, even if these traces are in different windows, since they are tied to the same channel. Note that these traces may be a combination of being created by a program and manually created by hand, so the trace names may be different. So I can't use 'CALC:PAR:CAT:EXT?', because of the uncertainty in trace names. That's why I'm relying on trace Tr annotation number instead. Any solution would be greatly appreciated. Thanks, rok |
|
相关推荐
6个回答
|
|
真正的问题是你想用这些信息做什么。
我们有独特的测量数字和测量名称。 测量数字对应于每个显示的迹线的“Tr#”标签。 测量编号和测量名称用于:用于选择特定测量的CALC操作。 但是,对于与显示相关的操作,例如将标签与轨迹相关联或设置比例,您需要知道相对于它所在窗口的测量的跟踪编号(顺便说一下,我真的不喜欢这个方案)。 在显示操作的情况下,唯一标识符是一对数字(winNum,traceNum)。 但是,此“traceNum”与该跟踪上的“Tr#”标签不同。 因此,如果您只想在设置中找到所有Tr#的列表(如下例所示),那么您可以使用“SYST:MEAS:CAT?”,但如果您告诉我们您要尝试做什么 信息,然后我们可以为您的用例提供更具体的示例。 !HTTPS://dl.dropbox.com/u/87949221/TraceNumbers.jpg! 以上来自于谷歌翻译 以下为原文 The real question is what are you trying to do with this information. We have measurement numbers and measurement names that are unique. The measurement numbers correspond to the "Tr#" labels for each displayed trace. Measurement numbers and measurement names are used in :CALC operations for selecting specific measurements. However, for display related operations, like associating labels with traces or setting up scales, you need to know the trace number of the measurement relative to the window in which it resides (by the way, I really don't like this scheme). In the case of the display operation, the unique identifier is a pair of numbers (winNum, traceNum). This "traceNum" however, is not the same as the "Tr#" label on that trace. So if you simply want a list of all the Tr#'s in your setup (like the example below), then you can use the "SYST:MEAS:CAT?", but if you tell us what you are trying to do with the information, then we can provide a more specific example for your use case. !https://dl.dropbox.com/u/87949221/TraceNumbers.jpg! |
|
|
|
你好,谢谢你的回复。 我正在尝试创建一个程序,允许用户加载他们想要的任何状态文件。 如果他们想要对他们看到的特定轨迹(即基于显示的Tr注释)进行数据转储,他们可以输入它,我将尝试查找它是否存在,如果是,则从该轨迹中获取数据。 理想情况下,我需要的命令可以让我首先检查“Tr”特定数字是否存在,然后能够选择它来进行数据转储。 'SYST:MEAS:CAT?' 似乎可以做到这一点。 我再次重新检查了命令,我必须对它进行修改,因为我认为它返回了测量名称,基于帮助文件中的示例(基于“返回所有测量名称”行),而不是测量数字。 如果可以修复帮助文件中的示例以指示它返回测量编号而不是测量名称,则有助于避免进一步混淆。 另外,我对'SYSTem:MEASurement:TRACe?'感到困惑。 下面列出的命令。 它声明它返回指定测量编号的跟踪编号。 基于上一个命令,我原本认为测量编号代表了跟踪编号。 但是当我在一个窗口内的某些测量中尝试它时,它返回+1,+ 2和+3,所以我认为'跟踪号'实际上意味着在特定窗口内的跟踪排序,而不是带注释的'Tr'数字。 也许在将来的帮助文件中,可以有一个部分列出引用特定实体的所有不同命名法。 (即窗口,通道,跟踪名称,Tr注释数字或测量编号,跟踪编号等)或稍微修改术语,以便人们不会将“跟踪编号”与“Tr”注释编号相关联。 现在,如果有办法选择测量数而不必弄清楚它与哪个通道相关联,那就更好了。 按照上面提到的方式,我将不得不搜索每个频道,直到找到有问题的特定“Tr”曲目。 再次感谢,rok 以上来自于谷歌翻译 以下为原文 Hi, Thanks for the reply. I'm trying to create a program that allows the user to load up any state file they want. If they want to do a data dump on a particular trace they see, (i.e. based on the displayed Tr annotation), they can input that and I'll try to find if it exists and if so, grab the data from that trace. Ideally, I need commands that would allow me to first check the existence of of the 'Tr' specific numbers and then have the ability to select it to do the data dump. The 'SYST:MEAS:CAT?' seems to do the trick. I re-examined the command again and I must have glossed over it, because I thought it returned measurement names, based on the example in the help file (based on the 'Returns all measurement names' line), rather than measurement numbers. If the example in the help file can be fixed to indicate that it returns measurement numbers rather than measurement names, that would help to avoid further confusion. Also, I'm confused by the 'SYSTem:MEASurement:TRACe?' command listed further below. It states it returns the trace number of the specified measurement number. Based on the previous command, I would have thought the measurement number would have represented the trace number. But when I tried it on some measurements within a window, it returns +1, +2, and +3, so I figure that 'trace number' actually means trace ordering within a particular window, rather than the annotated 'Tr' number. Perhaps in the future help files, there can be a section listing all the different nomenclature in referencing particular entities. (i.e. windows, channels, trace name, Tr annotated number or measurement number, trace number, etc) Or modify the terminology a bit so that people wouldn't associate 'trace number' with 'Tr' annotated number. Now if there was a way to select the measurement number without having to figure out what channel it is associated with, that would be even better. With the way you mentioned above, I'll have to search each and every channel until I find the particular 'Tr' trace in question. Thanks again, rok |
|
|
|
蓝色冰汐 发表于 2019-4-15 20:18 我已经要求我们的学习产品工程师查看这些主题,并确保示例和描述正确且清晰。 至于你建议通过简单地使用唯一的测量数字(即不知道频道号码)来选择测量的方法,我认为这是一个非常合理的请求,而且我们可能应该已经有了。 我们肯定会接受这个建议并且可能实现一个看起来像这样的命令:: SYSTem:MEASurement [:SELECT]然而,在这一点上,我不能做出任何承诺,因为我们的下一个可用 即将发布的2个版本正处于最终质量保证阶段,新功能将被锁定。 以上来自于谷歌翻译 以下为原文 I've already asked our learning products engineer to take a look at those topics and make sure that the examples and descriptions are correct and clear. As to your suggestion for a way to select a measurement by simply using the unique measurement number (i.e without knowing the channel number), I think it is a very reasonable request and one that we probably should have already had. We will definitely take this under advisement and probably implement a command that might look something like this: :SYSTem:MEASurement[:SELECT] However, at this point, I can't make any promises as to when this will be available since our next 2 impending releases are in final QA phase and new features are locked out. |
|
|
|
Topcbpcba 发表于 2019-4-15 20:35 嗨,感谢您考虑为将来的版本添加新命令。 这将是非常有帮助的,因为我有一些状态文件,有近100个频道! 再次感谢,rok 以上来自于谷歌翻译 以下为原文 Hi, Thank you for your consideration of adding in the new command for future releases. It would be extremely helpful, since I have some state files which have nearly 100 channels! Thanks again, rok |
|
|
|
要迁移,sourceId:103164 以上来自于谷歌翻译 以下为原文 to be migrated, sourceId: 103164 |
|
|
|
我修复了这个例子,但我也想创建一个详细讨论这个问题的主题。
根据Dara编写的程序长度,我同意这样的命令是完全合适的。 http://na.tm.agilent.com/pna/help/latest/Programming/GP-IB_Command_Finder/System.htm#measCat 以上来自于谷歌翻译 以下为原文 I fixed the example, but I also want to create a topic that discusses this in detail. And based on the length of the program that Dara wrote, I agree that a command like this is entirely appropriate. http://na.tm.agilent.com/pna/help/latest/Programming/GP-IB_Command_Finder/System.htm#measCat |
|
|
|
只有小组成员才能发言,加入小组>>
1231 浏览 0 评论
2351 浏览 1 评论
2161 浏览 1 评论
2026 浏览 5 评论
2910 浏览 3 评论
976浏览 1评论
关于Keysight x1149 Boundary Scan Analyzer
709浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
809浏览 0评论
1234浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-27 18:45 , Processed in 1.599260 second(s), Total 87, Slave 72 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号