The adjustment of the process image of modules with a variable processimage size should not be made by the object 0x31yy, since otherwiseonly the length in the module is adjusted but EtherCAT coupler andmaster further use the standard length!4.8 Object DictionaryIndex Object Dictionary Area0x0000 ... 0x0FFF Data Type Area0x1000 ... 0x1FFF Communication Area0x2000 ... 0x5FFF Manufacturer Specific Area0x6000 ... 0x6FFF Input Area0x7000 ... 0x7FFF Output Area0x8000 ... 0x8FFF Configuration Area0x9000 ... 0x9FFF Information Area0xA000 ... 0xAFFF Diagnosis Area0xB000 ... 0xBFFF Service Transfer Area0xC000 ... 0xEFFF Reserved Area0xF000 ... 0xFFFF Device AreaPlease consider the System SLIO power and clamp modules do not haveany module ID. These may not be recognized by the EtherCAT couplerand so are not listed respectively considered during slot allocation.Further within EtherCAT the slots are designated as EtherCAT-Slot. Thecounting always begins with 0.In the following example at the physical slot 2 a clamp module (CM) is connected. Sincethe clamp module does not have any module ID, this is not recognized by the EtherCATcoupler. So in EtherCAT the next module is mapped to EtherCAT-Slot 1 and so on.Index:Sub - Index and subindexUx - Data type UNSIGNEDxVSTRG - Data type VISIBLE STRINGAccess - Read, write access (ro: Read access only, rw: Read and write access)Default - Default valueOffset - Please note the offsetDevice TypeIndex:Sub Name Type Access Default Description0x1000:00 Device type U32 ro 0x00001389 0x00001389 means MDPÄ ‘Explanation of the elements’ page 71Object overviewExplanation of the ele-mentsVIPA System SLIO DeploymentObject DictionaryHB300 | IM | 053-1EC01 | en | 18-49 71