Dataforth broadens MAQ20 usability with OPC server

April 15, 2015

Dataforth’s introduction of an OPC Server for the MAQ20 industrial data acquisition and control system ensures data collection and analysis using the MAQ20 is now significantly broader-based and easier to use. The original acronym OPC stood for OLE for Process Control, or Object Linking and Embedding for Process Control. The OPC Foundation has officially renamed it to mean Open Platform Communications; it is also referred to as Open Productivity and Connectivity.

“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,” said 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

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.

About the Author

Rick Nelson | Contributing Editor

Rick is currently Contributing Technical Editor. He was Executive Editor for EE in 2011-2018. Previously he served on several publications, including EDN and Vision Systems Design, and has received awards for signed editorials from the American Society of Business Publication Editors. He began as a design engineer at General Electric and Litton Industries and earned a BSEE degree from Penn State.

Sponsored Recommendations


To join the conversation, and become an exclusive member of Electronic Design, create an account today!