OPC Weatherford EIE – Data Groups

Data Groups

With few exceptions, data groups must be defined in a device template file (DTF) in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.

CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.

For information about data group definitions and device template files, see Device Template Files.

For more information about data group dependencies, see Data Group Dependencies.

Note:

When point processing is performed on history data groups, only closed records will be published and processed to points. If a device has leading timestamped records and returns the current, open record, point processing will not be performed for that record, even though there is data in the DDS transaction. The point record will be updated only when that record is closed. This is to avoid a situation where a point has multiple entries with the same timestamp, since an open record may be still updating values with each new poll, but each update will have the same timestamp. For example, say you start polling for a daily history record at 8:00am, you’ll get the first value at 8:00am, then if you poll every five minutes, you’ll get new values throughout the day at the exact same timestamp. A history record is basically an array of data with a timestamp and values where the values have different process variables for each incremental poll. The timestamp won’t get written until the record is closed, which happens at the end of the time period, in this case, a day.

OPC Weatherford EIE Data Groups

See OPC EIE Data Groups for more information about OPC data groups on an OPC Weatherford EIE device.

Browse by letter: [A] [C] [D] [E] [F] [L] [P] [R] [S] [V]

Data Group Type	Usage Notes
AnlgInCtrl	"Analog Input Control"
AnlgScan	"Analog IO Status"
CfgDg	The "Configurable Data Group" data group provides a flexible way to create custom data groups on a per-device basis. See Configurable Data Group.
CmdMsg	"Command Message"
CntrBalEff	"Counter Balance Effect"
CommStats	"Comm Statistics"
ComSetup	"Comm Setup"
CtrlInfo	The "Controller Version Information" data group must be retrieved before requesting a failure card for the "Dynagraph Card" data group. See Dynagraph Card Data Group.
CtrlParms	"Control Parameters"
CtrlTimers	"Control Timers"
CycleRtms0	"Cycle Run Time History (0-59)"
CycleRtms1	"Cycle Run Time History (60-119)"
DHCalcRes	"Downhole Calculation Results"
DHSetup	"Downhole Setup"
DigInCntrs	"Digital Input Counters"
DynaCard	The "Dynagraph Card" data group retrieves and displays surface and/or downhole rod pump cycle data. Data is displayed in table and graph format. See Dynagraph Card Data Group. These "Dynagraph Card" data groups are supported: Current Card — A current card describes the most recent stroke stored in the RTU. The device stores the last 5 current cards. Shutdown Card — A shutdown card, or pump-off card, is generated when the pump is turned off, usually to wait for the reservoir to fill. The device stores the last 5 shutdown cards in two card sets. Pumpup Card — A pumpup card is generated when the pump starts again after having been shut down. Start Card — A start card is generated when the device restarts. Alarm Card — An alarm card is created whenever an alarm condition is met in a field device. The device does not have a dedicated alarm card buffer. Instead, the Shutdown Log is queried. If the latest entry is for an alarm event, the alarm card is obtained from the shutdown card buffer. The device stores the last 5 cards. Failure Card — A failure card is created whenever a fault condition is met in a field device. The device stores the last 5 cards. The "Controller Version Information" data group must be retrieved before requesting a failure card. The firmware version is used to determine which of two techniques to use to read failure cards. This data group is required if you are connecting this device to the CygNet Dynagraph Viewer client application. Ordinals associated with the different data group types are hard coded. For instance, ordinal 0 is always Current Card, ordinal 1 is always Shutdown Card, and so forth. Ordinals here do not merely identify a sequence of "Dynagraph Card" data groups. This data group references a specific subset of support data groups and elements. These items are required to support a connected system; they are not required if you are not reliant on a connected system for functionality or data. The "Dynagraph Card" (DynaCard) data group supports embedded composite data groups.
DynaConfig	"Pumpoff Configuration" This data group is required to render the POC stroke percentage. The "Pumpoff Configuration" (DynaConfig) data group supports embedded composite data groups.
DynaHdrs	"Dynacard headers"
DynaModCfg	"Dynacard modbus config"
EvtDir	"Event Directory" See Event Directory Data Group.
FldCalcSet	"Gross Fluid Calculation Settings"
LdValsSum	"Load Values Summary"
LoadSetup	"Load Violations Setup"
LogDaily	"Logger Freeze Buffer, Daily"
LogHourly	"Logger Freeze Buffer, Hourly"
LogSetup	"Logger Setup"
PkEgyMgtCg	"Peak Energy Mgmt Config"
PwrFailDat	"Power Failure Data"
RodTypes	"Rod Types"
Runtime	"Run Time History"
SensSetup	"Sensor Setup"
SingleItem	"Single Item"
StatusData	"Status Data"
StrkLen	"Stroke Length (Manual)"
VlvChkInfo	"Valve Check Support Info"
VSDCfg	"Yaskawa VSD Configuration"
VSDCtrlSt	"Yaskawa VSD Control Status"
VSDOpHist	"Yaskawa VSD Operation History"
VSDRodLCH	"Yaskawa VSD Rod Load Ctrl Hist"
VSDRodLCS	"VSD Rod Load Control Setup"
VSDSetup	"Yaskawa VSD Setup"
VSDStatus	"Yaskawa VSD Status"