Over the years I've been asked a lot about how to migrate old RSView32 systems to FactoryTalk View SE, and in today's article I'll list my five top tips.
Five Things You Need To Know About Migrating RSView32 To FactoryTalk View
1) FactoryTalk View Site Edition and RSView32 are licensed differently
To migrate an RSView32 system, you'll need a copy of FactoryView Studio Enterprise as well as a Station (runtime) license, or one Server and (at least) one Client license.
FactoryTalk View SE is also sold by Graphic Display count, not tag count. This change was made because View SE can directly reference PLC tags and device registers, which eliminates the need to create a tag database.
For more information on how RSView32 and View SE licenses differ, follow the below link to our article on the subject:
2) Rockwell offers a “Step Forward” discount – no support contract required
If you'll no longer need your RSView32 license after migrating, ask your local Rockwell representative to quote you the “Step Forward” price from the RSView32 you have to the View SE you would like to replace it with.
This discount, which does not require your old RSView32 license to be in support, is usually substantial and well worth your time to investigate.
3) FactoryTalk View Studio Enterprise Edition can directly import RSView32 projects.
At RSTechED 2013 I was shocked to learn some Rockwell representatives were not aware that View Studio could import RSView32 projects.
Ok, I've have been using RSView and RSView Studio since both their betas, so I may have a slight advantage.
But still, View Studio has been out for over ten years, so I would expect anyone who actually uses FactoryTalk View SE would know it can import old RSView32 projects (as well as View ME projects.)
4) SPC, Messenger and Recipe Pro Extensions do not import
FactoryTalk View does do a lot of things we always wished RSView32 would, but unfortunately it doesn't do everything RSView32 did.
Case in point: The RSView32 Extensions SPC, Messenger, and Recipe Pro.
These free add-on extensions for RSView32 have no counterparts in View SE, so if you use any of those heavily you'll want to do additional research before attempting to migrate.
5) VBA needs to be re-written
I've always directed my clients to use VBA sparingly, only when the equivalent feature or function was not already included in FactoryTalk View itself.
That said, most all RSView32 VBA code can be modified to work in ViewSE, however two things must be kept in mind:
First, View SE's VBA is client based, running in the client window from the graphic displays.
This is quite different from RSView32's VBA which was server based, much like Events and Derived Tags.
Second, View SE has a very different “Object Model” than RSView32.
This means the code for accessing Tags and other components needs to be changed, and in ViewSE it can often be simpler read a value from a display's object than access a tag directly.
And if you have any questions, comments, or suggestions, please feel free to share them with us by submitting the “post a comment or question” link below.
Sponsor and Advertise: Get your product or service in front of our 75K followers while also supporting independent automation journalism by sponsoring or advertising with us! Learn more in our Media Guide here, or contact us using this form.