8164A和8164B之间的区别

嗨Mike001，哎呀，我错过了那个用户名！
我不记得两代大型机之间的任何编程差异。
我们肯定会将8164A和8164B与lambda扫描功能互换使用。
仪器模块是否相同？
也许既然设置已经过时了，那么安装了816x即插即用驱动程序的旧版本，可能比8164B产品更旧？
在这种情况下，您可以尝试使用最新的816x驱动程序进行更新。
这与此页面相关联：[www.agilent.com/find/octfirmware]我希望能解决这个问题。
麦克风



     以下为原文

  Hi Mike001,

Gee, I missed taking that user name!
I don't remember any such programming difference between the two generations of mainframes. We definitely use the 8164A and 8164B interchangeably with the lambda scan functions. Are the instrument modules the same?
Maybe since the setup is old, there is an old version of the 816x Plug&Play driver installed, possibly older than the 8164B product?
In that case you could try updating with the latest 816x driver. That is linked from this page:
[www.agilent.com/find/octfirmware]

I hope that solves it.

Mike

嗨迈克，没关系。
您可以继续使用您的用户名。
下面是一些更详细的信息：到目前为止，我一直在使用带有TLS 81600B（插槽0）和PWM 81623A（插槽1）的Agilent 8164B主机。
执行lambdascan后，我们看到错误消息“No trigger”。
但是，使用相同的C程序和带有TLS 81680A（插槽0）和PWM 81623A（插槽1）的Agilent 8164A主机，一切正常。
你知道有什么理由吗？
此致，MikeEdited：Mike001于2013年10月24日下午3:31



     以下为原文

  Hi Mike,

That's OK. You can continue using your user name.

Here is some more detail:
So far, I've been using an Agilent 8164B Mainframe with a TLS 81600B (slot 0) and a PWM 81623A (slot 1). After we executed lambdascan, we saw error message "No trigger". 
However, using the same C program, and  Agilent 8164A Mainframe with a TLS 81680A (slot 0) and a PWM 81623A (slot 1), everything works fine.

Do you know any reason for that? 

Regards,
Mike

Edited by: Mike001 on Oct 24, 2013 3:31 PM

好的，这里有几个想法。
81600B是较新型号的激光器，因此如果程序使用旧版本的816x即插即用驱动程序，则可能无法识别81600B。
所以最好使用上面提到的最新版本。
并且可能需要在计算机中搜索任何旧版本的hp816x_32.dll文件，因为这些文件可能位于程序首先找到它们的路径中。
（就像在程序目录中一样。）然后你可以通过仪器上的内置PACT应用程序运行一个简短的测量来检查硬件，这也将检查触发。
这可以从前面板“Appl”按钮开始。
激光可以手动启动吗？
检查它是否已解锁以及后面BNC上的远程互锁是否终止。
此外，现在还有一个免费的GUI程序可用，它也使用MFlambdasscan功能，称为IL引擎，可在此处获得：[www.agilent.com/find/n7700]您可以看到设置是否运行，这也将确认
PnP驱动程序安装。
您甚至可能更喜欢将其用于测量。



     以下为原文

  OK, here are a couple ideas.

The 81600B is a newer model laser, so if the program is using an old version the 816x Plug&Play driver, it may not be recognizing the 81600B. So it is good to use the latest version, mentioned above. And it may be necessary to search the computer for any old versions of the hp816x_32.dll file, since these may be in a path where they are found first by the program. (Like in the program directory.)

Then you could check the hardware by running a short measurement with the built-in PACT application on the instrument, which will also check the triggering. That can be started from the front panel "Appl" button.

Can the laser be started manually? That checks whether it is unlocked and whether the remote interlock on the back BNC is terminated.

Also there is now a free GUI program available that also uses the MFlambdasscan functions, called the IL Engine and available here:
[www.agilent.com/find/n7700]
You could see if the setup runs with that, which would also confirm the PnP driver installation. You might even prefer to use that for your measurements.