検索機能を使用して 500 を上回る Kepware の知識ベース記事の中から閲覧します。結果を絞り込むか、クエリーを下部の検索フィールドに入力します。

解決策が見つからなかった場合には、当社の PTC eSupport Portal で追加資料を確認することもできます。eSupport Portal へのログインを要求された場合、My Kepware の認証情報を使用できます。My Kepware アカウントが必要ですか? こちらで作成

各種検索方法:
View All Solutions

Kepware Knowledge Base: Solution


Communication Diagnostics for a Channel Using a Serial Driver Shows TX But Not RX


Last Update: 2018/11/07

Problem:
The Communication Diagnostics for a channel using a serial driver shows TX (transmit) but not RX (receive).

Solution:
When this occurs, the problem could be with one or more of the following:

1. The RS485 converter.
2. Cabling.
3. The serial communication parameters (such as baud rate).
4. The Device ID or unit address.
5. An error in the request (such as, invalid memory address or a request for too much data) has caused the device to not respond.
6. The wrong protocol is being used (such as, using the Modbus ASCII Driver to communicate to a Modbus RTU device).
7. The device's communications port is turned off.

Solution:
1. In the Communications tab of Channel Properties, try setting the server's Flow Control parameter to RTS Always.
2. Ensure that the cabling has been properly configured.
3. Ensure that the serial communication parameters have been set correctly.
4. Verify the Device ID or unit address.
5. Resolve any errors that occurred in the request.
6. Ensure that the right protocol is being used.
7. Ensure that the device's communications port is turned on.

Note:
The suggestions described above still apply when Kepware's serial drivers are in Ethernet Encapsulation mode. For more information, refer to Communications Diagnostics.

See Also:
Troubleshooting KEPServerEX

Related Products
KEPServerEX