Importing Legacy PanelView Projects Into FactoryTalk View Studio

TAS_Banner_PVP_A



Import PV to PVP FiRockwell's FactoryTalk View Studio HMI/SCADA development software comes with the built-in ability to import old PanelView Projects. In today's article, I'll walk you through the steps to do just that.


Importing legacy PanelView Projects into FactoryTalk View Studio

Step 1) Start by opening FactoryTalk View Studio Machine Edition. When prompted with the below “New/Open” window, choose the “New” tab:

PV to PVPlus Import 1

Step 2) On the “New” tab, give your project a name (no spaces, under 28 characters,) but don't click on “Create:”

PV to PVPlus Import 2






Step 3) Next, click on the “Import” button

PV to PVPlus Import 2b

Step 4) Press “OK” after reading the notice:

PV to PVPlus Import 3

Step 5) Select the type of legacy PanelView project you would like to import and press next:

Note: PanelBuilder 1200 projects must first be imported to PanelBuilder 1400e (enhanced) software and saved as a “.PVC”

PV to PVPlus Import 4

Note: PanelBuilder Enhanced and pre-6.1 PanelView Plus projects can not be imported on Windows 7 64 bit without first preforming a lagecy tag database export on a 32bit OS. See this blog post for more information:

http://www.theautomationblog.com/how-to-migrate-factorytalk-view-projects-to-windows-7-64-bit/

Step 6) Browse for your legacy PanelView file, select it, and press “Next:”

PV to PVPlus Import 5

Note: In this example we will import a PanelView 1000 RIO Demo Project:

PV to PVPlus Import 5b

Step 7) Select your import options and then press “Finish:”

PV to PVPlus Import 6

Step 8) Once the import finishes, you will be prompted with a popup displaying the conversion results. All errors in this log will need to be considered before deploying your imported code:

PV to PVPlus Import 7

Step 9) Now you have completed the importing of your legacy PanelView project into FactoryTalk ViewStudio:

PV to PVPlus Import 8

Note: For more information about migrating old PanelView projects to FactoryTalk View check out the below migration guides:


I hope the above step-by-step procedure on how to import legacy PanelView projects into FactoryTalk ViewStudio was helpful. If you have any comment. questions, suggestions, or corrections please don't hesitate to share them by using the “post a comment or question” link below.

Sincerely,

Shawn Tierney
Automation Blogger and Trainer
If you enjoyed my article, you may like my affordable courses at TheAutomationSchool.com




Comments:
  1. Hi, i am trying to import Pannell view file.PVA to factory talk view studio but at the end it gives me the error that The PanelView builder export utility not installed, please help me on this, i have properly followed the instructions and every things goes well but when i start finish at the end the said error jumps up, need your kind assistance please

    Thanks
    Please Help me: I'm battling with HMI migration.

    How can I Change tag address to a full word address on Factory Talk as recommended by migration pdf guide. Below is the error:
    ( Tag es temp: Bit Array tags are not supported. Tag will be converted as a memory tag. )

    Also, how do I correct this error: ( Screen 2 Main: Message display object will be converted to Multistate Indicator object at (224, 88). )
    Good morning IdealDan,

    What version of FactoryTalk View Studio are you using? Also, what is the part number of the existing PanelView and new PanelView Plus?

    There are some easy ways to work around the Bit Array tags, and some versions of FTView which accidentally give warnings like this but import the tags without issue.

    But it all depends on your versions, etc.

    Background info here:

    https://rockwellautomation.custhelp....ail/a_id/27284
    https://rockwellautomation.custhelp....ail/a_id/24126

    If you check out the Message Display Object in PanelBuilder, and the new Multistate Indication in ViewStudio, you'll see they should display the same message based on the tag value, and if they do there's nothing to fix.

    Sincerely,

    Shawn Tierney
    The Automation Blog

4 Old Comments:

  1. Hi Shawn Tierney, I am trying to convert Panelbuilder 32 project to ME Studio but while I am doing that -at the end of the process- there is an error appears on the screen. It calls“ImportErr.log“ and also it writes:

    Cause: An invalid character was found in text content.
    Line number : 1 Character position: 1131

    Can you help me about this problem, what should I do?

    Thanks for help

  2. Good morning Merih,

    This is a very rare error, but if I remember correctly it means there is an unsupported text character somewhere in your PanelView Builder 32 project.

    I suggest saving a copy of your PB32 project with a different name and then looking through the project text list in PB32 to see if your project contains any non-alpha numeric characters.

    If my memory is correct, eliminating those should allow you to import the project.

    Hope this helps,

    Shawn Tierney

    If you enjoyed reading my article you may also like my affordable training courses at TheAutomationSchool.com

  3. Good morning Shawn,

    First of all I appreciate your interest. I will try your suggest, I am so new at this topic so excuse my ignorance but can you tell me how i reach to project text list that you implied.

    I opened the project in Panel Builder 32 with a diffrent name and there is a section folder on the left side called “System“ and under this section there is a “text editor“. When I open that “Message Text“ section appears on the screen. Are you talking about this ?

    Thanks for help

    Merih

  4. Merih,

    Yes, under system – text editor you should see all the text in the project. Look for odd characters like $ or &.

    I honestly can’t remember what character caused me issues years ago, but it was not one of the normal A-Z, 1-9 alpha numeric characters.

    Hope this helps,

    Shawn Tierney

    If you enjoyed reading my article you may also like my affordable training courses at TheAutomationSchool.com

Comments are closed.