OPC Server to OPC Server Bridging
The most common scenario for LinkMaster is to link data between two (or more) OPC Servers. An example might be a customer using RSLinx for connectivity to Allen Bradley PLCs and Kepware's U-CON Protocol Server for connectivity to a checkweigher. In this example the customer wants to easily send scale data to the PLC. |
|
OPC Server within Server bridging
This scenario is commonly used when a customer wants to route data between two PLCs connected to the same server. Using LinkMaster to define the tag data routing can be much easier than creating new ladder logic in your PLCs (especially for legacy systems). An example might be a customer using KEPServerEX to connect to an Allen Bradley ControlLogix PLC as well as a Yokogawa DX Data Recorder. |
|
OPC Server Collector or Gateway
Another interesting application scenario for LinkMaster is to function as a single OPC server which serves data from multiple OPC servers. This approach demonstrates LinkMaster's capability of acting as both a client and server. An example might be when a customer has a single OPC connection available from an OPC client application but multiple OPC servers that they want to acquire data from. |
|
OPC link between PLC and DCS
A powerful but simple link scenario for LinkMaster is to use it to share data between a PLC and a DCS. In this example, both device systems have an OPC server connected to them to make data available to OPC client applications but they do not have an easy way to share data with other servers. An example might be that a paper mill needs to send gauging system data to a PLC. Honeywell's Davinci server would communicate with the Measurex gauging system in the DCS. LinkMaster would pass data from the Davinci Server to Kepware's OPC server KEPServerEX and KEPServerEX would send the data to the Siemens S7 PLC. |
|
