- #Rslinx classic lite driver configure how to
- #Rslinx classic lite driver configure install
- #Rslinx classic lite driver configure serial
- #Rslinx classic lite driver configure software
- #Rslinx classic lite driver configure trial
#Rslinx classic lite driver configure software
There is definitely no chance for your old Windows NT-based software to use Inductive Automation’s OPC-UA server. However, lets start with this and see how it goes. Here’s what I have, might be different based on the versions you have installed:ĬLSID: Īssuming you can get connected, your next challenge will be the item addressing. Restart your opc client, and see if kepware shows a connection.Copy the CLSID value from kepware, and set it as the value under RSLinx.Copy the CLSID for RSLinx and save it in a text file, so that you can set it back if necessary.The CLSID is the value under the CLSID key. The name you find, by the way, is the “ProgID”. The CLSIDs can be found by going to HKEY_CLASSES_ROOT, and then finding the OPC server.If you don’t feel comfortable working in Regedit, I don’t recommend you try this. If your client is trying to connect directly through the Clsid, there’s not much you can do. Then, if your client is trying to connect to RSLinx through that name, it will connect to kepware instead. You could in theory remap RSLinx’s ProgId to point to Kepware’s Clsid. Basically, the ProgId to Clsid lookup is in the registry. This is possible due to how OPC Clients normally connect to OPC Servers. NOW… there is one thing that comes to mind that you might be able to do. I’ve never seen an OPC client hard coded for a certain server, but it looks like that might be the case here. But how? You would need to be able to select which server to use, but it doesn’t seem like you can. As the people here have suggested, Kepware is a good one to try. Now, that means you want to try a different OPC-DA server.
#Rslinx classic lite driver configure install
So, first things first, since your client uses OPC-DA, there is nothing you can do with Ignition’s OPC-UA server, unless you were to install some sort of adapter, but let’s not get into that! The client uses TCP to connect to a server, which is waiting for requests. UA: Completely different, more like what you’re used to with “client/server” setups. It then goes through Windows’ COM system to access the application identified by that CLSID. To connect, it uses this progid to look up a different id, the CLSID, in the registry.
You first need to understand how “connections” happen with both.ĭA: The client (usually) has a name, called a “ProgID”. Tech support should also be able to help.įirst, I think we need to clarify a few things: This is one of those “try before you buy” opportunities.
I know RSLinx Lite (Free Rockwell version)won’t work, Gateway and Professional should in any case, OEM would work locally, maybe across the network (I’m not sure) - you get the idea. There are also considerations on the RSLinx side, depending on licensing and if the installation is on the same machine or across the network.
#Rslinx classic lite driver configure trial
You should be able to do a free trial first, but you would need to eventually purchase the OPC-COM module ($300, I think). In your case it might actually make sense since all of the communication to the PLC is going through the same process. Typically, this is the least recommended method since you’re going with the legacy route.
#Rslinx classic lite driver configure how to
But how to do that if HMI software is writed to work only with RsLinx? Something middle software that will be pretend RsLinx, sending signals to Inductive and Inductive to machine? Something like proxy in network?Ĭould someone send me some link with descriptions about difference between OPC-DA and OPC-UA Servers? I’d like to try test this software with other OPC Server. I figured out how to make it working on Windows 7 and XP but is much slower than on NT.
#Rslinx classic lite driver configure serial
Manufacturer is still selling machine and software with Windows NT and not PnP serial card. Probably (I’m trying to test that now) HMI software will not be able to connect with machine by any other OPC Server than RsLinx. This manufacturer is selling their machines with his own HMI software and RsLinx. What are you trying to do, if I may ask? The more details you can provide, the better answer you will likely get. The OPC server supplied by RSLinx is OPC-DA, while Ignition is OPC-UA.