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 IIoT Secure 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 IIoT Secure will provide indications as described in Further Actions to Resolve Mismatch.
Resolving Mismatch (Default Configuration)
If the Real Identification has been established according to the default mode, the Anybus CompactCom 40 PROFINET IRT IIoT Secure 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 (flowchart)
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 IIoT Secure 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 (flowchart)
Expected_Ident_Ind, see command details in PROFINET IO Object (F6h)
Ident_Change_Done, see command details in Network PROFINET IO Object (0Eh)
Further Actions to Resolve Mismatch
If the mismatch remains unsolved, either for default or custom configuration, the following will be performed by the Anybus CompactCom 40 PROFINET IRT IIoT Secure to find a solution that will make exchange of valid data possible:
- Incomplete output mapping:
If the controller tries to connect to fewer output submodules than are plugged by the application, the controller will not be granted ownership of any output submodule. The Anybus state is set to ERROR and the LEDs will indicate configuration mismatch. Matching input submodules will be owned by controller and work normally.
- Incomplete input mapping:
The controller may choose to connect to a subset of the available input submodules without any restrictions. Anybus state is set to PROCESS_ACTIVE and no error is indicated on any LED.
- Mismatch of submodule(s):
As long as all of the output submodules of the Real Identification are present and matching in the Expected Identification, the Anybus state is set to PROCESS_ACTIVE. However, if there is any mismatch among the other submodules the LEDs will indicate configuration mismatch.
See also...
The Remap_ADI_Write_Area and Remap_ADI_Read_Area commands in the Application Data Object (FEh), found in Anybus CompactCom 40 Software Design Guide.