![]() So, there wasn’t a huge push from the hardware vendors to play nicely. Most companies didn’t support OPC directly on their hardware because they already had their own protocols and “open” is kind of a “four letter word” in manufacturing. Technically, MQTT was also around, but wasn’t very well known until recently. ![]() ![]() OPC was introduced alongside Modbus, Profibus, Ethernet/IP, Profinet, FINS, and a handful of other protocols supported by various vendors. OPC was built on top of the DCOM protocol in Windows and designed to be a standard communication protocol you could use with SCADA systems and other software platforms to send process data where it needed to go. Without going into a full history lesson, before OPC-UA, there was only standard OPC (now known as OPC-DA). Otherwise, it was fairly ubiquitous in the industry. ![]() If your SCADA platform of choice supported Modbus Communication or it was made by the same manufacturer as your PLCs (like using FactoryTalk View and Allen Bradley PLCs) you could get rid of the Kepware piece. Before Ignition came on the market-and before OPC-UA was a mainstay-a very common SCADA architecture looked like “SCADA Platform of your choice Kepware PLCs”
0 Comments
Leave a Reply. |