完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
你好,我发现自己现在有点迷失了。
我正试图用我的Vee应用程序与Eurotherm温度控制器进行通信。 作为协议,我打算通过RS232端口而不是Modbus使用专有的Bisynch以便于使用(至少我希望如此)。 我的Vee版本是9.22。 Agilent Connection Expert为16.1。 我尝试通过直接I / O ASRL设备访问仪器.Bisynch RS232通信要求RS232在这种情况下设置为19.2k波特,7Bit,LSB,奇偶校验=偶数,停止位= 1。 我已经通过Connection专家和LSB在Vee下的高级设备选项中配置了速度,数据宽度等。示例数据请求看起来像(Hex):04 30 30 31 31 50 56 05预期响应看起来像(Hex) ):02 50 56 56 ?? ?? ?? 03 ??如果我通过终端应用程序将请求直接发送到串口,我会收到预期的响应。 响应时间最长为10ms。当我通过直接I / O对象(如文本或二进制)发送请求时,我可以看到通过I / O监视器发送正确的十六进制值。 但无论我尝试什么,我都无法从串口发出任何响应。 我总是超时。 不知怎的,我必须在这里错过一些关键部分。最诚挚的问候,LarsSölter 以上来自于谷歌翻译 以下为原文 Hello, I find my self a bit lost at the moment. I'm trying to communicate from my Vee application with an Eurotherm temperature controller. As protocol I intent to use the propriatary Bisynch via an RS232 port instead of Modbus for the ease of use (at least I hoped so). My Vee Version is 9.22. The Agilent Connection Expert is 16.1. I try to access the Instrument via a Direct I/O ASRL device. The Bisynch RS232 communication requires RS232 to be set in this case to 19.2k Baud, 7Bit, LSB, Parity=Even, Stop Bit=1. I have configured speed, data width and so on via the Connection Expert and LSB in the advanced device options under Vee. An example data request would look like (Hex): 04 30 30 31 31 50 56 05 The expected response would look like (Hex): 02 50 56 56 ?? ?? ?? 03 ?? If I send the request directly to the serial port via a terminal application I receive the expected response. Response time is max 10ms. When I send the request via a Direct I/O Object (as Text or Binary) I can see the correct Hex values being send via the I/O Monitor. But I can catch no response from the serial port regardless of what I try. I always get a timeout. Somehow I must be missing some crucial part here. With best regards, Lars Sölter |
|
相关推荐
3个回答
|
|
也许你得到一个响应...放入一个接口事件,等待...如果它触发,theres字节就绪,你可以一次一个,然后看看它们用于EOL。
如果事件没有触发,也许你没有发送正确的EOL? ......再一次,也许我完全不正确地阅读了这个问题...... 以上来自于谷歌翻译 以下为原文 Maybe you are getting a response ... put in an interface event, with wait... if it triggers, theres bytes ready, you can take them in one at a time, and see what they use for EOL. If the event doesnt trigger, maybe you are not sending the right EOL ? ... And again, maybe I completely read the problem incorrectly... |
|
|
|
嗨拉尔斯 - 这些问题可能很难找到,因为你现在无疑已经得出结论!
令我印象深刻的是Eurotherm尽可能地让它变得如此困难:选择随机的非标准通信协议(BTW,根据我的经验,Windows无论如何都忽略了奇偶校验),使用简洁的命令代码,包括以EOT字符开头。 ..我同意维基百科的回应。 另一种方法是使用READ BINARY x BYTE事务,它应该读取[任何东西的第一个字节]。 同样如前所述,如果没有任何回复,那么您发送的命令一定存在问题。 我知道你说你在I / O监视器中检查了它...你在05十六进制字符后检查了什么吗? 可能是以下CR / LF角色可能会扰乱Eurotherm。 或者它可能需要一个:当你通过超级终端控制它时,你是否必须按Enter键才能让它响应? 以上来自于谷歌翻译 以下为原文 Hi Lars - these issues can be tricky to track down, as you will no doubt have concluded by now! I'm impressed Eurotherm have gone to such lengths to make it as difficult as possible: choose a random, non-standard comms protocol ( BTW, in my experience Windows ignores parity anyway ), use terse command codes including starting with the EOT character... I would agree with wikily's response. An alternative is to use a READ BINARY x BYTE transaction which should read [the first byte of] anything. Also as was stated, if nothing comes back then there must be a problem with the command you're sending. I know you said you checked it in the I/O monitor... did you check for anything after the 05 hex char? It may be that a following CR/LF character might upset the Eurotherm. Or maybe it needs one: when you are controlling it via hyperterminal, do you have to press the Enter key to get it to respond? |
|
|
|
谢谢你们的答案!
我终于找到了问题的根源。 我得知手册有点错误,并没有在直接I / O对象的高级部分配置串行设置,因为我不知何故确信在不使用8.5 I / O模式时需要在Connection Expert中配置。 所以我发送数据为8Bit块,而不是7.所以我没有回答设备.Rears,Lars 以上来自于谷歌翻译 以下为原文 Thank you both for the answers! I finally got to the source of my problem. I got the manual somehow wrong and did not configure the serial setting in the advanced section of the direct I/O object, as I somehow got convinced that this needs to be configured within the Connection Expert when not using the 8.5 I/O mode. So I was sending the data as 8Bit chunks and not 7. So i gut no answer from the device. Regards, Lars |
|
|
|
只有小组成员才能发言,加入小组>>
1291 浏览 0 评论
2375 浏览 1 评论
2194 浏览 1 评论
2065 浏览 5 评论
2952 浏览 3 评论
1119浏览 1评论
关于Keysight x1149 Boundary Scan Analyzer
756浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
931浏览 0评论
1293浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-25 20:45 , Processed in 1.618413 second(s), Total 82, Slave 66 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号