Page 16 of 26 |
4.12.Map Descriptor Example 8 – Dumping the Current Record
This example is almost identical to the previous one. The one difference is that a secondary Data Array has been specified. When this is done, each time a response is received, in addition to the storage specified in the previous example, the driver dumps the response byte for byte the secondary Array. It is important to avoid overlaps in the secondary arrays if this feature is used on multiple Map Descriptors. We suggest that about
Map_Descriptors |
|
|
|
|
|
|
|
|
Map_Descriptor_Name, | Data_Array_Name, | Data_Array_Offset, | DA_Byte_Name, | Function, | Node_Name | Met1_Function, | Length, | Scan_Interval |
Read Record, | DA_DATA, | 0, | DA_DUMP, | Rdbc, | MET1, | Current Record, | 20, | 1.0s |
|
|
|
|
|
|
|
|
|
A secondary Data Array is specified with the ‘DA_Byte_Name’ parameter. When this is done the driver stores the read current record response, byte for byte, in the secondary DA.
The length specified the amount of Data Array space reserved for primary storage and has no effect on the dump. Ensure that dumps don’t overlap each other.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: 408
