postCard

The postCard element contains block elements that define the terminal communication parameters for all cards in a Modbus DynaCard request. The unique role of postCard blocks is reflected in the enumeration of blocks in a DynaCard data group: postCard blocks are numbered in sequence with other blocks in the data group even though postCard 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 larger than any other block in the parent cardBlocks element. postCard use and structure varies by field device.

This element is:

• Case sensitive
• Not required in a DynaCard-enabled, Modbus device template file
• If used, used 1 time per cardBlocks element

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

Click here to see an example of the element   <cardBlocks cardOrdinal="0" surfacePtCount="50" regByteLen="2" funcCode="3" regOff="-40001" txMaxRegCnt="124"> <card cardNum="1" surfacePtCount="200" downholePtCount="200"> <block1 regNum="57201" regCnt="477" cardRep="none"/> <block2 regNum="50001" regCnt="400" cardRep="surface"/> <block3 regNum="50401" regCnt="400" cardRep="surface"/> <block4 regNum="50801" regCnt="400" cardRep="downhole"/> <block5 regNum="51201" regCnt="400" cardRep="downhole"/> </card> <card cardNum="2" cardRep="surface"> <block1 regNum="57201" regCnt="477" cardRep="none"/> <block2 regNum="58401" regCnt="100"/> <block3 regNum="58801" regCnt="100"/> </card> <postCard> <block6 regNum="60000" regCnt="2"/> </postCard> </cardBlocks>

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.