HMS Networks Anybus CompactCom 40 Network Manual page 25

Real Identification (RI)
4.5.2. Configuration Mismatch
General
A configuration mismatch occurs when the Real Identification (RI) does not match the Expected Identification.
Depending on how the RI configuration is established, the Anybus CompactCom 40 PROFINET IRT will first try to
resolve the mismatch as described in the applicable section below (Resolving Mismatch for default configuration
or custom configuration). If this attempt to resolve the mismatch fails, the Anybus CompactCom 40 PROFINET IRT
will provide indications as described in
Resolving Mismatch (Default Configuration)
If the Real Identification has been established according to the default mode, the Anybus CompactCom 40
PROFINET IRT will try to remap the Real Identification to match the Expected Identification.
IMPORTANT
The application must have implemented support for the remap commands in the Application Data
object (FEh), for remap to be possible.
As the Module ID contains the ADI number and the Submodule ID describes I/O direction and element section,
all information required to perform a remap is available.
NOTE
The application must be able to respond with the data type for every ADI, or a remap is not possible.
The remap is performed as follows:
• A request is sent to remap the read area. If this request is rejected no change is made to the process data map
and the Real Identification.
• If the read area remap succeeds, a write remap request is sent. If this is rejected, the process data map is in an
inconsistent state and new remap commands are sent that will remove all mappings.
• If both the read and the write remap requests succeed a new Real Identification will be built to match the
Expected Identification.
See also ...
• Default Configuration Mismatch (page 142)
• Application Data Object (FEh) (see Anybus CompactCom 40 Software Design Guide)
Resolving Mismatch (Custom Configuration)
If a configuration mismatch occurs for a custom configuration, the Anybus CompactCom 40 PROFINET IRT will
issue the command Expected_Ident_Ind to the host application. If the host application intends to change the
Real Identification based on the Expected Identification, it responds with "Block" and performs the required
Pull/Plug operations, before sending an Ident_Change_Done command to the Network PROFINET IO Object
(0Eh).
See also ....
• Custom Configuration mismatch (page 143)
• Expected_Ident_Ind, see command details in
• Ident_Change_Done, see command details in
SCM-1202-021 Version 2.6
Anybus
Further Actions to Resolve Mismatch (page
(flowchart)
(flowchart)
PROFINET IO Object (F6h) (page 112)
Network PROFINET IO Object (0Eh) (page 59)
® ™
CompactCom 40 - PROFINET IRT Transparent
18).
Ethernet
Page 17 of 177