34401A RS232连接问题

你手上有一个谜！
有一种可能性。
检查AppTabDB文件夹。
如果PC重置时损坏了，可以解释一下。
此文件夹位于C： Program Files（x86） Keysight  BenchVue  Platform  Service  AppTabDB 。
您可以将此文件夹替换为此文件夹以查看是否修复了该文件夹：[https://www.dropbox.com/s/vi0y4u4sfylvvur/AppTabDB.zip?dl=0]此外，如果您可以请转到齿轮图标，
选择“报告问题”，然后将生成的zip文件发送给我，我将查看日志文件，看看是否有任何突出。
布赖恩



     以下为原文

  You do have a mystery on your hands! There is one possibility. Check your AppTabDB folder. If it got corrupted when your PC reset, it could explain this. This folder is located at C:Program Files (x86)KeysightBenchVuePlatformServiceAppTabDB. You can replace this folder with this one to see if it fixes it: 

[https://www.dropbox.com/s/vi0y4u4sfylvvur/AppTabDB.zip?dl=0]

Also, if you could please go to the gear icon and select "Report an Issue", then send the resulting zip file to me, I will look at the log files and see if anything stands out.

Brian

谢谢Brian，替换该目录已经解决了问题！
我已生成一个报告，并将生成的ZIP文件附加到此线程（我不知道如何直接发送给您）。
另一方面，虽然它可能不那么重要，因为我在尝试修复此问题时重新安装并修复了Keysight库和其他相关应用程序的安装，BenchVue中的所有应用程序都报告PRO试用期已过期（即使我
从未有过试用期。
这是我必须忍受的东西吗？
再次感谢！



     以下为原文

  Thanks Brian,

Replacing that directory has fixed the problem!

I have generated a report, and attached the resulting ZIP file to this thread (I wasn't sure how to send to you directly).

On another note, although it is probably not that important, since I reinstalled and repaired installations of the Keysight libraries and other associated applications whilst trying to fix this problem, all the apps within BenchVue report that the PRO Trial period has expired (even though I've never had a trial period). Is this something that I will just have to live with?

Thanks again!

附件

• 20160120_071445116_271be2f40ad84d089009f3557c6acb23.zip118.3 KB
  

很高兴听到这个有用！
现在，如果我们能弄明白为什么！
日志将非常有用，谢谢。
当您点击BV中的“报告问题”时，它会将其拉上并创建一封电子邮件，并将其作为附件发送。
然后将该电子邮件发送到keysight dot com的benchvue dot support，直接发送给我。
编辑此回复 - 抱歉，忘记回答其他问题...我们发现如果您以一位用户身份登录，开始3​​0天试用，然后以其他用户身份登录，则会报告您的试用版已过期。
你有两个不同的登录？
如果是这样，请尝试另一个。
如果没有，那么这又是试验许可证过早失效的又一个案例，我们想要了解更多关于事件链的详细信息，尽可能详细记录。
Brian编辑：w0dz于2016年1月19日下午2:05



     以下为原文

  Glad to hear that worked! Now if we could just figure out why! The logs will be useful, thanks. When you click the "Report an Issue" in BV, it zips them up and creates an email with them as an attachment. That email is then sent to benchvue dot support at keysight dot com, which comes directly to me.

Editing this response -- sorry, forgot to answer the other question...

We have found that if you log in as one user, start the 30 day trial, then log in as a different user, it reports that your trial has expired. Do you have two different logins? If so, try the other one. If not, then this is one more case of the premature expiration of the trial license, and we'd like more details as to exactly what the chain of events was, in as much detail as you can remember.

Brian

Edited by: w0dz on Jan 19, 2016 2:05 PM

谢谢Brian，我只登录了一个用户。
我可能有一个访客帐户，但我从不使用它。
我记忆中最好的事件链如下：1。我下载并安装了最新的BenchVue。
除此之外，还安装了IO库。
2.我通过串口USB连接了我的34401A并运行了Keysight Connection Expert。
3.我手动添加了仪器，然后在仪器屏幕上更新了34401A的驱动程序（下载并安装了IVI驱动程序）。
然后我跑了BenchVue，我无法“显示”34401A。
5.此时我在我的PC上运行了一个终端程序，并尝试自己直接连接到34401A，由于Connection Expert已连接到串口，我认为存在一些冲突，终端程序停止响应。
6.此时我离开了我的电脑，当我回来时它重新开始（我不知道为什么）。
7.一旦重新启动，我无法运行BenchVue，因为我在启动屏幕后收到错误消息，无法联系到许可证服务器或其他什么，我应该等待几秒钟或重新启动。
我做了两个，等待，然后重新启动。
仍无济于事。
我无法让BenchVue运行。
9.然后我卸载并重新安装BenchVue。
10.它仍然无法运行（即使重启后）。
11.然后我运行控制面板 - >程序和功能，并注意到应用程序“是德科技许可证服务”。
这可能是问题，但我右键单击并在此应用程序上点击修复。
12. BenchVue然后运行正常，我现在可以第一次看到该仪器，但我也被告知我的试用期已经过期。
13.我开始使用仪器记录一些电压（大约50分钟左右，在几个开始停止会话中）。
在这一点上，我离开我的电脑有点做一些硬件的东西，并注意到屏幕已经空白（我认为这只是屏幕保护程序），但随后PC重新启动。
我不确定导致意外重置的原因，但我通常没有意外的重置，这是自安装Keysight应用程序以来的第二个。
14.重新启动后，我再也看不到BenchVue中的仪器了，剩下的就是历史了。
我希望这有点帮助。
谢谢你快速回复。
贾斯汀。



     以下为原文

  Thanks Brian,

I've only logged on as the one user. I may have a guest account, but I never use it.

The chain of events as best I can remember is as follows:

1. I downloaded and installed the latest BenchVue. Along with this, the IO libraries were also installed.
2. I connected my 34401A via serial-USB and ran Keysight Connection Expert.
3. I manually added my instrument, and then in the instrument screen I updated the drivers for the 34401A (which downloaded and installed the IVI drivers).
4. I then ran BenchVue, and I could not "show" the 34401A.
5. At this point I ran a terminal program on my PC and tried to connect directly to the 34401A myself, and since the Connection Expert was already connected to the serial port I think there was some conflict, and the terminal program stopped responding.
6. I walked away from my PC at this point, and when I returned it was restarting (I'm not sure why).
7. Once it restarted, I could not run BenchVue as I got an error message after the splash screen that the license server could not be contacted or something, and I should wait a few seconds or reboot.
8. I did both, waited, then rebooted. Still to no avail. I could not get BenchVue to run.
9. I then uninstalled and reinstalled BenchVue.
10. It still would not run (even after a reboot).
11. I then ran Control Panel -> Programs and Features, and noticed the application "Keysight License Service". This is probably the issue, but I right clicked and hit repair on this application.
12. BenchVue then ran ok, and I could now see the instrument for the first time, but I was also informed that my trial period had expired.
13. I started using the instrument to log some voltages (for about 50minutes or so, over a couple of start stop sessions). At this point I walked away from my PC for a bit to do some hardware stuff, and noticed the screen had gone blank (I thought it was just the screen saver), but then the PC rebooted. I'm not sure what caused that unexpected reset, but I don't usually have unexpected resets, and this was the second one since installing the Keysight applications.
14. After the reboot, I could no longer see in the instrument in BenchVue, and the rest is history.

I hope this helps somewhat.

Thanks for you quick responses.

Justin.

嗨布莱恩，请帮助！
我回来用BenchVue和Keysight Connection Expert再次撕掉我的头发。
我确实已经运行了几次，如前所述连接到我的34401A，但在数据捕获过程中，我在Win7 x64上获得了可怕的蓝屏死机。
自从我上次运行BenchVue以来，我没有蓝屏。
问题是，一旦我得到蓝屏，BenchVue就不再识别34401A了。
DMM仍在Connection Expert中可见。
我试过更换AppTabDB目录，但无济于事。
如果我在Connection Expert中删除了34401A连接，我只能通过选择“自动识别本仪器”和“测试此VISA地址”，然后选择“接受”来重新添加它。
然后当我在仪器选项卡下点击重新扫描时，34401A出现了。
这是添加仪器的正确方法吗？
BenchVue将34401A显示为隐藏或不支持的仪器。
我已经附加了BenchVue的日志报告文件。



     以下为原文

  Hi Brian,

PLEASE HELP!

I am back to tearing my hair out again with BenchVue and the Keysight Connection Expert.

I did have it up an running a couple of times today connected as described previously to my 34401A, but during the data capture process I got the dreaded blue screen of death on Win7 x64. I haven't had a blue-screen since I last ran BenchVue. The problem is, once I get a blue-screen, BenchVue no longer recognises the 34401A. The DMM is still visible in the Connection Expert. I have tried replacing the AppTabDB directory, but to no avail.

If I delete the 34401A connection in the Connection Expert, I can only re-add it by selecting "Auto-Identify This Instrument" and "Test This VISA Address", followed by "Accept". Then when I hit rescan under the instruments tab, the 34401A comes up. Is this the correct way to add the instrument?

BenchVue shows the 34401A as a hidden or unsupported instrument.

I have attached the log report file from BenchVue.

附件

• 20160316_193330894_00a3dc6cf12a4a29acd2d74b5c4fad9c.zip260.0 KB
  

是的，您正确地添加仪器。
如果您必须将其添加为RS-232仪器，请确保您没有在* IDN中删除掉字符？
Connection Expert用于确定它是什么仪器。
使用Interactive IO来试验设备。
如果它作为不支持的乐器出现在BV中，它很可能无法找出死于乱码的乐器。
确保握手协议设置正确，并且您有一根支持握手的电缆。
如果您使用的是GPIB，请确保您没有在82357B（9,11,13,25,27,29）上使用错误的地址，并且如果使用NI IO库，您已在NI MAX中启用了Passport到Tulip
。
Brian PS - 可能是升级PC或O / S的时候了。
BSOD并不好玩！



     以下为原文

  Yes, you are doing it correctly to add the instrument. If you have to add it as an RS-232 instrument, be sure you aren't getting dropped characters in the *IDN? that Connection Expert uses to determine what instrument it is. Use Interactive IO to experiment with the device. If it is showing up in BV as an unsupported instrument, it is likely not able to figure out what instrument it is die to garbled characters. Make sure the handshake protocol is set correctly and that you have a cable that supports handshaking. If you are using GPIB, make sure you aren't using a bad address on an 82357B (9,11,13,25,27,29) and, if using NI IO Libraries, that you have enabled Passport to Tulip in  NI MAX.

Brian

PS - It might be time to upgrade that PC or O/S. BSODs are no fun!

谢谢Brian，我可以确认使用交互式IO没有删除任何字符，但BV仍然无法识别该工具。
我发现只有按照以下步骤才能让BenchVue识别仪器：1。删除AppTabDB目录2.运行BenchVue（然后获取并返回错误消息然后关闭）3。重新启动已删除的AppTabDB目录
（来自上面发布的副本）。
4.重新运行BenchVue。
如果我省略步骤2，那么BenchVue仍然无法识别该仪器。
请注意，每次重新启动Windows 7计算机时都必须执行这些步骤。
连接专家似乎工作正常，只是BenchVue在遵循上述程序之前无法识别仪器。
NB，关于BSOD：作为一项规则，我从来没有遇到过它们 - 如果我正在运行BenchVue，我只会看到它们（并且BSOD消息提到了一些看起来像是Keysight驱动程序的IO驱动程序 - 我会记下它，如果
我再看一遍）。
这显然是BenchVue的一个错误，而不是我正在做的事情！
更新：我已经从BenchVue 3.0更新到3.1。
重置后，它识别了仪器 - 到目前为止一切顺利。
记录时我还有另一个BSOD。
Windows消息指向我的RS232到USB串行适配器的驱动程序。
我现在升级了那个驱动程序，所以希望不再能看到这个问题。
谢谢，Justin。编辑：linners于2016年3月20日下午7:34



     以下为原文

  Thanks Brian,

I can confirm that using interactive IO that no characters are dropped, and yet BV still does not recognise the instrument.

I have found that I can get BenchVue to recognise the instrument only if I follow the following steps:

1. Delete the AppTabDB directory
2. Run BenchVue (and get and error message that I then close)
3. Re-instate the deleted AppTabDB directory (from the copy you have posted above).
4. Re-run BenchVue.

If I omit step 2, then BenchVue will still not recognise the instrument.
Note that I have to follow these steps every time I reboot my Windows 7 machine.

The connection expert seems to work fine, it is just that BenchVue doesn't recognise the instrument until the above procedure is followed.

NB, regarding the BSOD: As a rule I never encounter them - I only ever see them if I am running BenchVue (and the BSOD message mentions something about an IO driver that looks suspiciously like a Keysight driver - I'll jot it down if I see it again).

This is obviously a bug with BenchVue, and not something I am doing!

UPDATE: I have updated from BenchVue 3.0 to 3.1. After a reset, it recognised the instrument - so far so good. I also had another BSOD whilst logging. The Windows message pointed to the driver for my RS232 to USB serial adapter. I have now upgraded that driver, so hopefully will no longer see that issue. 

Thanks,
Justin.

Edited by: linners on Mar 20, 2016 7:34 PM