Amocams 700 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.

Notes:

Max Records limits the number of records to be retrieved with one request. This value is available on the Data Group Properties dialog box for log data groups. This value is a configurable parameter on the data group property page. When multiple log message types are used, like Change Log and Event Log for FMS Legacy Events, the max records limit applies to each message type. When this condition has occurred, the data group transaction shows a status of "Get Failed" and the records that were retrieved are displayed. The ELS displays the additional information of "Partial Success: maximum record limit reached."
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.

Amocams 700 EIE Data Groups

Browse by letter: [C] [D] [E] [G] [H] [M] [P] [R] [S] [T]

Data Group Type	Usage Notes
ChangeLog	"Change Log" caches next message ID and timestamp. Displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Clear cache option available.
CntlDwnld	"Control Parameters"
Composite Data Group	The "Composite Data Group" is a special kind of data group that enables you to combine any data group element(s) from any data group(s) as long as they are in the same template as the composite data group. The "Composite Data Group" does not appear in a remote device editor unless it has been defined in the relevant device template file. See Composite Data Group.
CtrlLogL	"Control Logs (Long)" displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Get Latest functionality available. Clear cache option available.
CtrlLogS	"Control Logs (Short)" displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Get Latest functionality available. Clear cache option available.
DailyVals	"Daily History Rollup" The values come from the "History - Hourly" data group.
DProdLog	"Daily Prod Log" displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Get Latest functionality available. Clear cache option available.
EGMConvF	"EGM Conversion Factors". See length to override record length.
EGMFacts	"EGM Factors". See length to override record length.
EGMGas	"EGM Gas Composition". See length to override record length.
EGMMtrRun	"EGM Meter Run". See length to override record length.
EGMParms	"EGM Parameters". See length to override record length.
EGMPlus	"EGM Parameters Plus"
EndDevInd	"End Device Indexes"
EventLog	"Event Log" caches next message ID and timestamp. Displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Clear cache option available.
GChangeLog	"Change Log General"
GEventLog	"Event Log General"
GmrCfgSend	"FMS Legacy Config Send Data" is used to send modified FMS Legacy data from the FMS to the field device. It reads each support data group, updates the values sent from the FMS, and sends the data to the field device. This data group is required only if you plan to use FMS and want to perform this specific task. Support data groups: EGMGas data groups enumerated in device template file for customDg data group element.
GmrConfig	"FMS Legacy Configuration Data" Support data groups: EGMConvF EGMFacts EGMGas EGMMtrRun EGMParms data groups enumerated in device template file for customDg data group element.
GmrEvent	"FMS Legacy Events Data" Support data groups: ChangeLog EventLog (if defIncAlarms="true" in device template)
GmrHist	"FMS Legacy History Data" Support data groups: HrlyHist
HrlyHist	"History - Hourly" A new optional attribute, named autoDetectResponse, is available on the "History – Hourly" (HrlyHist) data group for the Amo700EGMP2 and Amo700EGMWC devices that return a different response to the Upload Audit Log command. If autoDetectResponse="true", the Amocams EIE will parse the data based on data length of the response. Response data will be parsed according to the Command Code 32 EGM layout as defined in the Communication Manuals for Models 700EGMWC and 700EGMP2 if the response data length matches.
MiscCntl	"Misc Control Parameters"
MProdLog	"Monthly Prod Log" displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Get Latest functionality available. Clear cache option available.
ProdCLog	"Prod Cycle Log" displays cache in data group dialog box. Displays current and next message IDs in data group dialog box. Uses optimized requests with start-date margin. Get Latest functionality available. Clear cache option available.
ProdHist	"Production History (26)". See length to override record length.
ProdRep	"Production Report (27/28)"
PulseRelay	"Pulse Relay"
ResetCntl	"Reset Control"
Scan2A	"Scan 2A - Rate/Vol/FlwCtrl". See length to override record length.
Scan2B	"Scan 2B - ATMOS Stn Scan list". See length to override record length.
Scan21	"Scan 21 - Analogs/Rates". See length to override record length.
Scan22	"Scan 22 - Analogs/Rates". See length to override record length.
SwabCtrl	"Swab Control"
TankShut	"Tank Shutdown". See length to override record length.
TProdCLog	"Test Set Prod Cycle Log"
TimeVer	"Date, Time and Version". See length to override record length.