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:
-
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.
Allen Bradley CIP EIE Data Groups
| Data Group Type | Usage Notes |
|---|---|
|
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. |
|
Datatypes |
"Micro800 data types" |
|
DateTime |
"Date and Time" |
|
DGData |
"File Data" |
|
FDAscii |
"File Data (Ascii)" |
|
FDBinary |
"File Data (Binary)" |
|
FDControl |
"File Data (Control)" |
|
FDCounter |
"File Data (Counter)" |
|
FDFloat |
"File Data (Float)" |
|
FDInput |
"File Data (Input)" |
|
FDInteger |
"File Data (Integer)" |
|
FDOutput |
"File Data (Output)" |
|
FDStatus |
"File Data (Status) / Main" |
|
FDString |
"File Data (String)" |
|
FDTimer |
"File Data (Timer)" |
|
GetAttr |
"Get Attributes All" |
|
RdFragArr |
"Read Tag Fragmented (array)" See IOService for more information. |
|
RdTag |
"Read Tag Service" See IOService for more information. |
|
ReadTag |
"Read Tag" See IOService for more information. |
|
String1 |
"String 1 - Read Multi" |
|
String2 |
"String 1 - Read Tag" See IOService for more information. |
|
String3 |
"String 1 - Read Tag Fragmented" See IOService for more information. |
|
WriteStr1 |
"Write Multi" |
|
WriteStr2 |
"Write Tag" See IOService for more information. |
|
WriteStr3 |
"Write Tag Fragmented" See IOService for more information. |


