| Page 21 of 31 |
Appendix A.2. Using the Carrier Datalink Driver to Obtain Field Names
The Carrier Datalink driver can be used to obtain a list of variable names for a given table using the following Map Descriptors. It is recommended that these Map Descriptors are removed from the configuration after the variable names have been obtained as they will consume resource and processing time.
The following example illustrates a Map Descriptor which reads a table and dumps the response in ASCII format to a Data Array which can be browsed using RUINET (Refer to RuiNet Manual)
Data_Arrays |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Data_Array_Name, |
| Data_Format, | Data_Array_Length |
|
|
|
|
|
|
|
| ||||
DA_DUMP | , |
| BYTE | , | 2000 |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Map Descriptors |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Map_Descriptor_Name, | Data_Array_Name, | Data_Array_Offset, | Function, | Node_Name, | Length, | Scan_Interval, | Table_Name | Field_Name, | Storet_As | ||||||
Md1 |
| , |
| DA_DUMP | , | 0 | , | rdbc , | FAN01 , | 1000 , | 5.0s, | DISPLAY , | EVERYTHING, | Ascii |
The s=data array DA_DUMP has been defined with format BYTE. When viewing this table with RUINET display the array in ‘STRING’ format so that you can read it.
This is what tells the driver to dump the table, its variables names and variable descriptions in ASCII format.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)