Skip to main content
InSource Solutions

TN DAS169 RSLinx OPC Server to FS Gateway Licensing Limitations

  1. Last updated
  2. Save as PDF

InSource_Logo_Transparent.png

Description

This article from InSource Solutions describes the licensing limitations related to the RSLinx OPC Server connection to FS Gateway.

  • Author: Daniel London
  • Published: 11/02/2017
  • Applies to: RSLinx / FS Gateway

Details

The information listed below shows the specific limitations for different versions of RSLinx. The source of this info is from Wonderware's resource site....

RSLinx Licensing information (Check the RSLinx title bar to see what it displays. Make sure that you have the RSLinx activation file that enables you to have at least OEM version):
 
  • RSLinx Lite - no OPC capability

 

  • RSLinx Single Node - limited to one local OPC client connection to one device, using an in-process connection type. Other local or remote OPC clients will not be able to connect.

 

  • RSLinx OEM – limited to one local OPC client connection to many devices, using an in-process connection type. Other local or remote OPC clients will not be able to connect.

 

  • RSLinx Professional - limited to one local OPC client connection to many devices, using an in-process connection type. Other local or remote OPC clients will not be able to connect.

 

  • RSLinx Gateway – multiple local or remote OPC client connection permitted to many devices, using out-of-process connection types.

 

To make an in-process (in-proc) connection, deselect the "Connect to OPC Server Out-of-Proc" in OI Gateway, FSGateway, or OPCClient object, and stop the RSLinx service and shut it down. Then make sure RSlinx is a manual service. For the in-proc connection, the OPC client has to start the OPC server.

 

 

Additionally, in general, communication to RSLinx is less likely to have DCOM security issues if it is set to run as a Windows Service.