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.
Obviously you would need to purchase a license from Kepware to remove the 2 hour free trial restriction. If the Kepware trial works connecting Ignition via the Kepware OPC-UA server - go that route.
From your screenshots it looks like the device uses an Ethernet enabled PLC5. You may be able to connect with the built in (free) Ignition OPC-UA server.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. 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.
0 kommentar(er)
