Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

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

Last Update: 11/12/2018

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.

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.