多次校准没有得到相同的响应

增强型响应校准和1端口校准共享输入端口的相同错误术语：指向性SourceMatch ReflectionTracking因此，如果您在校准集中有增强响应校正然后执行1端口校准，则增强响应校准将是
覆盖。
反之亦然。
因此，这两种不同的校正类型不能共享相同的校准集。



     以下为原文

  An Enhanced Response cal and 1-port cal share the same error terms for input port:

Directivity
SourceMatch
ReflectionTracking

Because of this, if you have an Enhanced Response correction in a calset and then perform a 1-port cal, the Enhanced response cal will be over-written. The opposite is also true.  Therefore these two different correction types can not share the same calset.

嗨Daras，谢谢你的回复。
完成增强响应校准后，我保存.csa文件。
然后我预设了PNA，然后执行新的1端口校准并保存文件。
预设也没有帮助。
我该如何克服这个问题？
RGDS



     以下为原文

  Hi Daras,

Thank you for the response. After I finish the enhanced response cal, I save the .csa file. Then I preset the PNA and then do a new 1 port cal and save the file. The preset is also not helping. How do I overcome this problem?

rgds

好的 - 也许我不理解这里事件的确切顺序。
如果您执行增强的响应校准，然后保存.csa文件，预设该框，执行1端口校准，然后将其保存到不同的.csa文件中，然后在进行测量时，将应用的校正将
基于被召回的最后一个州。
因此，如果您想进行测量并对其应用增强的响应校正，则调用您保存的第一个.csa文件，连接DUT并进行扫描。
现在，如果您想进行测量并应用1端口校准，请调用您保存的第二个.csa文件，连接DUT并进行扫描。
我打赌您在校准向导结束时使用默认保存选项，这将校准保存在通道校准寄存器中。
另外我认为，对于增强响应校准设置和1端口校准设置，您使用相同的通道（可能是通道1？），因此在两种情况下校准都保存在通道1的校准寄存器中，即使您节省了两个
不同的.csa文件，每次调用一个，它都会覆盖通道1 cal寄存器的内容。
因此，如果您想在相同的状态下进行增强的响应测量和1端口测量（不需要在扫描测量之间调用不同的状态），那么您需要为每个测量设置2个不同的通道，这样两者都可以
修正可以在同一状态下共存。



     以下为原文

  Ok - maybe I am not understanding the exact sequence of events here.  if you do an enhanced response cal and then save a .csa file, preset the box, do a 1-port cal and then save it into a different .csa file, then when you make the measurement, the correction that will be applied will be based on the last state that was recalled.  so if you want to make a measurement and apply the enhanced response correction to it, then recall the first .csa file that you save, connect the DUT and take a sweep. now if you want to make a measurement and apply the 1-port calibration, recall the 2nd .csa file you saved, connect the DUT and take a sweep.

I am betting that you are using the default save option at the end of the Calibration wizard, which saves the calibration in the channel cal register.  Also I am betting that for both the enhanced response cal setup and the 1-port cal setup you are using the same channel (probably channel 1?) so in both cases the calibrations are saved into Channel 1's cal register and even though you save two different .csa file, each time one is recalled, it overwrites the contents of the channel 1 cal register.  so if you want to make an enhanced response measurement and a 1-port measurement in the same state (without recalling a different state in between sweeping the measurements), then you need to setup 2 different channels for each of the measurements, so that both corrections can coexist in the same state.

嗨Daras，校准顺序如下。正如您所指出的，我们正在使用通道1进行两次测量。
1.将DNA设置为DUT的工作频率。
2.做一个增强的响应cal。
3.将state和cal文件另存为enhanced_resp.csa 4.预设PNA。
5.设置PNA以获得DUT的工作频率。
6.进行1端口校准。
7.将state和cal文件保存为1port_resp.csa。
现在进行测量。
我记得测量的enhanced_resp.csa。
我发现这个cal与enhanced_resp.csa不同。
它被1port cal覆盖。
PNA上的预设无助于将校准和状态保存为其他文件？
我们是否必须为机器人创建一个单独的通道来协助？
RGDS



     以下为原文

  Hi Daras,

The sequence of calibration is as follows.As you have pointed out we are using Channel 1 for both the measurements.

1. Set the PNA for the frequency of operation of the DUT.
2. Do an enhanced response cal.
3. Save the state and cal file as enhanced_resp.csa
4. Preset the PNA.
5.Set the PNA for the frequency of operation of the DUT.
6.Do a 1 port calibration.
7. Save the state and cal file as 1port_resp.csa.

Now for the measurements.

1. I recall the enhanced_resp.csa for the measurement. I find that this cal is not the same as the enhanced_resp.csa. It is being overwritten by the 1port cal. The preset on the PNA does not help to save the cal and state as a different file?

DO we have to create a separate channel for bot the cals to co-esist?

Rgds

> {quote：title = nsm写道：} {quote}> 1.我想起了测量的enhanced_resp.csa。
我发现这个cal与enhanced_resp.csa不同。
它被1port cal覆盖。
PNA上的预设无助于将校准和状态保存为其他文件？
>这似乎有点奇怪。
如果您正在调用.csa文件，它应该将通道校准寄存器恢复为保存.csa文件时通道1校准寄存器中的任何内容。
自保存.csa文件以来，您在该通道中执行的其他校准无关紧要。
它应该覆盖已经存在的任何东西。
你可以发布你的enhanced_resp.csa和1Port_resp.csa文件，还要注意你正在使用的固件版本？



     以下为原文

  > {quote:title=nsm wrote:}{quote}
> 1. I recall the enhanced_resp.csa for the measurement. I find that this cal is not the same as the enhanced_resp.csa. It is being overwritten by the 1port cal. The preset on the PNA does not help to save the cal and state as a different file?
> 

this seems a bit odd.  if you are recalling the .csa file it should restore the channel cal register to whatever was in the channel 1 cal register when you saved the .csa file.  it should not matter what other calibrations you have performed in that channel since you saved the .csa file.  it should over-write anything that is already there.  can you post both your enhanced_resp.csa and 1Port_resp.csa files and also note what firmware revision you are using?

嗨Daras，我使用的是PNA E8362C固件版本A.09.33.09。
请找到附件。
F1P是一个端口呼叫，F2P是增强的响应cal。
Rgds nsm
Rx_June6_F1P_T1.csa1,000.4 KB



     以下为原文

  Hi Daras,

I am using the PNA E8362C firmware revision A.09.33.09. Please find the files attached. The F1P is aone port call and the F2P is the enhanced response cal.

Rgds
nsm

附件

• Rx_June6_F2P_T1.csa1,000.3 KB
  
• Rx_June6_F1P_T1.csa1,000.4 KB
  

虽然daras会对召回内容进行排序，但我建议您将每个保存为命名用户calset，例如nsm_oneport nad nsm_enhanced;
通过这种方式，他们可以独立地明确保存。
我几乎从不使用默认的cal寄存器，因为它很容易被其他校准损坏，并且很难知道它何时被破坏;
损坏我的意思是你可以做一个1端口的cal，然后是一个响应cal，然后是另一个端口上的1端口cal并且一切正常，那么如果你做了一个强化响应，1端口和respone cal被覆盖，
但是端口2上的旧1端口校准是留下的（这是故意的，但它也可能会让人感到困惑;它是故意的，所以你可以在每个端口上建立许多不同的校准，例如响应和1个端口，一个在
时间，但使用guied power cal消除了对此的需要）。
因此，保存到用户校准集，看看是否修复了所有内容。
另外，我认为在C版本上最多可以使用9.42，而且我知道在该版本中修复了很多东西;
这将是C版本的最终主要分支，因为我们刚刚推出了新版本的PNA-L：http：//www.home.agilent.com/sec/product.jspx？nid = -536902643.1017780.00＆amp ;pselect
= SR.Looking＆amp; pageMode = OV＆amp; lc = eng＆amp; cc = US oops，我刚看到它是你正在使用的PNA;
无论如何，你也可以使用9.42。编辑：Dr_joel于2012年6月13日上午11:24



     以下为原文

  While daras sorts out the recall stuff, might I recommend that you save each as a named user calset, such as nsm_oneport nad nsm_enhanced; in that way they are explicitly saved independetly.  I almost never use the default cal register as its is easily corrupted by other calibrations and it's hard to know when it gets corrupted; by corrupted I mean that you can do a 1 port cal, then a response cal, and then a 1 port cal on the other port and it's all ok, then if you do an enhaced response, the 1 port and respone cal are overwritten, but the old 1-port cal on port 2 is left around (it's intentional, but it can also get confusing; it's intentional so you can build up a lot of different calibratoins such as response and 1 ports, on each port, one at a time, but using the guied power cal eliminates the need for this now). 

So, save to a user cal set and see if that fixes everything.  Also, I think you can use up to 9.42 on the C versions, and I know of lot of things are fixed in that version; and that will be the final major branch for C versions as we just introduced a new version of the PNA-L: 

http://www.home.agilent.com/sec/product.jspx?nid=-536902643.1017780.00&pselect=SR.Looking&pageMode=OV&lc=eng&cc=US

oops, I just saw that it is a PNA you are using; anyway, you can use 9.42 on that as well.

Edited by: Dr_joel on Jun 13, 2012 11:24 AM

嗨，我在运行A.09.33.09版本固件的E8364C PNA上调用了这些文件，它表现得如预期的那样。
当我回想起F2P文件时，S21测量结果通过增强响应校正进行校正（您可以通过查看状态栏进行确认 - 它应该说“C Enh Resp”）。
当我回想起F1P文件时，S11测量通过1端口校正进行校正（状态栏显示“C 1端口”）。
所以基本上，我没有观察到这个问题被错误地覆盖了。
由于我们无法重现问题（部分问题可能是错误传达），我建议您致电安捷伦支持热线或联系您当地的安捷伦代表，以便我们提供更好的实际操作，面对面的支持
。



     以下为原文

  Hi nsm,

I recalled these files on an E8364C PNA running A.09.33.09 version of firmware and it behaved as expected.  when I recall the F2P file, the S21 measurement is corrected with an Enhanced Response correction (you can confirm by looking at the status bar - it should say "C Enh Resp"). And when I recall the F1P file, the S11 measurement is corrected with a 1-port correction (Status Bar says "C 1-Port").  So basically, I am not observing this issue of an improperly overridden calset.  Since we can't recreate the issue (and part of the problem might be miscommunication), I would recommend that you call the Agilent support hotline or contact your local Agilent rep, so that we can provide better hands-on, face to face support.