Advant Controller 410/450 - Command GVD can corrupt the MVI data base
Problem:Solution
A description of this resolution:
"Advant Controller 410/450 - Command GVD can corrupt the MVI data base" resolves the following:
A description of this resolution:
- The error will corrected in the next main revision of the Advant Controller 400 Series *1.2
Workaround:
Avoid using the command GVD in data base elements MVI2 - MVI5. If the damage is done, it can be corrected by taking one of the following measures:
1. If you see something wrong in the data base element, set IMPL=0 for the corresponding submodule, CI532Vxx, identify and correct the errors (command MDB) with the engineering station and then set IMPL=1.
2. If you have errors in MVIx that can not be corrected with MDB in operational mode you can do ECONFIG and delete the erroneous data base element with the command DDB MVIx. Then create the same data base element again. To be on the safe side it is advisable to set POSITION and SUBPOSITION to 0,0 before using DDB. Finally use the command DICONFIG.
[ref SR6070 VASMASOITA0798 ]
"Advant Controller 410/450 - Command GVD can corrupt the MVI data base" resolves the following:
- Advant Controller 410/450 - Command GVD can corrupt the MVI data base
When command GVD, given from the engineering station, is used in a database element with item designation MVI2 - MVI5 (call name CI532) some data base contents can be corrupt.
If the command GVD is used in the S2 or S3 part in one of the data base elements MVI2 - MVI5 data can be destroyed in this element. It is not possible to describe the corrupt data since it will differ depending on which of the data base elements that is accessed and also from time to time in the same data base element.
NOTE: The data base element with item designation MVI1 is not affected. The command GVD can be used without any problem.
Product concerned
Advant Controller 410 *1.2/0
Advant Controller 450 *1.2/0
Software concerned
QC01-BAS11*8.0/0
QC01-BAS21*8.0/0
- Article imported from the previous version of KnowledgeBank
Answers
Cause: Article was imported from the previous version of KnowledgeBank Resolution:
Add new comment