是德科技
直播中

孙燕冉

7年用户 328经验值
私信 关注
[问答]

请问谁能查看触发设置未被保存的组并解决其他小问题吗？

嗨，我目前正在使用A.09.42.12固件。
我有一个.csa文件，我想将所有测量通道的组触发器设置为10。
但是，每当我回想起该文件时，它都会恢复为1.因此，由于某种原因，该设置未被保存。
这是一个痛苦，因为我有大约30多个频道，我必须一个接一个地将它改回10。
此外，以下是我遇到的一些其他小固件问题：1）在IM频谱测量类中，如果指定10kHz范围，则右边列出的频率不正确。
（详见附件）。
例如，它应该是999.995Mhz到1.000005 Ghz，而不是1.00001Ghz。
2）当使用具有较旧固件版本的PNA时，它将列出生成pdf打印输出时“跟踪属性表”中使用的平滑量。
但是使用新固件，这些信息似乎已经消失了！
3）对于具有多个标记的单个迹线，如果我对其启用跟踪统计，它将仅显示其中一个标记，并用统计表覆盖其余部分。
我不明白为什么你不能同时显示所有标记和统计表。
4）使用向导使用e-cal单元进行校准时，在某些步骤中，我注意到端口上的蓝灯已经点亮，甚至有机会点击“测量”按钮并将其连接到e-
cal端口！
我担心这可能会造成一些辐射危险，特别是在高功率和频率水平校准时。
如果有人可以查看触发设置未被保存的组并解决其他小问题，那将非常感激。
韩国

以上来自于谷歌翻译


     以下为原文

  Hi,

I'm currently using A.09.42.12 firmware. I have a .csa file where I want to to set the group trigger to 10 for all the measurement channels. However, everytime I recall the file, it reverts back to 1. So that setting is not being saved for some reason. It is a pain, since I have about 30+ channels and I have to change it back to 10 again one by one.  

Also, here are some other minor firmware issues I have encountered:

1) In the IM spectrum measurement class, if you specify a 10kHz span, the frequency listed at the right edge is incorrect. (see attached for details). For the example, it should be 999.995Mhz to 1.000005 Ghz, not 1.00001Ghz.  

2) When using the PNA with the older firmware version, it would list the smoothing amount used in the 'Trace Attributes Table' when generating a pdf printout. But with the new firmware, that information seems to have disappeared!  

3) For a single trace with several markers, if I enable trace statistics on it, it will only show 1 of the markers and cover the rest up with the statistics table. I don't see why you can't show all the markers and the statistics table at the same time.

4) When performing a calibration with an e-cal unit using the wizard, during some steps, I noticed the blue light on the ports already lit on before even having a chance to click the 'Measure' button and connecting it to the e-cal port! I am worried this might pose some radiation risk, especially when calibrating at high power and frequency levels.  

If someone can looking into the group triggering settings not being saved and address the other minor issues, that would be greatly appreciated.

rok   
附件

回帖（9）

庞书娟

2019-6-4 12:34:46
您好，您是对的，在召回期间未恢复群组的触发计数。
我提交了一个缺陷，我们将在下一个版本中修复它。
关于您的逐项注释：1）IMD频率：这是显示注释舍入的工件。
我们在显示器上的空间有限，因此我们必须限制写在这个表面上的所有幅度和刺激数的分辨率。
这不是IM Spectrum特有的，但在IMD和IMS中，由于为这些通道配置频率的方式，您会更倾向于注意到它。
2）打印跟踪属性表中缺少平滑数字。
此功能在我们的标准参数化通道中可用，但在其他通道类型的打印输出中缺失。
3）显示跟踪统计信息时，标记显示受限。
我将把上述三条评论转发给我们的用户界面工程师。
4）在按下“测量”之前打开端口。
这样做是为了向用户提供实时跟踪，可用于确保正确连接下一个标准。
远程接口不会以这种方式运行。
但图形校准向导故意有这种行为。
与许多消费类设备（如手机）相比，本机端口功率非常低。

以上来自于谷歌翻译


     以下为原文

  Hello rok,

You are correct, the trigger count for groups is not restored during recall.  I'm submitting a defect against this and we will fix it in our next release.

With regard to your itemized comments:
1)  IMD frequency:  this is an artifact of display annotation rounding.  We have limited space on the display, consequently we have to limit the resolution of all amplitude and stimulus numbers written on this surface.  This is not peculiar to IM Spectrum, but in IMD and IMS you'll tend to notice it more due to the way frequency is configured for those channels. 

2)  Smoothing number missing from the print trace attributes table.
  This feature is available in our standard sparameter channel but is missing from the print outs for the rest of our channel types.

3)  Marker display limited when trace statistics is displayed.

I will forward all three of the above comments to our user interface engineer.  

4)  Cal ports on before pressing "Measure".  This is done to provide the user with a live trace that can be used to ensure that the next standard is connected properly.  The remote interface does not behave this way.  But the graphical cal wizard intentionally has this behavior.   The native port power is quite low compared with many consumer devices such as cell phones.
举报

孙燕冉

2019-6-4 12:47:05
引用: wyerwerwz 发表于 2019-6-4 12:34
您好，您是对的，在召回期间未恢复群组的触发计数。
我提交了一个缺陷，我们将在下一个版本中修复它。
关于您的逐项注释：1）IMD频率：这是显示注释舍入的工件。

你好，谢谢你的回复。
我的操作员今天发现了另一个UI评论。
对于SMC通道，如果我选择S11测量迹线以获得RF回波损耗，则默认显示的x轴是IF输出频率范围的x轴，而不是RF输入频率范围。
我知道我可以手动更改它，但如果固件可以自动默认为正确的x轴范围，那将是很好的，以匹配正常的s参数测量类的行为。
再次感谢，rok

以上来自于谷歌翻译


     以下为原文

  Hi,

Thanks for the reply. I have another UI comment to pass along that my operator discovered today. For an SMC channel, if I pick the S11 measurement trace to get RF return loss, the x axis displayed by default is that of the IF output frequency range, instead of the RF input frequency range. I know I can manually change it, but it would be nice if the firmware can be made to automatically default to the right x axis range just for that case, to match the behavior of the normal s-parameter measurement class. 

Thanks again,
rok
举报

刘华湘

2019-6-4 12:54:22
引用: 蓝色冰汐 发表于 2019-6-4 12:47
你好，谢谢你的回复。
我的操作员今天发现了另一个UI评论。
对于SMC通道，如果我选择S11测量迹线以获得RF回波损耗，则默认显示的x轴是IF输出频率范围的x轴，而不是RF输入频率范围。

感谢您的评论。
关于让参数的输入或输出性质决定适当的x轴是什么，我们已经玩弄了这个想法。
对于像S11或IPwr这样的参数的SMC，选择似乎很明显，但对于SC21或SC12这样的传输参数来说并不那么明显。
由于在同一通道中对不同参数具有不同的x轴，还会产生其他影响。
例如，假设窗口中有S11和SC21轨迹，S11使用输入范围作为x轴，SC21使用输出范围。
在SC21轨迹上，您会注意到一个很大的异常，并在该位置放置一个标记。
您可能会认为异常是由于输入处的不匹配导致的，并且想知道在异常发生的同一频率下返回损耗是多少。
如果你尝试耦合标记方法，它将无法工作，因为标记位置是从x轴选择键入的，并且两条迹线具有不同的x轴。
我的观点不是找借口，而是为了说明这种特殊的行为选择是那些无论我们默认做什么都会让人感到高兴而有些人不那么开心的行为之一。
我们在SMC通道中的妥协是将所有x轴范围选择默认为一个范围（即输出），但允许用户实际更改各个迹线上的x轴范围。

以上来自于谷歌翻译


     以下为原文

  thank you for your comment.  we have toyed with this idea before about letting the input or output nature of the parameter decide what the appropriate x-axis is.  in the case of SMC for parameters like S11 or IPwr, the choice seems obvious, but it is not so obvious for the transmission parameters like SC21 or SC12.  there are also other implications resulting from having different x-axis on different parameters in the same channel.  As an example imagine you have an S11 and SC21 trace in the window and the S11 is using the input range as the x-axis and the SC21 is using the output range.  on your SC21 trace, you notice a large anomaly and you place a marker on the location.  you might think that the anomaly is due to a bad mismatch at the input and want to know what the return loss is at the same frequency where the anomaly occurs.  if you try the coupled markers approach, it won't work because marker positions are keyed off of the x-axis selection and the two traces have different x-axes.

my point wasn't to make an excuse, but to illustrate that this particular choice of behavior is one of those that no matter what we decided to do by default, would make some people happy and some people not so happy.  our compromise in the SMC channel was to default all the x-axis range selections to one range (namely output), but allow the users to actually change the x-axis range on individual traces.
举报

陈键

2019-6-4 13:02:55
嗨，另一种处理显示跟踪统计时可见的有限数量标记的方法是查看标记表中的各个标记。
有几种方法可以打开标记表。
这是一种方式：按Marker，More Markers，Marker Table ON。

以上来自于谷歌翻译


     以下为原文

  Hi, 
Another alternative for dealing with the limited number of markers visible when showing Trace Statistics is to view the individual markers in the Marker Table.  There are several ways to turn on the Marker Table.  Here's one way: press Marker, More Markers, Marker Table ON.
举报

更多回帖

9 0 0

相关问答

频率
发帖
电子发烧友APP
|投诉反馈|电子发烧友网
© 2021 bbs.elecfans.com
湘ICP备2023018690号
×
20
完善资料，
赚取积分