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:
- Except for UDC mapping, native, predefined data groups can not be altered in the device template file. Only the "Generic TLP Data" data group enables user alterations.
- A valid "ROC Config" (RtuConfig) data group must be retrieved before other data groups can be retrieved or sent. The data group should always be repolled if there are configuration changes to the field device, after a CygNet upgrade, after importing a device or after modifying the device template file.
- The attribute minFirmwareVer can be configured in the device template file to specify the minimum firmware version supported for the specified TLP of the DEID. If the firmware version information has not been successfully retrieved from the field device, any TLP using the minFirmwareVer attribute will be excluded. To retrieve the firmware version information, poll the "ROC Config" (RtuConfig) data group or the "System Variables" (SysVars) data group.
-
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.
-
Best practice recommends that you do not perform UDC and point processing on FMS data groups. The DEIDs specified in FMS data groups are generic and use the eFMS enumeration to identify the CygNet-defined FMS items referenced in the device template file. No polling is done on these data groups — all data is coming from the native data groups. Points should be mapped to the native data groups since that is the data group that is actually processing the device data. While point processing may work on the FMS data groups, it is not supported, not tested, not consistent across EIEs, and is not recommended practice.
- CygNet Gas Measurement Repository (GMR) has been discontinued. Effective with the CygNet v8.5.0 release, GMR files must be migrated to FMS. See Migrating Data Groups from GMR to FMS to migrate data groups for Emerson ROC devices.
Emerson ROCPlus EIE Data Groups
Browse by letter: [A] [C] [D] [E] [F] [G] [H] [I] [L] [M] [O] [P] [R] [S] [T] [U] [V] [W]
| Data Group Type | Usage Notes |
|---|---|
|
The "Analog Input" data group uses point type 103. Use the following equation to supply the correct ordinal number in the AI# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog input designation is 7-1 in ROCLINK, AI# is 56. |
|
|
"Alarm Log" stores up to the last 450 alarms. |
|
|
AO800 |
The "Analog Output" data group uses point type 104. Use the following equation to supply the correct ordinal number in the AO# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, AO# is 56. |
|
"Analog Output - Auto Value" is point type 104, parameter 12. Use the following equation to supply the correct ordinal number in the AO# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, AO# is 56. |
|
|
APM800 |
"Advanced Pulse Module" |
|
The "Configurable Opcode Settings" data group uses point type 99. If you add this data group, also add a "Configurable Opcode Data" data group. Read this data group before reading the "Configurable Opcode Data" data group to ensure that the table data is interpreted correctly. Use ROCLINK to configure a configurable Opcode table. Although ROCLink allows you to skip items when configuring the table, CygNet requires the items to be contiguous. If you make changes to the Opcode table configuration, poll this data group afterwards. |
|
|
The "Configurable Opcode Data" data group works in conjunction with a "Configurable Opcode Settings" data group. Retrieving this data group automatically retrieves required configurable Opcode settings. Use ROCLINK to configure a configurable Opcode table. Although ROCLink allows you to skip items when configuring the table, CygNet requires the items to be contiguous. Any data after a skip will not be retrieved. If you make changes to the Opcode table configuration, poll this data group afterwards. |
|
|
"Time / Date" |
|
|
DensityIF |
The "Liquid Density Interface" data group uses point type 202. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. |
|
DI800 |
The "Discrete Input" data group uses point type 101. Use the following equation to supply the correct ordinal number in the Point # field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, Point # is 56. |
|
DO800 |
The "Discrete Output" data group uses point type 102. Use the following equation to supply the correct ordinal number in the DO# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, DO# is 56. |
|
The "Discrete Output - Auto Out Value" data group uses point type 102. Use the following equation to supply the correct ordinal number in the DO# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, DO# is 56. |
|
|
The "Discrete Output - TDO EU Value" data group uses point type 102. Use the following equation to supply the correct ordinal number in the DO# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog output designation is 7-1 in ROCLINK, DO# is 56. |
|
|
The "Event Log" data group uses Opcode 119 by default. However, you can use the readOpCode attribute in the device template file to substitute Opcode 204 for 119. 204 provides a less messaging-efficient, but more complete, option to 119. Up to the last 450 events are stored. See the various Weights and Measures Event Logs for event information specific to liquids. |
|
|
"FMS Alarms" FMS data group units displayed in the DDS reflect their points of origin. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. Dependencies:
|
|
|
FmsConfig |
"FMS Configuration" is required if you use FMS. When adding an "FMS Configuration" data group, specify the meter type and ordinal number of the supporting meter configuration data group in the Meter Type area. Possible meter type options are as follows:
This data group supports send/write functionality. However, sends can only be initiated from FMS. Sending periodic quality from FMS to a field device requires you to instantiate each "FMS Configuration" support data group for the applicable remote device before initiating the send from FMS. FMS data group units displayed in the DDS reflect their points of origin. "FMS Configuration" must be retrieved before polling other FMS data groups of the same ordinal. Dependencies:
|
|
"FMS Events" Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. FMS data group units displayed in the DDS reflect their points of origin. A "Special Configuration Events" event appears in the Event Category column of the "FMS Events" data if any one of the following configuration properties is changed on a field device:
The "special" status sets a flag for the event's display in FMS Explorer. See Special Configuration Events for more information about these events. Dependencies:
|
|
|
"FMS Daily PM History" History points must be defined in this data group's properties. Best practice recommends polling the "History Segment Config Summary" (HSeg800Sum) data group before configuring a measurement history data group. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. FMS data group units displayed in the DDS reflect their points of origin. For information about how ordinals are formed for this data group, see History Ordinals and Points. Dependencies:
|
|
|
"FMS Daily PQ History" History points must be defined in this data group's properties. Best practice recommends polling the "History Segment Config Summary" (HSeg800Sum) data group before configuring a measurement history data group. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. FMS data group units displayed in the DDS reflect their points of origin. For information about how ordinals are formed for this data group, see History Ordinals and Points. Dependencies:
|
|
|
"FMS Hourly PM History" History points must be defined in this data group's properties. Best practice recommends polling the "History Segment Config Summary" (HSeg800Sum) data group before configuring a measurement history data group. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. FMS data group units displayed in the DDS reflect their points of origin. For information about how ordinals are formed for this data group, see History Ordinals and Points. Dependencies:
|
|
|
"FMS Hourly PQ History" History points must be defined in this data group's properties. Best practice recommends polling the "History Segment Config Summary" (HSeg800Sum) data group before configuring a measurement history data group. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. FMS data group units displayed in the DDS reflect their points of origin. For information about how ordinals are formed for this data group, see History Ordinals and Points. Dependencies:
|
|
|
FmsProduct |
"FMS Liquid Product" enables the retrieval of liquid product data by an associated CygNet Measurement system. A single set of 24 liquid products is shared by all liquid meters. However, liquid product data is sent to FMS with meter-specific data on a per-meter basis. Each instance of LiqMeter and its corresponding FmsProduct data group share both the set of liquid products as well as meter-specific product values. Applicable RtuConfig, FmsConfig, LiqMeter, and FmsProduct data group types must be instantiated to poll FmsProduct. RtuConfig and FmsConfig must be polled before polling FmsProduct. Dependencies:
|
|
FmsTicket |
"FMS Liquid Ticket" must be instantiated to retrieve transactional history for use in CygNet Measurement. History points must be defined in this data group's properties. Ticket items are FMS-specific items. Transactional history points are field device-specific points that make up a given transaction set. You must manually map applicable ticket items to transactional history points. You must also manually specify units for every transaction history point to which they apply. For a complete list of FMS ticket items, see FMS Ticket Data Items. For a list of FMS ticket items that might not have a corresponding Emerson history point, see FMS Ticket Item Mapping. The Transaction Set # value is filled in by default. You can override this value if you choose. But if you change a Transaction Set # value after configuring the data group, you must click Update to apply the new transaction configuration. If you change the transaction set configuration on the applicable field device, you must also click Update to apply the new transaction configuration. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. See also Collecting Ticket Data. Dependencies:
|
|
FST800 |
The "FST Parameters" data group uses point type 96. A maximum of 6 "FST Parameters" data groups can be added per remote device. |
|
"Generic TLP Data" See Generic TLP Data Group. |
|
|
The "HART Device 1" data group uses point type 85. |
|
|
HARTD2 |
The "HART Device 2" data group uses point type 85. |
|
HARTD3 |
The "HART Device 3" data group uses point type 85. |
|
HARTD4 |
The "HART Device 4" data group uses point type 85. |
|
HARTD5 |
The "HART Device 5" data group uses point type 85. |
|
HARTSUM |
The "HART Summary" data group uses point type 85. |
|
"History – Daily/Periodic for Day" For information about how ordinals are formed for this data group, see History Ordinals and Points. |
|
|
Hist60800 |
"History – Sixty Minute Point" For information about how ordinals are formed for this data group, see History Ordinals and Points. |
|
HistD800 |
"History – Daily" For information about how ordinals are formed for this data group, see History Ordinals and Points. |
|
HistIdx |
The "History Indices" data group uses point type 124. This data group retrieves and displays the maximum number of periodic points, the periodic index, and the contract hour for available history segments. |
|
HistIdxD |
The "History Indices - Daily" data group uses point type 124. This data group retrieves and displays the maximum number of daily points and the daily index for available history segments. |
|
HistIdxDS2 |
The "History Indices - Daily Series 2" data group uses point type 124. This data group retrieves and displays the maximum number of periodic points, the periodic index, and the contract hour for available history segments. |
|
HistIdxS2 |
The "History Indices Series 2" data group uses point type 124. This data group retrieves and displays the maximum number of daily points and the daily index for available history segments. |
|
The "History Multiple Points Daily" data group is used to optimize the retrieval of row-based daily history for multiple points using Opcode 136 (History Multiple Points Periodic). See also History Retrieval Optimization. |
|
|
The "History Multiple Points Minute" data group is used to optimize the retrieval of row-based minute history for multiple points using Opcode 136 (History Multiple Points Periodic). See also History Retrieval Optimization. |
|
|
The "History Multiple Points Periodic" data group is used to optimize the retrieval of row-based periodic history for multiple points using Opcode 136 (History Multiple Points Periodic). See also History Retrieval Optimization. |
|
|
HPtCfg800 |
The "History Point Configuration" data group uses point type 125. This data group obtains the TLPs assigned to history within a segment. |
|
HSeg800 |
"History Segment Configuration" |
|
HSeg800Sum |
The "History Segment Config Summary" data group uses point type 124. Use the Edit buttons corresponding to segments to access and edit the corresponding "History Segment Configuration" data group. Use the View Points buttons corresponding to segments to access and view the corresponding "History Point Configuration" data group. This option is unavailable for segments with no configured points. Polling this data group before configuring a measurement history data group ensures that the number of history points available to a measurement history data group is constrained to the total of history points configured for the specified segment on a field device. For example, if you first poll HSeg800Sum and history segment 2 is configured to include 27 history points, a measurement history data group with a history segment of 2 can include up to 27 history points. Keep in mind that while the history points are contiguous, not all points in a segment must be configured. (The default history point limit is still 200.) |
|
"I/O Point List" enables you to request the type and/or logical number of all I/O points in their physical order from a connected field device. This in turn enables you to focus on only those I/O point collections you most care about, making it easier to create your own I/O data groups. IoPntCfg uses Opcode 50. You can select the Add Data Groups button to automatically create I/O data groups that have not previously been created. The Tag column does not display a value until that I/O data group has been retrieved. |
|
|
The "Liquid Meter Run Configuration" data group uses point type 204. Applies to any linear meter that uses a pulse stream, including turbine, Coriolis, and ultrasonic meters. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. |
|
|
LiqMtrEx |
The "Liquid Meters Extended" data group uses point type 205. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. |
|
LiqPref |
The "Liquid Preferences" data group uses point type 200. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. Note: For liquid meters, global contract hour comes from two different locations, depending on the firmware version of the ROC800L device. For firmware versions up to but not including 1.03, the contract hour for all liquid meters is in the General History Segment #0 in TLP 124,0,8. For firmware versions 1.03 and later, the contract hour is in the "Liquid Preferences" data group in TLP 200,0,89. The firmware version is found in the "System Variables" data group (Other information page). Best practice recommends configuring the global contract hour in the "Liquid Preferences" data group, and then the value will get pushed to all associated history segments for all meters and stations. When you go to retrieve history data, each segment will have the appropriate contract hour. |
|
LiqProd |
The "Liquid Products" data group uses point type 201. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. |
|
Liquid Station |
The "Liquid Station" data group uses point type 203. See also Collecting Liquid Periodic Data, Collecting Batch Data, and Collecting Ticket Data. |
|
The "Login Request" data group is issued to the device via Opcode 17. It is only relevant if the port being used to communicate with the target field device is security enabled. This data group enables a user with valid credentials to communicate with a field device from the CygNet host. As long as that user is logged in, subsequent messaging is allowed through the relevant communication port and the user's ID is included in event log records. If the relevant port is security enabled, a log-in request using invalid data will fail with an error message of "invalid header". The "Login Credentials" data group can be used to see the valid credentials as they are defined on a field device. If the relevant port is security disabled, a log-in request with invalid data will succeed since no internal Emerson validation is performed. A user might be unexpectedly logged out if any one of the following conditions occurs:
Write capability for access levels is disabled in CygNet. See Emerson device security documentation for more details. |
|
|
The "Login Credentials" data group uses point type 92. This data group reads operator IDs and their corresponding password and access level from a field device. These items must be configured on the field device before CygNet can read them. The field device does not allow the credentials to be configured from external applications like CygNet. The credentials that are displayed in this data group are the only valid ones that can be used in the "Login Request" data group. As with all CygNet data groups, you can set individual CygNet security permissions for this data group. |
|
|
The "Login Secure Enhanced Request" data group enables a user with enhanced security credentials to communicate with a field device from the CygNet host. The login request is issued to the device via Opcode 17. The data group operates with a Login Secure UIS command and LOGINSEC command component type. Enhanced secure login credentials are configured in the Login secure section of the Device page of the remote device editor. Note: This data group applies to ROC800 and ROC800L remote devices. It complies with enhanced security features required by the United States Transport Security Administration (TSA) Security Directive Pipeline-2021-02. See Emerson device security documentation for more information. |
|
|
The "Logout Request" data group is issued to the device via Opcode 17. |
|
|
The "Meter Batch - Current" data group uses point type 213. See also Collecting Batch Data. |
|
|
MtrHistB |
The "Meter Batch - History" data group uses point type 214. See also Collecting Batch Data. |
|
Multi-Variable Sensor (1 of 2) |
Use in combination with "Multi-Variable Sensor (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
Multi-Variable Sensor (2 of 2) |
Use in combination with "Multi-Variable Sensor (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
MVS800 |
The "Multi-Variable Sensor" data group uses point type 108. |
|
The "Orifice Meter Run Configuration" data group uses point type 113. A total of 12 orifice meter runs can be configured for an associated field device. |
|
|
OMRV800 |
The "Orifice Meter Run Values" data group uses point type 114. |
|
"Periodic History" For information about how ordinals are formed for this data group, see History Ordinals and Points. See also History Retrieval Optimization. |
|
|
"Periodic Daily History" For information about how ordinals are formed for this data group, see History Ordinals and Points. See also History Retrieval Optimization. |
|
|
PI800 |
The "Pulse Input" data group uses point type 105. Use the following equation to supply the correct ordinal number in the PI# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the pulse input designation is 7-1 in ROCLINK, PI# is 56. |
|
PID Control Parameters (1 of 2) |
Use in combination with "PID Control Parameters (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
PID Control Parameters (2 of 2) |
Use in combination with "PID Control Parameters (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
PID Control Params |
The "PID Control Params" data group uses point type 110. |
|
PID800 |
The "PID Control Parameter" data group uses point type 110. |
|
PvrCfg |
The "Prover Config" data group uses point type 206. |
|
PvrFinal |
The "Prover Final Report" data group uses point type 208. |
|
PvrTrial |
The "Prover Trial Report" data group uses point type 207. |
|
The "Reporting Program" data group uses point type 219. |
|
|
RTag800 |
The "FST Register Tags" data group uses point type 97. A maximum of 6 "FST Register Tags" data groups can be added per remote device, each with a maximum of 10 register tags. |
|
RTD800 |
"RTD" |
|
RtuConfig |
A valid "ROC Config" (RtuConfig) data group must be retrieved before other data groups can be retrieved or sent. The data group should always be repolled if there are configuration changes to the field device, after a CygNet upgrade, after importing a device or after modifying the device template file. All available and relevant point types for the associated field device are displayed in table format in the ROC Config properties dialog box. |
|
The "System Analog Input" data group uses point type 109. Use the following equation to supply the correct ordinal number in the AI# field on the Data Group Properties dialog box:
Module# and Point# are obtained from ROCLINK. For example, if the analog input designation is 7-1 in ROCLINK, AI# is 56. |
|
|
Sampler |
The "Sampler" data group uses point type 220. |
|
"Single TLP" enables you to read from and write to a single user-specified TLP. You can use a single-element data group on an ad hoc basis from a data group editor or set up a UIS command that uses a single-element data group. You can use a remote device editor dialog box to enter a user-defined TLP. To do so, configure the data group as usual, but type in the desired values for the fields Point type, Logical #, and Parameter # in the TLP settings. Both the Point type and Parameter # fields are combo boxes that enable you to type your own values rather than only selecting from a list of known TLPs. |
|
|
Soft Point Parameters (1 of 2) |
Use in combination with "Soft Point Parameters (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
Soft Point Parameters (2 of 2) |
Use in combination with "Soft Point Parameters (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
Soft800 |
The "Soft Point" data group uses point type 98. |
|
SP800 |
The "Station Params (Orifice, Linear)" (or "Station Parameters" for the ROC800) data group uses point type 112. A total of 12 stations can be configured for an associated field device. |
|
The "Station Params (Liquids)" data group uses point type 203. A total of 6 stations can be configured for an associated field device. |
|
|
Station Parameters (1 of 2) |
Use in combination with "Station Parameters (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
Station Parameters (2 of 2) |
Use in combination with "Station Parameters (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
StnBatCfg |
The "Station Batch Configuration" data group uses point type 210. See also Collecting Batch Data. |
|
StnBatCurr |
The "Station Batch - Current" data group uses point type 211. See also Collecting Batch Data. |
|
StnBatHist |
The "Station Batch - History" data group uses point type 212. See also Collecting Batch Data. |
|
StnBatQ |
The "Station Batch Queue" data group uses point type 216. |
|
StnBatQCfg |
The "Station Batch Queue Cfg" data group uses point type 215. |
|
The "System Variables" data group uses point type 91. |
|
|
System Variables (1 of 2) |
Use in combination with "System Variables (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
System Variables (2 of 2) |
Use in combination with "System Variables (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
The "Linear Meter Run Configuration" data group uses point type 115. A total of 12 linear meter runs can be configured for an associated field device. This data group was formerly known as "Turbine Meter Run Configuration". |
|
|
Turbine Meter Values (1 of 2) |
Use in combination with "Turbine Meter Values (2 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
Turbine Meter Values (2 of 2) |
Use in combination with "Turbine Meter Values (1 of 2)". Note: This is a legacy data group that is no longer supported by CygNet. It has been consolidated into a single data group that preserves the functionality of the obsolete, paired data group it replaces. |
|
The "Linear Meter Values" data group uses point type 116. This data group was formerly known as "Turbine Meter Values". |
|
|
The "Transactional History Cfg" data group defines transactional history configuration information for individual transaction sets. The data group is ordinalized to reflect individual transaction sets. One such data group is required for each transaction set that you want to collect data from. To configure the transactional history points that make up a transaction set, use the "Transactional History Point Cfg" data group. A new transaction can not be triggered using this data group. Use the TXHISTRG command component to trigger a transaction. See also Collecting Ticket Data. |
|
|
TxHisCfgLk |
The "Transactional History Cfg Lock" data group can not be edited and does not appear in the remote device editor. Its purpose is to facilitate the locking and unlocking of transactional point configuration. See also Collecting Ticket Data. |
|
Warning: An edit initiated from this data group unlocks the transaction configuration. If you change the configuration of an existing transaction set, all of the set's existing data is wiped from the field device to accommodate the new configuration. The "Transactional History Point Cfg" data group defines point configuration information for individual transaction sets. Each transaction set can be made up of a maximum of 100 TLP data points. These TLPs are user configurable; how many you add and which you add depends on the amount of available storage on the field device. A new transaction can not be triggered using this data group. Use the TXHISTRG command component to trigger a transaction. See also Collecting Ticket Data. |
|
|
The "Transactional History" data group displays historicized transactional data on a per-transaction set basis. The data group is ordinalized to reflect individual transaction sets; data for a transaction set is displayed by timestamps that fall within the specified time range. The historical data that makes up this grid can be requested from existing transaction set records stored on the field device, but a new transaction can not be triggered using this data group. Use the TXHISTRG command component to trigger a transaction. See also History Retrieval Optimization. See also Collecting Ticket Data. |
|
|
The "Transactional History Trigger" data group is a kind of event record for transactions initiated from CygNet. Each TXHISTRG command issued is recorded in this data group. If you want to maintain a record of transaction set triggers initiated from CygNet, you must instantiate a "Transactional History Trigger" data group for each applicable transaction set. That is to say, if you have 5 transaction sets and want to maintain trigger event records for each, you must add 5 of these data groups to your Device Definition Service (DDS), each ordinalized accordingly. Records of CygNet-initiated triggers cannot be viewed as DDS transactions without this data group, although fields in the "Transactional History Cfg" data group editor(s) reflect the number of transactions. A new transaction can not be triggered using this data group. Use the TXHISTRG command component to trigger a transaction. See also Collecting Ticket Data. |
|
|
The "User Program Status" data group uses point type 94. It enables the retrieval of status information for a user-defined C program used on a specific Emerson field device. If the user program version information has not been successfully retrieved from the field device, any TLP using the minUProgVer attribute will be excluded. To retrieve the user program version information, poll the "ROC Config" (RtuConfig) data group or the "User Program Status" (UserPgStat) data group. See also User Programs. |
|
|
UserProg |
The "User Program Configuration" data group uses point type 94. It enables the retrieval of configuration information for a user-defined C program used on a specific Emerson field device. See also User Programs. |
|
The "V-Cone Meter Run Configuration" data group uses point type 61 or 71, as defined by your user program. This data group is only meaningful if you've installed the relevant cone user program on your field device. If you are uncertain, poll "User Program Status" and confirm. Every "V-Cone Meter Run Configuration" data group requires an associated "Orifice Meter Run Configuration" data group to support it. To associate these data groups, add and poll a "V-Cone Meter Run Configuration" data group, then use its Meter data group element current value to determine the associated orifice run's ID. Add the corresponding "Orifice Meter Run Configuration" data group. The second numeral in the "V-Cone Meter Run Configuration" data group Meter data group element (i.e., the 2 in 113,2,0) identifies the logical number of a meter run. If you configure FMS for use with a cone meter, a "V-Cone Meter Run Configuration" data group and an associated "Orifice Meter Run Configuration" data group are necessary to supply the cone data required by FMS. However, only the "V-Cone Meter Run Configuration" data group is explicitly associated with the FMS data group. |
|
|
"Wafer-Cone Meter Configuration" |
|
|
The "Weights and Measures Events Log" data group uses Opcode 117 by default. However, you can use the readOpCode attribute in the device template file to substitute Opcode 204 for 117. 204 provides a less messaging-efficient, but more complete, option to 117. The "Weights and Measures Events Log" holds up to 1000 events. |
