Symptom: The slave MPU cannot be registered after the CF card on the slave MPU is replaced.
%%01SRM/4/Reset(l): Slot17 will be reset, the reason is:The slave version is different from the master.
%%01SRM/4/Verdiff(l): Slave MPU 17 version V100R005C02B01B is different from the master
%%01PAT/3/PATOPER(l): Patch operation error
,the information is: reply slave get patch state message failed, get file information err..
1. Check the versions of the master and the slave MPUs. It is found that the version of the files loaded through BootROM to the slave MPU is consistent with the version of the files on the master MPU.
2. Run the dir command to check the patch status file on the CF card of the master MPU. The command output shows that the file patchnpstate.dat does not exist. Copy patchnpstate.dat from another ME60 to the tested device and restart the slave MPU. Then, the slave MPU is successfully registered.
1. The versions of the master and slave MPUs are inconsistent.
2. Patch information cannot be synchronized from the master MPU to the slave MPU.
During the registration of the slave MPU, the system automatically reads patchnpstate.dat on the master MPU, and synchronizes the file together with patch files to the slave MPU. If there is patchnpstate.dat on the master MPU, the system prompts that the registration fails because the versions of the master and slave MPUs are inconsistent.
Note that you can copy patchnpstate.dat from another ME60 to the tested ME60 only when the configurations of the files on the two ME60s are completely consistent, that is, both the types and the slot numbers of the master MPUs on the two ME60s are consistent.