CACService™ (OPC Server for eP Products)

Quick Links to Information Below

• CACService Overview
• Communication Summary for CACService
• Message Logging for CACService
• Other OPC Related Products
• Features of CACService
• CACService Options & Configurations

PDF Documents

• CACService (OPC Server for eP Products)
• CACService (OPC Server for eP Products) - Spanish Version

CACService Overview

OLE for Process Control™ (OPC™) is a software standard designed to provide business applications with easy and common access to instrumentation data. The OPC specification is maintained by the OPC Foundation™, and is a nonproprietary technical specification. Standard interfaces are based upon Microsoft’s® OLE/COM technology and will enable the definition of standard objects and properties for servers of real-time information such as programmable logic controllers (PLCs), remote terminal units (RTUs), and other field devices.

The major benefit of using OPC is the ability for vendors to offer a standard server which will “plug in” to OPC compliant clients, including but not limited to Shell Services International Artificial Lift Application, Intellution®, and Wonderware™.

CACService has been developed to handle the direct interface with instrumentation manufactured by eProduction Solution (eP) using 8500 protocol. CACService is based upon the OPC toolkit from FactorySoft, and features a Windows® interface for configuration of devices and tags. CACService delivers process specific data for rod pump controllers (RPCs) and manages a keypad display for eP’s EXS-1000™ and RPC product lines.

Communication Summary for CACService

Gather and display statistics about the communication history per device. Each transaction is logged for success or failure, along with data about total bytes read/written, retry attempts and current scanning status. This information is useful for tuning communication parameters to increase the efficiency with telemetry.

Message Logging for CACService

The raw I/O will be logged on demand to the screen. This is useful for discovering why the server may reject a message when the associated device is responding.

Other OPC Related Products

1. Dynagraph ActiveX Control
2. Keypad ActiveX Control

Features of CACService

• Provides industry standard design to access instrumentation data
• Customer can “plug in” the OPC Server, configure devices, tag points, and bring in real-time information to a data acquisition system quickly
• Uses eP’s 8500 or 8550 native protocols to gather tagged-base or dynagraph data from RPCs
• Supports direct connection, CDPD, dial-up modems and radio keying applications
• Supports scan scheduling to allow user to prioritize data collection from all devices
• Communication statistics for each device are displayed with details about bytes sent/received and retries
• Each communication port is handled by a separate task to increase cycle scanning time
• Access the EXS-1000 or RPC products directly through an Internet connection

CACService Options & Configurations

Telemetry Options for CACService

• Directly connected
• Dial-up modem (regular line and CDPD)
• Radio keying support
• Dynamically built tags

Communication Configuration for CACService

• Message response time-outs
• Unique address per device
• Serial device communication parameters
• Telephone number for dial-up applications
• All radio keying parameters
• Scan rate selection
• Scan priority configuration
• Transaction retry count before communication failure
• Modem configuration strings

Device and Groups Configuration for CACService

Each physical instrument may have one or more devices associated with it. The device associates data tags to collect from the instrumentation. The device may optionally group tags together to facilitate related data being displayed together.

Tag Configuration for CACService

Each tag is associated with data either being gathered and/or written to the device. Most of the tagged data is of common data types, such as analog or digital.

Dynagraph Collection for CACService

CACService facilitates gathering of dynagraph data from pump off controllers from a single tag. By using a single tag for the interface of dynagraphs, client applications may request the delivery of dynagraph data with a simple Read instruction on the tag. All the details of the interface with the controller to gather the data are transparent from the client applications.

Summary Screens for CACService

Two screens for displaying information about the communication status are available.