internal alignments - I connected AMPTD REF OUT to INPUT and after some warmup time set it to "
2018-12-25 16:12
朋友购买了二手N9912A * S / N US48310198 *固件A.03.06 *固件版本2009-03-31 14.54 *好像已经过校准/验证？通过“PLLB Elettronica”我不知道日期，因为没有校准贴纸。选项包括：106 6 GHz电缆和天线分析仪110传输测量111 QuickCal 231 6 GHz频谱分析仪235频谱分析仪前置放大器302外部USB支持303网络分析仪功能308矢量电压表他希望我在发送给他之前查看。我知道固件已经过时了，但我不想更新它，因为这可能会退回给卖家。我只和N9912A玩了一会儿，但我曾经拥有一台N9923A，所以之前遇到过FieldFox。无论是使用网络分析仪（NA）模式还是电缆和天线测试仪（CAT）模式，都让我觉得很奇怪。两者都显示出奇怪的结果。只是打开，而不是做任何类型的cal，我相信它应该使用CalReady。有一个短接头的同轴电缆，每端有N个连接器，我看到：* S21在751.750 MHz处显示峰值+1.88 dB * S21在2671.11 MHz处显示最小值-8.40 dB参见附图我从屏幕上看。这对我没有任何意义。为了尽可能地检查我的能力，我1）使用12磅的扭矩扳手来获得连接器上的扭矩2）更换电缆。但它不会改变结果。我没有尝试过机械校准套件或适合的QuickCal选件。但是我怀疑如果CalReady离这么远，那么就有某种错误。我可能能够通过校准来“隐藏”这个故障，但它并没有解决基本问题。有什么想法吗？考虑到两个测试端口之间只有一根短的高质量电缆，这看起来很奇怪吗？戴夫 以上来自于谷歌翻译 以下为原文A friend has bought a used N9912A * S/N US48310198 * Firmware A.03.06 * Firmware build 2009-03-31 14.54* Seems to have been calibrated/verification ?? by "PLLB Elettronica" I've no idea of the date, as there is no cal sticker. Options are: 106 6 GHz cable and antenna analyzer 110 Transmission measurement 111 QuickCal 231 6 GHz spectrum analyzer 235 Preamp for spectrum analyzer 302 External USB support 303 Network analyzer capability 308 Vector voltmeter He wants me to look at before sending on to him. I know the firmware is old, but I don't wish to update it yet, since this might be returned to the seller. I've only played with the N9912A a little but I used to own an N9923A, so have met a FieldFox before. Something strikes me as very odd either using network analyzer (NA) mode, or cable and antenna tester (CAT) mode. Both show bizare results. Just switching on, and not doing any sort of cal, I believe it should use the CalReady. With a short bit of coax with N connectors each end, I see: * S21 showing a peak +1.88 dB at 751.750 MHz * S21 showing a minimum of -8.40 dB at 2671.11 MHz See attached photo I look from the screen. This does not make any sense to me. To check things best I could, I 1) Used a 12 lb in torque wrench to get the torque on the connectors right 2) Changed the cable. but it does not change the result. I've *not* tried a mechanical cal kit or the fitted QuickCal option. But I'm suspicious if CalReady is so far off, then there is a fault of some sort. I might be able to "hide" this fault by calibration, but it does not solve the basic problem. Any thoughts? Does this look odd, given there is only a short high quality cables between the two test ports? Dave附件dubious-S21-measurement-on-short-N-N-cable.jpg557.5 KB
2019-03-11 15:50
我希望安捷伦支付我找到FieldFox的错误 - 我会成为一个富翁。在菜单中显示该连接器类型的任何校准套件之前，似乎需要至少两个相同连接器类型的校准套件。我可举几个例子，但最容易再现的是85039B 75欧姆F型连接器。 85039B位于固件中，是固件中唯一的F连接器套件。但是如果选择F型连接器，则无法看到85039B。附加文件“copy_of_85039B.xml”实际上与FieldFox中的“85039B.xml”文件相同。唯一的区别是“标签”行，我修改为读取85039B的副本如果文件“copy_of_85039B.xml”现在加载到FieldFox中，则会看到两个校准套件1）85039B 2）85039B的副本，而之前有没有用于F连接器。这个错误不是特定于F连接器，因为我看到7 mm套件和我制作的SMA套件的相同行为。戴夫 以上来自于谷歌翻译 以下为原文I wish Agilent would pay me for finding FieldFox bugs - I would be a rich man. It would appear that there needs to be at least two calibration kits of the same connector type before any of the calibration kits of that connector type are shown in the menus. I could give several examples of this, but the most easily reproduced is the 85039B 75 Ohm F-connector. The 85039B is in the firmware, and is the only F-connector kit in the firmware. But if you select the type F connector, the 85039B can't be seen. The attached file "copy_of_85039B.xml" is virtually identical to the "85039B.xml" file in the FieldFox. The only difference is the "Label" line, which I modified to read copy of 85039B If the file "copy_of_85039B.xml" is now loaded into the FieldFox, one sees two calibration kits 1) 85039B 2) copy of 85039B whereas previously there were none for the F-connector. This bug is not specific to the F-connector, as I see the same behavior with 7 mm kits and an SMA kit I made. Dave附件copy_of_85039B.xml4.6 KB
2019-01-08 14:47
当在Windows 10启动MPLAB X时，程序挂在“启动模块”上，不会响应。 以上来自于百度翻译 以下为原文 When starting MPLAB X in Windows 10 the program hangs at "starting modules"and will not respond.
2019-01-29 07:24
这刚刚开始，正在运行3.4，它随机关闭了IDE。重新打开，做了同样的事情，有时它会立即做其他的时间大约几分钟。下载3.6，仍然在发生。我在Windows 10 PC上，我刚刚安装了Windows的更新，但除了MPLAX，没有其他东西崩溃。有什么想法来诊断这个？ 以上来自于百度翻译 以下为原文 This just started happening, was running 3.4 and it randomly closed out of the IDE.reopened and did the same thing, sometimes it will do it immediately other times about a few minutes in.downloaded 3.6 and still happening.Im on a windows 10 PC and I just installed an update for windows but nothing else is crashing except mplab x.any ideas how to diagnose this?
2019-04-08 08:29
