Devices > Remote Devices > Device Template Files > Elements and Attributes > card

card

card elements contain block elements that define the data required for a single Modbus DynaCard.

This element is:

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

See also Dynagraph Card Data Group.

Example

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

downholePtCount

downholePtCard specifies the number of downhole points (i.e., load-position pairs) to retrieve for a DynaCard. The number of points retrieved affects the precision of the resulting graph.

Value:
  • Must be a positive whole number.

cardNum

cardNum specifies the numeric identifier of an instance of a DynaCard type. Typically used to represent historicized instances of a card.

Value:
  • Must be a positive whole number 1 - 5.
  • Must conform to the card number(s) used by a field device and parent card type.

cardRep

cardRep specifies the type of DynaCard data represented by a card or block element.

Value:
  • Must be defined at the card or block level for every block included in a card element.
  • downhole: Indicates that the data source is downhole. If set to downhole, downholePtCount must also be defined in the parent or grandparent element.
  • none: Indicates that the data source is neither downhole nor surface.
  • surface: Indicates that the data source is surface. If set to surface, surfacePtCount must also be defined in the parent or grandparent element.

reqType

reqType specifies a unique request type for different card elements that use the same cardNum value. Effectively, this enables you to switch between two card selection modes that include the same card number.

Value:
  • singleCard: Indicates that the card is part of a single-card request. This card element must be paired with another card element in the same cardBlocks element. The other card element must use the same cardNum value and must use the reqType value multipleCard.
  • multipleCard: Indicates that the card is part of a multi-card request. This card element must be paired with another card element in the same cardBlocks element. The other card element must use the same cardNum value and must use the reqType value singleCard.

See regNum.

surfacePtCount

surfacePtCard specifies the number of surface points (i.e., load-position pairs) to retrieve for a DynaCard. The number of points retrieved affects the precision of the resulting graph.

Value:
  • Must be a positive whole number.
Back to top

Let us know how we can improve this topic.

CygNet at weatherford.com

© 2020 Weatherford. All rights reserved.