是德科技
直播中

刘阳

7年用户 165经验值
私信 关注
[问答]

E363xA Labview编程有很多VI_ERROR_TMO

Hi Everyone当前设置:labview 2013 Agilent 82357B USB到GPIB Agilent IO套件16.3 - Agilent VISA设置为主要Agilent E3633A我有一个问题,希望有人可以帮助我。
有时当我从Labview运行Agilent E363X系列 Public  Initialize.vi驱动程序时,vi运行正常,但是当我使用Agilent IO Monitor监控IO时,我发现有很多VI_ERROR_TMO,实际上在VI之后
完成执行后,这些继续流。
这是因为VISA会话被打开并且它不断尝试通信吗?
这是正常的吗?
有趣的是,当我使用Agilent Interactive IO并逐个发送命令时,没有问题。
现在这是一个陌生的事情。
当我使用VI作为一个独立的VI时,它确实有效(虽然仍有上述错误)但是当我把这个VI放到一个更大的程序中时,有时这个VI挂在Initialize.VI中的WRITE / READ可以任何人帮忙或者
提供一些见解????

以上来自于谷歌翻译


     以下为原文

  Hi Everyone
Current setup:
LABView 2013
Agilent 82357B USB to GPIB  
Agilent IO suite 16.3 - Agilent VISA set to primary
Agilent E3633A

I have an issue that hopefully someone can help me with.
Sometimes when I run the Agilent E363X SeriesPublicInitialize.vi driver from Labview, the vi functions fine, but when I monitor the IO using the Agilent IO Monitor, I see that there are a lot of VI_ERROR_TMOs and in fact after the VI completes execution, these continue to stream after.  
Is this because the VISA session is opened and it continually tries to communicate?  
Is this normal? The interesting thing is that when I use the Agilent Interactive IO and send the commands one by one, there is no issue.

Now here is a stranger thing. When I use the VI as a standalone VI, it does work( although still with the errors above) but when I place this VI into a larger program, sometimes this VI hangs at the WRITE/READ within the Initialize.VI

Can anyone help or provide some insight????  

回帖(1)

罗敏

2019-1-24 06:44:04
你在哪里下载驱动程序?
如果您没有从安捷伦网站下载驱动程序,我们无法提供太多帮助,因为我们无法控制该驱动程序。
您是否尝试使用VISA读写VI在Labview中直接进行IO?
请考虑使用此代替驱动程序。

以上来自于谷歌翻译


     以下为原文

  Where did you download the driver?  If you did not download the driver from the Agilent website, we cannot really help much since we do not control that driver.

Have you tried direct IO in Labview using the VISA read and write VIs?  Please consider using this instead of the driver.
举报

更多回帖

发帖
×
20
完善资料,
赚取积分