Page 14 of 34 |
6.6.3.Map Descriptors Example
Only two Map Descriptors are allowed, one to transfer data to the Logix CPU and one to accept data from the Logix CPU.
// Server Side Map Descriptors |
|
|
|
|
|
| |
Map_Descriptors |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Map_Descriptor_Name, | Scan_Interval, | Function, | Node_Name, | IO_Data_Type, | DA_Name_Start4, | DA_Count, | Protocol_Type_ID |
Input_BP_Image, | 0.2s, | WRBC, | SlotServer_CPU, | REAL, | In_1, | 2, | 0 |
Output_BP_Image, | 0.2s, | RDBC, | SlotServer_CPU, | REAL, | Out_1, | 2, | 0 |
|
|
|
|
|
|
|
|
The following Data Arrays section must exist for the above Map Descriptors:
// Data Arrays |
|
|
Data_Arrays |
|
|
Data_Array_Name, | Data_Format, | Data_Array_Length |
In_1, | Float, | 76 |
In_2, | Float, | 76 |
Out_1, | Float, | 76 |
Out_2, | Float, | 76 |
|
|
|
The data format should be chosen to allow no loss of resolution with the chosen IO_Data_Type of the Map Descriptor, e.g. don’t use integer here if you intend transferring float data.
See the Data Arrays section for the maximum Data Array lengths allowed per IO_Data_Type chosen on the Map Descriptor.
4Refer to Appendix A.6 for information specific to naming Logics driver Data Arrays.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: (408)
