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

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 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.