800xa Migration- 2.1 to 5.1
We are upgrading a system from 800xA 2.1 to 800xA 5.1, for which the path we are following is 2.1->4.1-> 5.1.
While we upgraded from 2.1 to 4.1 we are facing couple of issues, have listed them as below,
1. The aspects (Alarm List, Event List) appear twice in 4.1 system because of inheretance property in the system. Please refer attached screenshots for details.
2. Another issue is after upgrading one of the project does not open in control builder. The control builder will crash after creating dump files. see attched log and dump files for reference. Note that the Upgrade has completed without any errors.
Can anyone help us regarding this.
Thanks & Regards,
Voted best answer
I did such an upgrade last year, and I went from 2.1 -> 5.0 -> 5.0 with SPx -> 5.1.
The reason was that I had lost of errors importing in 4.1 and it was trouble free importing in 5.0. It was a little more work with the 5.0 path as you need to load service packs twice but having no errors on import saved lots of time.
As per document the path Shoul be be following:
- Step1 : Preapre a system with 5.0 SP2REvE and perform the restore 2.1. refer Section 4 of 3BSE036342R5001
- Step 2 : Preapre a system with 5.1 RevD and carry out the restore from 5.0 system
- Optional Step: Update to 5.1 FP4RevD
In later versions of the REUSE alarm lists are probably inherited from a super type. The faceplate's aspect link will only open one of them, so which one to keep and which one to get rid of is not a problematic choice.
Please contact the vendor of the REUSE library for an upgrade description.
The CBM crash should be reported to your regional ABB support center.
Did you perform NLS Correction and Consistency Checks in all intermediate stages of the upgrade? These two are hinted in the E144 System Health Check workshop - see if you can find a copy of an SHC user's guide (or contact me and I will send you the most recent one).
Its recommended to solve a problem as early as possible in the upgrade process. In version 2, NLS problems were common. Also consistency errors that later versions of 800xA can find/repair.