The preCard element contains block elements that define the initial communication parameters for all cards in a Modbus DynaCard request. The unique role of preCard blocks is reflected in the enumeration of blocks in a DynaCard data group: preCard blocks are numbered in sequence with all other blocks in the data group even though preCard blocks are not defined within card elements. A postCard block cannot have the same enumeration as any other block in the parent cardBlocks element and its enumeration must be smaller than any other block in the parent cardBlocks element. preCard use and structure varies by field device.
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
|
<cardBlocks cardOrdinal="0" surfacePtCount="200" downholePtCount="100" regByteLen="2" funcCode="4" regOff="-30001"> <preCard> <block1 regNum_singleCard="109" regNum_multipleCard="103" regOff="0" regBitLen="1" regCnt="1" funcCode="5"/> </preCard> <card cardNum="1" reqType="singleCard"> <block2 regNum="35749" regCnt="7" cardRep="surface"/> <block3 regNum="35756" regCnt="400" cardRep="surface"/> <block4 regNum="36156" regCnt="9" cardRep="downhole"/> <block5 regNum="36165" regCnt="200" cardRep="downhole"/> </card> <card cardNum="1" reqType="multipleCard"> <block2 regNum="32669" regCnt="7" cardRep="surface"/> <block3 regNum="32676" regCnt="400" cardRep="surface"/> <block4 regNum="34704" regCnt="9" cardRep="downhole"/> <block5 regNum="34713" regCnt="200" cardRep="downhole"/> </card> <card cardNum="2"> <block2 regNum="33076" regCnt="7" cardRep="surface"/> <block3 regNum="33083" regCnt="400" cardRep="surface"/> <block4 regNum="34913" regCnt="9" cardRep="downhole"/> <block5 regNum="34922" regCnt="200" cardRep="downhole"/> </card> </cardBlocks> |
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. |