Download Procidia i|Ware PC - Introduction - Service, Support

In the traditional case, servers or devices have different interfaces / drivers for each client
application. Each arrow line above represents different driver or interface software.
Although the protocol of a device or a server may not change, the architecture of different
client applications (from different vendors) is different. This leads to increased work,
costs and time. If the device or server’s protocol is changed or updated, then the client
application also needs to change.
Fig. 1.2. OPC based Client-Server Architecture
OPC Architecture was introduced by the OPC Foundation mainly to overcome the above
issue. In this case, a device/ server will have only one standard driver which is an OPC
Compliant Server and all the client packages can be connected to it as the clients
themselves are OPC Compliant Clients.
i|Ware PC Basic Edition
i|Ware PC™ is a family of 32 bit OPC Client and Server Applications for Windows. All
applications are multi-threaded and feature ActiveX™ and Visual Basic for
Applications™ (VBA) technology. The i|Ware PC Basic Edition is a HMI Client that is
fully autoconfiguring. The OPC Server auto builds a complete OPC database of a
configured controller. The i|Ware PC™ HMI client, when connected to this OPC
database, automatically builds faceplates and detail screens that enables full operation of
the controller from the HMI client. In additional, graphic screens, that further enhance the
operation of the process, can be easily added and linked to the OPC database. Controller
and Analog detail screens include a Trend Viewer that queries ATD (Analog Trend
Display) blocks in the controller and provides short term historical trending when directly
connected to the Modbus/Ethernet port of the controller. The Trend Viewer is then
updated with new values using persistent trending. When using the LIL OPC Server
persistent trending is used to populate the trend graph on the controller detail screen.