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

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

各種検索方法:
View All Solutions

Kepware Knowledge Base: Solution


Server Stops Communicating with Serial Device via Third-Party Serial Port Card


Last Update: 2018/11/12

Problem:
On a windows operating system, serial communications are managed via a communication library file, which can support the on-board serial ports or serial cards for most PC manufacturers. A number of the third-party manufacturers of after-market serial cards provide their own communication library file for managing communications via the serial card. Since the manufacturer is replacing the library file provided by Microsoft, it should support all of the calls and parameters that the original file contained. If it does not, there can be a loss of communications or a complete failure to initialize communications. This issue can also apply to virtual communications port software that is used with Serial-to-Ethernet converters.

Solution:
1. Verify that the issue is the communication library by establishing a serial connection on a PC that is using the default Microsoft communication library.
2. If using a Serial-to-Ethernet converter, try using Ethernet Encapsulation mode in the server to avoid the communications library.
3. Check with the manufacturer to make sure the latest firmware is running in it.