使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Communication Diagnostics for a Channel Using a Modbus Driver Shows TX But No RX


Last Update: 2018/11/7

Problem:
When using Kepware's Modbus drivers, the Communication Diagnostics show TX (transmit) but no RX (receive).

Solution:
1. If using an Ethernet-to-serial converter, verify that it is set for Modbus/TCP-to-Modbus-RTU conversion. If it is, use the Modbus Ethernet Driver. Certain devices that are not supported by the Ethernet driver can use Modbus Serial Driver instead with "Use Modbus TCP framing" option enabled.

2. The device may not respond when a Modbus RTU request is sent to a Modbus ASCII device (or vice versa). Users that want to transfer ASCII strings do not have to use the Modbus ASCII Driver: strings can be transferred over Modbus RTU. To verify the type of serial Modbus is supported, refer to the device's documentation.

3. When sending a Modbus RTU or Modbus ASCII request to unit address 0, the device is not supposed to respond; however, native Modbus/TCP devices will normally respond to requests sent to unit address 0.

Note:
Most suggestions that apply to the Modbus RTU protocol (used by the Modbus Serial Driver) also apply to the Modbus Ethernet Driver when connected to a Modbus/TCP-to-Modbus-RTU Ethernet-to-serial gateway. This is because the device on the serial side of the gateway receives the requests in Modbus RTU form.

Related Protocols
Modbus Ethernet