Driver Manual |
4.4Client Side Map Descriptors
4.4.1FieldServer Related Map Descriptor Parameters
Column Title | Function | Legal Values |
Map_Descriptor_Name | Name of this Map Descriptor | Up to 32 alphanumeric |
|
| characters |
Data_Array_Name | Name of Data Array where data is to be | One of the Data Array names |
| stored / retrieved in the FieldServer. | from “Data Array” section above |
| The use of this array is dependent on |
|
| the Optomux command used in the map |
|
| descriptor. |
|
| For example some commands use one |
|
| data value for all module positions to be |
|
| affected by the command (Driver will |
|
| only use one data array element). Other |
|
| commands may use one data element |
|
| per module position specified. In this |
|
| case the FieldServer may use up to 16 |
|
| data array elements. |
|
| To fully understand this, read the notes |
|
| in chapter 6. |
|
Da_Bit_Name* | This parameter is only required for | One of the Data Array names |
| dynamic module position specification. | from “Data Array” section above |
| Ie. You intend using a data array to tell |
|
| the driver which module positions to |
|
| affect by a command. In this case use |
|
| this parameter. Up to 16 elements will |
|
| be inspected. The first element will |
|
| always be used for the first module |
|
| position , the 2nd element for the 2nd |
|
| module position …. |
|
| Module positions are specified by setting |
|
| the corresponding array element to a |
|
|
| |
| unspecified by setting the module array |
|
| position to zero. |
|
| The first element of this array that is |
|
| used is determined by the |
|
| Data_Array_Offset parameter. |
|
| Additional information is provided in |
|
| chapter 6. |
|
FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408)
Visit our website: www.fieldserver.com
Page 6