Map_Adi_Write_Area; Map_Adi_Read_Area; Map_Adi_Write_Ext_Area; Map_Adi_Read_Ext_Area - HMS Networks Anybus CompactCom 40 Network Manual

® ™
Anybus CompactCom 40 - PROFINET IRT Network PROFINET IO Object (0Eh)
13.10. Network PROFINET IO Object (0Eh)
13.10.1. Category
Extended
13.10.2. Object Description
When the application maps ADIs to process data during start-up, the Anybus CompactCom 40 PROFINET IRT will
create the module configuration as described in Real Identification (RI) (page 16). The modules in the GSDML file
must then be described in the same way. The GSDML file provided by HMS provides a few examples based on
this way of describing modules.
If the end user wishes to define modules in another way the application must provide the module configuration
to the Anybus CompactCom 40 PROFINET IRT. This is achieved by using the following commands:
• API_Add
• Plug_Module
• Plug_Submodule
• Plug_Submodule_Ext
These commands need to be sent after the process data is mapped, and before sending setup complete to the
Anybus CompactCom 40 PROFINET IRT.
Example:
Initially, the application maps ADIs as process data by calling all or some of the functions below:
• Map_ADI_Write_Area (10h)
• Map_ADI_Read_Area (11h)
• Map_ADI_Write_Ext_Area (12h)
• Map_ADI_Read_Ext_Area (13h)
Modules and submodules are now created based on this information as described in Real Identification (RI) (page
16).
1. Call API_Add to add an API.
2. Call Plug_Module to add a module to the API.
3. Call Plug_Submodule one or more times to add submodules to the module.
4. Repeat steps 2 and 3 to add modules to the API.
After the configuration is complete, call setup complete.
See also ...
• Flowchart —Establishment of Real Identification (RI) (page 212)
Page 130 of 249 SCM-1202-023 Version 2.6