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


Connecting to an RSLinx OEM on a Remote PC


Last Update: 11/7/2018

Problem:
LinkMaster is on Machine A and the RSLinx OEM is on Machine B, but the two cannot communicate.

Possible Cause:
The RSLinx OEM only supports local OPC connectivity.

Solution:
Place LinkMaster on the same machine as the RSLinx OEM. At that point, users will be able to serve data to other OPC clients or bridge data to other OPC servers.

Note:
This also applies to KEPServerEX and its OPC DA Client Driver when attempting to connect the OPC DA Client Driver to an RSLinx OEM.

Related Products
KEPServerEX, LinkMaster, OPC DA Client

Related Protocols
OPC Data Access (DA)