发 帖  
原厂入驻New
申请华秋企业认证 多层板首单免费打样!
30s提交资料,10分钟通过审核(免费赔付+顺丰包邮)>>立即报名
[问答] Agilent VEE不会与设备通信
164 VEE Modbus
分享
您好,我在Agilent VEE上遇到modbus通讯问题。
我尝试使用一种名为mbus的软件与设备进行通信,它可以进行通信。
连接是正确的。
但是当我在VEE上写一个交易时,它不会与设备通信(我选择了ASRL)。
错误消息:“VEE运行时错误I / O错误或VISA设备上发生超时:”新文件“.VISA错误:VEE_ERROR_TMO错误号:811In事务号2对象标题:newinstrument(@ASRL4 :: INSTR)对象类型:直接I /
O“我应该安装dll还是那样的东西?

以上来自于谷歌翻译


     以下为原文

  Hello,

I have a problem with modbus communication on Agilent VEE. I tried to a software which is calLED mbus for communication to device, it can commmunicate. The connections are correct. But when i write a transaction on VEE, it won't communicate the device (i chose ASRL). The error message:

"VEE Run Time Error
I/O error or timeout occured on VISA device: "new enstrument". VISA Error: VEE_ERROR_TMO
Error number: 811
In transaction number 2
Object title: newinstrument (@ASRL4::INSTR)
Object type: Direct I/O
"

Should i install dll or something like that?  
0
2019-8-5 09:12:32   评论 分享淘帖 邀请回答

相关问题

12个回答
嗨mistipliler,如果端口设置不正确,通常会发生ASRL的IO超时错误。
在Instrument Manager中,右键单击仪器,然后单击Advanced ...按钮。
验证通用,串行和直接I / O中的设置是否适合您的设备。希望这有帮助,-mk

以上来自于谷歌翻译


     以下为原文

  Hi mistipliler,

The IO timeout error for ASRL usually happen if the port settings are incorrect. In Instrument Manager, right click on the instrument then click on Advanced... button. Verify the settings in General, Serial and Direct I/O are correct for your device.

Hope this helps,
-mk
2019-8-5 09:18:33 评论

举报

lc123617 发表于 2019-8-5 09:18
嗨mistipliler,如果端口设置不正确,通常会发生ASRL的IO超时错误。
在Instrument Manager中,右键单击仪器,然后单击Advanced ...按钮。
验证通用,串行和直接I / O中的设置是否适合您的设备。希望这有帮助,-mk

亲爱的先生,我有同样的问题,但是无法解决它虽然我试图通过Agilent I / O控制中的工具I / O连接仪器请帮助我,以下是错误“VEE运行时错误I / O错误或超时发生
在VISA设备上:“新仪器”.VISA错误:VI_ERROR_TMO错误号码:811在事务编号7中对象标题:newinstrument(@ agu2723a @ IV study)对象类型:直接I / O“问候minisha

以上来自于谷歌翻译


     以下为原文

  Dear Sir,

I have same problem, but could not solve it although i tried to connect the instrument via intractive I/O in Agilent I/O control
please help me, following is error

"VEE Run Time Error
I/O error or timeout occured on VISA device: "new instrument". VISA Error: VI_ERROR_TMO
Error number: 811
In transaction number 7
Object title: newinstrument (@agu2723a@IV study)
Object type: Direct I/O"

Regards 
minisha
lc123617 发表于 2019-8-5 09:18
嗨mistipliler,如果端口设置不正确,通常会发生ASRL的IO超时错误。
在Instrument Manager中,右键单击仪器,然后单击Advanced ...按钮。
验证通用,串行和直接I / O中的设置是否适合您的设备。希望这有帮助,-mk

亲爱的先生,我有同样的问题,但是无法解决它虽然我试图通过Agilent I / O控制中的工具I / O连接仪器请帮助我,以下是错误“VEE运行时错误I / O错误或超时发生
在VISA设备上:“新仪器”.VISA错误:VI_ERROR_TMO错误号码:811在事务编号7中对象标题:newinstrument(@ agu2723a @ IV study)对象类型:直接I / O“问候minisha

以上来自于谷歌翻译


     以下为原文

  Dear Sir,

I have same problem, but could not solve it although i tried to connect the instrument via intractive I/O in Agilent I/O control
please help me, following is error

"VEE Run Time Error
I/O error or timeout occured on VISA device: "new instrument". VISA Error: VI_ERROR_TMO
Error number: 811
In transaction number 7
Object title: newinstrument (@agu2723a@IV study)
Object type: Direct I/O"

Regards
minisha
通常有很多原因:A。超时持续时间不足。
也许仪器需要更长的时间来处理数据。
B.首先插入Read事务而不编写查询命令。
您可以先尝试延长超时时间。
如果这不起作用,建议您是否可以更容易:*附加VEE程序部分*:1。附上VEE程序部分的图像。
确保Direct IO对象足够大以查看发送的完整命令。
2.附加VEE程序的一部分,使用直接IO对象给出错误。
对于1或2,请包括该直接IO对象中的所有事务以确定它是否属于方案B. *附加IO监视文件*:1。要收集文件,请转到IO系统托盘图标(靠近日期/时间)
在Windows桌面的右下角),右键单击IO,然后选择Utilities> IO Monitor。
2.转到选项,确保为监视器和显示消息选择了Agilent VISA。
3.单击开始捕获消息。
运行VEE程序,直到引发超时错误。
4.单击“停止捕获邮件”。
将消息保存到文件中并将其附加到此处。
希望这可以帮助。
-mk编辑:changmeikuan于2013年8月22日上午10:39

以上来自于谷歌翻译


     以下为原文

  In general there are many causes:
A. Insufficient timeout duration. Maybe the instrument need longer time to process the data.
B. Insert a Read transaction without writing a query command first.

You can try prolong the timeout duration first. If that doesn't work, it will be easier to advise if you can either:
*Attach the portion of the VEE program*:
1. Attach either the image of the portion of the VEE program. Make sure the Direct IO object is big enough to see the full command sent. 
2. Attach the portion of the VEE program, with the Direct IO object giving the error is included. 
For 1 or 2, do include all transactions in that direct IO object to identify if it falls under scenario B.

*Attach the IO Monitor file*: 
1. To collect the file, go to IO system tray icon (near the Date/Time on the bottom right corner of windows desktop), right click on IO, then select Utilities > IO Monitor.
2. Go to Options, make sure Agilent VISA is selected for both Monitor and Display Messages.
3. Click on Start capturing messages. Run the VEE program until the timeout error is thrown.
4. Click on Stop capturing messages. Save the Messages into a file and attach it here.

Hope this helps.
-mk

Edited by: changmeikuan on Aug 22, 2013 10:39 AM
2019-8-5 09:44:20 评论

举报

感谢您的留言,但我无法获得如何继续第一步,第二步(IO监视器)我尝试但仍然保持相同的错误:附加VEE程序的部分:1。附上VEE部分的图像
程序。
确保Direct IO对象足够大以查看发送的完整命令。
2.附加VEE程序的一部分,使用直接IO对象给出错误。
对于1或2,确实包括该直接IO对象中的所有事务以识别它是否属于方案B.我的意思是如何附加VEE程序

以上来自于谷歌翻译


     以下为原文

  Thanks for message but I could not get how to proceed with first step, seccond step ( IO monitor) i tried but it remain the same error:
Attach the portion of the VEE program:
1. Attach either the image of the portion of the VEE program. Make sure the Direct IO object is big enough to see the full command sent. 
2. Attach the portion of the VEE program, with the Direct IO object giving the error is included. 
For 1 or 2, do include all transactions in that direct IO object to identify if it falls under scenario B.

I mean how to attach VEE program
冷冷萧魂丶芮 发表于 2019-8-5 09:55
感谢您的留言,但我无法获得如何继续第一步,第二步(IO监视器)我尝试但仍然保持相同的错误:附加VEE程序的部分:1。附上VEE部分的图像
程序。
确保Direct IO对象足够大以查看发送的完整命令。

>第二步(IO监视器)我试过但它仍然是相同的错误:运行IO监视器并不意味着解决问题。
如果您可以按照附加IO监视器文件中的步骤1-4,在此处共享IO监视文件(.xml),那么我可以通过查看IO监视器文件来帮助诊断问题。
>我的意思是如何附加VEE程序当你回复一个帖子时,在你输入信息的方框之后,有一个附加文件选项,只需点击选择文件并上传文件。
-MK

以上来自于谷歌翻译


     以下为原文

  >second step ( IO monitor) i tried but it remain the same error:
Running IO Monitor isn't meant to solve the issue. If you can follow the steps 1-4 in Attach the IO Monitor file, share the IO monitor file (.xml) here, then I can help diagnose the issue by looking at the IO Monitor file.

>I mean how to attach VEE program
When you reply to a thread, after the box you type message, there is a Attach Files options, just click on Choose File and upload the file.

-mk
2019-8-5 10:03:30 评论

举报

嗨,chamemeikuan感谢您的帮助。我添加了我的屏幕视图,也许您可​​以在这些配置中发现错误。
我是这个职位的新手。任何帮助都会受到赞赏。最诚挚的问候

以上来自于谷歌翻译


     以下为原文

  Hi, changmeikuan

Thanks for your help.

I add my screen views, maybe you can find a mistake in these configurations. I'm rookie on this job.











Any helps would be appreciated.

Best regards
2019-8-5 10:14:56 评论

举报

嗨mistipliler,我很遗憾地说我无法判断设置是否正确,因为每个设备都有不同的设置,例如
设备波特率,奇偶校验等。当我查看其他用户的帖子时,通常错误来自串口设置,读终结器和EOL序列。
我建议查看设备手册/规范以验证设备设置。
这些必须与您的设备设置相匹配才能与设备通信。顺便说一句,您是否在WRITE BYTE之后收到超时错误?
每当遇到IO错误时,我都会使用IO监视器来帮助查找更多详细信息。
不知道这对你的情况是否有帮助,因为我很少使用ASRL。希望这有帮助,-mk

以上来自于谷歌翻译


     以下为原文

  Hi mistipliler,

I am sorry to say I cannot tell if the settings are correct or not because every device has different settings, e.g. device baud rate, parity and etc. When I look into other user's post, usually the error come from Serial setting, Read Terminator and EOL Sequence. I recommend to look into the device manual/specification to verify the device settings. Those must match your device setting in order to be able to talk to the device.

By the way, are you getting an timeout error after WRITE BYTE a?

Whenever I encounter IO error, I will use IO monitor to help to find out more details. Not sure if this will be helpful in your case as I rarely use ASRL.

Hope this helps,
-mk
2019-8-5 10:24:16 评论

举报

嗨再次,我解决了这个问题。
我在codeThanks和最好的问候中犯了一些错误

以上来自于谷歌翻译


     以下为原文

  Hi again,

I solved this problem. I did some mistakes in the codes



Thanks and best regards
2019-8-5 10:34:37 评论

举报

大!

以上来自于谷歌翻译


     以下为原文

  Great!
2019-8-5 10:41:36 评论

举报

如果有人仍然感兴趣我已经成功使用来自http://code.google.com/p/free-dotnet-modbus/的第三方.NET DLL我必须重建它到.NET 3.5,因为它目前在
4.0级 - 如果需要,我可以在这里发布dll。
具有WriteSingleCoil,ReadHoldingRegisters等的典型MODBus操作.Mike Watts

以上来自于谷歌翻译


     以下为原文

  If anyone is still interested I have had success using a 3rd-party .NET DLL from
http://code.google.com/p/free-dotnet-modbus/

I had to rebuild it to .NET 3.5 as it is currently at 4.0 level - I could post the dll here if requested.

Has typical MODBus operations of WriteSingleCoil, ReadHoldingRegisters etc.

Mike Watts
2019-8-5 10:57:23 评论

举报

迈克,我是Vee Pro的新手,但我需要与Vee Pro进行Modbus RTU从站的通信。
这个.NET DLL编译是如何完成的?
你如何在Vee Pro中集成它?

以上来自于谷歌翻译


     以下为原文

  Mike, i am kind of new in Vee Pro, but i have the need to have a communication to a Modbus RTU slave with Vee Pro. How was this .NET DLL compilation done? how do you integrate it within Vee Pro?
2019-8-5 11:15:22 评论

举报

只有小组成员才能发言,加入小组>>

68个成员聚集在这个小组

加入小组

创建小组步骤

关闭

站长推荐 上一条 /10 下一条

快速回复 返回顶部 返回列表