.vxe无法识别与其他GPIB-USB转换器的连接

错误消息的屏幕截图将非常有用。
此外，IO Monitor中的跟踪也很有用（如果您使用的是Agilent IO Lib。如果您使用的是NI VISA，它将是NI I / O跟踪）。
哪个IO Lib版本？
-MK



     以下为原文

  Screenshot on the error message will be useful. Besides, traces in IO Monitor will be useful too (if you are using Agilent IO Lib. It will be NI I/O Trace if you are using NI VISA).
Which IO Lib version?

-mk

对不起，我花了很长时间才回来。
我之前应该提供更多信息。
我使用的是HP3458A，它们已经足够大，没有IDN标识符。
当我查看Agilent或NI连接向导时，我可以看到仪表。
我无法弄清楚为什么Vee看不到它。
我正在运行图书馆16. DH
错误屏幕截图.pdf9.3 KB



     以下为原文

  Sorry I took so long to get back. I should have given more info before. I am using HP3458A's and they are old enough that they don't have an IDN identifier. When I look in Agilent or NI connection wizard I can see the meters. I can't figure out why the Vee can't see it. I am running Libraries 16.
DH

附件

• Agilent IO.pdf46.8 KB
  
• error screen shot.pdf9.3 KB
  

要迁移，sourceId：103409



     以下为原文

  to be migrated, sourceId: 103409

我想我可能已经找到了我的问题，但我无法超越它。
我尝试了附加PDF中的所有步骤（几次）我甚至尝试以安全模式启动而没有运气。
谢谢你抽出宝贵的时间。
DH



     以下为原文

  I think I might have found my problem, but I can't get past it. I tried all the steps in the attached PDF (several times)
I even tried to start in safe mode with no luck. Thanks for taking your time.
DH

附件

• agilent 488 problem.pdf186.0 KB
  

对不起，以下是您要求的结果。
谢谢。
DH



     以下为原文

  Sorry, here are the results that you asked for. Thanks.
DH

附件

• IO Monitor results 8-24-12.pdf83.2 KB
  

再次查看您的Agilent IO.pdf，我很抱歉，我认为我错过了一些重要的事情。
从Agilent IO.pdf中可以看出，当您使用82357A和82357B时，它们都具有不同的接口编号，即GPIB0 :: 22 :: INSTR和GPIB1 :: 22 :: INSTR。
我猜+ 82357A是GPIB0 :: 22 :: INSTR +而+ 82357B是GPIB1 :: 22 :: INSTR +。
如果我的猜测是正确的，那么解决起来要容易得多。
首先把488.2的东西放在一边。
我不确定你的程序如何查找设备。
我希望它不是硬编码到任何GPIB接口号GPIB0或GPIB1。
但是在附加的IO Monitor结果中，它正在尝试与gpib0通信，而82357B正在使用GPIB1。
我建议尝试以下方法：（A）转到程序> Agilent VEE Pro Runtime 6.0配置> IO配置，将设备地址更改为82357B正在使用的地址，即GPIB1 :: 22 :: INSTR。
然后再次运行.vxe，看它是否有效。
如果它不起作用，可能是接口号在程序内部硬编码。
无论如何，在IO配置中将地址重置为GPIB0 :: 22 :: INSTR。
然后尝试（B）。
（B）在Agilent Connection Expert（Agilent IO.pdf中的ACE软件）中，右键单击GPIB0并删除整个界面。
也删除整个GPIB1接口。
将82357B与仪器连接到PC。
现在，82357B的默认地址应为GPIB0，使用82357B时，设备地址应为GPIB0 :: 22 :: INSTR。
再次运行.vxe以查看它是否有效。
请分享结果然后我们可以看到下一步如何继续:)希望这有帮助，-mk编辑：changmeikuan于2012年8月27日下午2:16



     以下为原文

  Looking at your Agilent IO.pdf again, I am sorry that I think I have missed out something important. From Agilent IO.pdf, it seems like when you use 82357A and 82357B, both of them have different interface number i.e. GPIB0::22::INSTR and GPIB1::22::INSTR.  I guess 
+82357A is GPIB0::22::INSTR+ while 
+82357B is GPIB1::22::INSTR+.

If my guesses are correct then it is much easier to solve. Put the 488.2 things aside first. I am not sure in your program how does it look for device. I hope it is not hard coding to any GPIB interface number GPIB0 or GPIB1. However in IO Monitor result you attached, it is trying to communicate with gpib0, while 82357B is using GPIB1. I would recommend to try below: 

(A) Go to Programs > Agilent VEE Pro Runtime 6.0 config > IO Configuration, change the device address to the one that 82357B is using i.e. GPIB1::22::INSTR. Then run the .vxe again see if it works. If it doesn't work, probably the interface number is hard coded inside the program. Anyway, reset the address to GPIB0::22::INSTR in IO Configuration. Then try (B).

(B) In Agilent Connection Expert (the ACE software in Agilent IO.pdf), right click on GPIB0 and delete the whole interface. Delete the whole GPIB1 interface too. Connect 82357B with the instrument to the PC. The default address for 82357B should now be GPIB0 and the device address should be GPIB0::22::INSTR when using 82357B. Run the .vxe again to see if it works.

Please share the outcome then we can see how to proceed next :)

Hope this helps,
-mk

Edited by: changmeikuan on Aug 27, 2012 2:16 PM