OPC server added to data acquisition and control system
Dataforth’s introduction of an OPC Server for the MAQ20 Industrial Data Acquisition & Control System ensures data collection and analysis using the MAQ20 is now significantly broader-based and easier to use.
"Our MAQ20 OPC Server provides a common interface to the MAQ20 system that is usable by any SCADA, HMI, or other custom software that is an OPC client," says Engineering Manager John Lehman. "This eliminates the need for a custom interface or driver when using the MAQ20 with industry standard software, and it enables real-time information exchange on local hosts or over distributed networks." The MAQ20 OPC server uses Kepware Technologies’ KEPServerEX OPC Server and Modbus TCP driver, which have been configured for the MAQ20 system.
OPC servers consist of three basic parts: channels, devices, and tags.
A channel represents the communication medium from the host computer to one or more devices. For example, the MAQ20-COM4 communications module has an RS-485 port and an Ethernet port; a serial or Ethernet connection between the host computer and the MAQ20 would be a channel in an OPC server.
A device is the hardware with which the server communicates. The device driver provides the interface to the data acquisition hardware. For the MAQ20 OPC server, the MAQ20 Data Acquisition System is the device.
A tag represents addresses within the hardware with which the server communicates. The KEPServerEX OPC Server allows both dynamic tags and user-defined static tags. Dynamic tags are entered in the OPC client and specify device data. User-defined static tags are created in the server and support tag scaling. When the MAQ20 system is used as the device, tags are assigned to the addresses within the MAQ20 I/O modules and communications modules from which data is read and to which data is written.
www.controleng.com/products has additional products. Also see the product section in the April print/digital edition of Control Engineering.
Interested in introducing a product to the world here? Contact Mark T. Hoske, firstname.lastname@example.org