preCard

The preCard element contains block elements that define the initial communication parameters for all cards in a Modbus DynaCard request. Block numbers must be unique across all preCard, card, and postCard sections. The block numbers in the preCard section must be less than any block number in the card section. Use of the preCard section is optional, and 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 Device Template File Hierarchy.

See also Modbus EFM EIE Dynagraph Card Data Group.

Example

Click here to see an example of the element <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>

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.