dgOrdinals

The dgOrdinals element enables you to define a list in a device template file that specifies data group ordinal numbers along with corresponding ordinal names. Once defined, access the list on a per-data group basis in the remote device editor where it appears on the Data Group Properties dialog box as a drop-down list. This feature is useful when data group ordinals have a very specific purpose, typically as described in a device manufacturer protocol.

This element is:

To learn about how this element relates to other elements in a CygNet device template file, see Device Template File Hierarchy.

Example

<Trend niceName="Trend" maxCnt="15" dgCat="trend" hasArray="true" ordLabel="Trend #">

<dgOrdinals>

<e0 value="Valve Check"/>

<e1 value="Inactive #1"/>

<e2 value="Inactive #2"/>

<e3 value="General #1"/>

<e4 value="General #2"/>

<e5 value="Stroke #1"/>

<e6 value="Stroke #2"/>

<e7 value="Speed #1"/>

<e8 value="Speed #2"/>

<e9 value="Time #1"/>

<e10 value="Time #2"/>

<e11 value="Time #3"/>

<e12 value="Time #4"/>

<e13 value="Idle Time"/>

<e14 value="Run Time"/>

</dgOrdinals>

<dgElements secLev="4">

<DateTime desc="Time" structOff="1:0" type="r8" cvtF="TimeSeconds" isUTC="true" hidden="true"/>

<DateTimeT desc="Time" ref="DateTime" type="string" format="DateTime"/>

<Value desc="Value" structOff="1:4" type="vrnt" arrSize="1000"/>

</dgElements>

<readBlocks>

<block1 regNum="65450" regCnt="1" type="struct" len="2004"/>

</readBlocks>

</Trend>

Supporting Elements

The following table lists and describes special child elements used within an dgOrdinals element's container elements.

Attribute Description

ex

Empty elements are used within a container element to make up a list of possible values.

Each enumeration must begin with a lowercase e. It is then to be followed by a non-negative integer. The integers used do not need to be sequential. For instance, you could use 0, 4, and 7.

Each enumeration element must be unique, but its value does not need to be unique. For example, using e1 twice within a single enumeration list is illegal. But using the value "Some Meaningful Text" for e1 and e2 is legal.

Each enumeration must use a value attribute to define a constant value that corresponds to the enumeration.

Attributes

The following table lists and describes attributes generally applicable to this element. However, not all of the attributes listed here are applicable to all EIEs. Additionally, some attributes are required for use in every device template file of a certain EIE, but others may be used on a case-by-case or device-by-device basis, depending on your specific needs. All attributes in templates are case sensitive; but the case sensitivity of attribute values is based on context.

Note: Occasionally, device template files for different EIEs use attributes of the same name that do different things. Efforts are made in this document to highlight cases where an attribute by one name does different things in different EIEs.

Attribute Description

N/A

None apply at this time.

Back to top