Blood...Stone...
JohnCalderwood said:
...What type/name/brand of SCADA are you using...?
rejoe.koshy said:
Its a PC based SCADA developed by the manufacturer
Okay...it's a SCADA...it's running on a PC...and it's been developed by a manufacturer...
Nope...nothings coming up in my Crystal Ball?...it must be on the blink today?
I'm sorry if I sound rude here but that has to be one of the most vague and unhelpful (ultimately to you) replies to a direct question I've seen for some time here.
There are, and as has been pointed out, many ways to communicate with AB controllers without using RSLinx Classic, from many different SCADA packages.
But if you, and you alone, in this thread, are the only one that knows the SCADA package in question, then you will remain alone in trying to figure out how it is currently communicating with the controller.
Even if you think it is a somewhat obscure and proprietary SCADA package, you would be as well say. You may be surprised to find that someone here might have some prior knowledge of it. Failing that, the resources to help you find some information will undoubtedly increase.
Help us to help you.
rejoe.koshy said:
...Are you talking about a software interface or a hardware one?
A hardware converter would only have been required here to convert different communications protocols and the different plugs/jacks they use. It was thought you had an SLC 5/03 which would be possibly using the DH-485 or DF1 protocol, and so would have required some type of converter.
As we now know, at least, that it is an Ethernet based SLC 5/05, then presumably, both are connected to an Ethernet network, and so no hardware converter should be required.
Only a software driver should be required in the SCADA package to successfully communicate with the SLC 5/05. Because the addressing structure for RSLogix 500 based controllers is unique, they must have developed a specific AB driver for their SCADA package or else they are using some third party software as a go between.
Regards,
George