Example: Mapping Conversion
An SWC created with ASCET V6.3 is opened with ASCETV6.4.10. The SWC contains a module with several messages:
The messages are mapped as follows:
The Convert to NV-Data Mapping menu option is called, the mappings of messages to NVData interface elements are converted. The process is 
logged in the ASCET monitor window.
### INFORMATION: Conversion of External Message Mapping for NV-Data Interface elements started.
### WARNING: No Conversion done for Message msg_sendRec because it is already mapped in Internal Mapping to a IRV.
### INFORMATION: Converted Message msg_l_enum (exported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_c (exported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_c (imported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_u (exported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_u (imported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_i (exported) to non-volatile Variable.
### INFORMATION: Converted Message msg_rec_i (imported) to non-volatile Variable.
### INFORMATION: New NV-Data mapping: msg_l_enum - NVData.l_enum
### INFORMATION: New NV-Data mapping: msg_rec_c - NVData.rec_c
### INFORMATION: New NV-Data mapping: msg_rec_u - NVData.rec_u
### INFORMATION: New NV-Data mapping: msg_rec_i - NVData.rec_i
### INFORMATION: Conversion of External Message Mapping for NV-Data Interface elements ended.
After the conversion, the module looks as follows:
The content of the Internal Access tab of the Message Mapping view is unchanged.
The External Access tab contains only the mappings of messages to SenderReceiver interface elements.
The converted mappings are shown in the NV-Data Mapping view.
The original messages msg_rec_c, msg_rec_i, and msg_rec_u were imported. Therefore, the exported counterparts in the project are converted to NV variables, too.
See also
NV Data Mapping
Accessing Non-Volatile Variables
Message Mapping