Remote I/O PanelView to PanelView Plus Communications Configuration Migration

The Automation School - HMI Basics - Article Banner

When importing a PanelView RIO project, there's one crucial step you don't want to miss!

Over the years I've received many calls from clients struggling with the conversion of Remote I/O (RIO) PanelViews.

RIO PV to PV Plus Comms Import FiMost found it easy enough to import their old PanelView projects into FactoryTalk View Studio. But when came to setting up the communications, many ran into a dead end.

At first glance, it would seem that the manufacturer had left the task of recreating the RIO configuration to the user.

But while the conversion process doesn't recreate the RSLinx Enterprise configuration for you, it does create a configuration file you can import into RSLinx Enterprise.

Unfortunately, the manufacturer gives the user no indication that this import file is being created. This leaves many attempting to recreate from scratch what they could easily import.

With that in mind, today I'll show you the simple steps to take to import your PanelView RIO communications configuration into FactoryTalk ViewStudio and RSLinx Enterprise.





Importing a PanelView RIO configuration into RSLinx Enterprise

Prep: First you need to import your legacy PanelView project into View Studio. For step-by-step instructions on how to do this see the below article:

http://www.theautomationblog.com/importing-legacy-panelview-projects-into-factorytalk-view-studio

Step 1: Open your imported PanelView project in FactoryTalk View Studio and double click on RSLinx Enterprise Communications Setup:

RIO PV to PV Plus Comms Import 1

Step 2: When prompted, choose “Create a new configuration:”

RIO PV to PV Plus Comms Import 2

Step 3: When RSLinx Enterprise opens, you'll notice that no “shortcuts” exist. Before we create a shortcut we must first verify that name of the shortcut the import utility assigned to our imported tags.

RIO PV to PV Plus Comms Import 3

Step 4: Open the “HMI Tag Database” and select a device tag as shown below:

RIO PV to PV Plus Comms Import 4

Step 5: Review the address field for your device tag. You should find all the imported PanelView RIO tags have been assigned a shortcut name of “PVRIO.”

RIO PV to PV Plus Comms Import 4b

Step 6: Close the HMI Tag Database and return to RSLinx Enterprise. Now click on the “Add” shortcut button:

RIO PV to PV Plus Comms Import 5

Step 7: Name your new shortcut “PVRIO”

RIO PV to PV Plus Comms Import 5c

Step 8: Now select the Runtime (Target) tab. In this tab, right click on “RSLinx Enterprise” and select “Add Driver”

RIO PV to PV Plus Comms Import 6

Step 9: Select the Remote I/O hardware for your system. The most common RIO option is the 2711P-RN6 used with legacy PanelView Plus models.

RIO PV to PV Plus Comms Import 7

NOTE: For a complete list of PanelView Plus models which are still available and support RIO check out the below article:

http://www.theautomationblog.com/panelview-plus-with-remote-io-support/

Step 10: Change the “Baud Rate” to match your RIO network speed, and leave “Jumper ID” at zero.

RIO PV to PV Plus Comms Import 8

Step 11: Expand the new “Remote I/O, RIO” entry by clicking on the plus sign. Then right click on “RIOdata” and select “Configure RIO”

RIO PV to PV Plus Comms Import 9

Step 12: Right click on “RIO” and select “Import”

RIO PV to PV Plus Comms Import 10

Step 13: Browse to the “HMI Projects” folder, and then to the folder of your imported PanelView project. In this folder you will find a “PV Rio.XML” file which was created when you initially imported your PanelView RIO project into ViewStudio. Select this file and press open:

RIO PV to PV Plus Comms Import 11

Step 14: Once done, you should see something like the below configuration. Press “Save” and “OK.”

RIO PV to PV Plus Comms Import 12

Step 15: The last step is to assign your “PVRIO” shortcut to “RIOdata.” You do this by selecting the “PVRIO” shortcut, then “RIOdata,” and then by pressing “Apply,” and “OK.”

RIO PV to PV Plus Comms Import 13

Note: For more information about migrating old PanelView projects to FactoryTalk View, please reference the below migration guides (as of the publication of this blog these guides have not been updated with information about Bit Array support discussed in this article:)


I hope the above step-by-step procedure on how to import legacy PanelView RIO Communication Configurations into FactoryTalk ViewStudio and RSLinx Enterprise 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


The Automation School - HMI Basics - Article Banner

Comments:
  1. Thanks for your clear explanation! In fact I found a similar but smaller description in the FT View ME User Manual (v8.10).
    But what I miss is how I can connect a RIO configuration to an external RIO-Ethernet/IP gateway using RSLinx Enterprise?
    A little explanation of my situation: I have to migrate several legacy PanelViews (Standard and 1400e) to PanelView Plus 7. These have to communicate to PLC5's on RIO interface. To do this the AN-X2 RIO-Ethernet/IP gateway of Prosoft is proposed.
    For some conversions this works pretty quick, just configure the right BTW and BTR in the gateway and the communication works fine. The gateway is added in RSLinx Enterprise under "Ethernet" as "NetENI-connected PCCC devices" and then choose the right one from the PLC-5 Family Processors.
    But now I have some old applications that use RIO addresses in the tagdatabase, that seem to be linked to Block Transfers. The address notation of a tag is not like the PLC5 notation (i.e. N20:5 or N20:5/2), but such as "B01 20/00-20/15". These notations of adresses are similar to the aliases in the RIO configuration in RSLinx Enterprise.
    What I can't find is how the "NetENI-connected PCCC devices" relates to the RIO configuration? I think those have to be linked somehow to get the communication running.
    On both the Rockwell Automation Knowledgebase and the Prosoft Knowledgebase I can't find how this works in practice...
    Do you know a solution to this? I hope my description is sufficient, if not I'm happy to explain it in more detail.
    Good morning ,
    If you see addresses like To find out what RGS that B01 is assigned to (so you can look in your PLC program to see what data table addresses correspond to the BT instruction for B01's RGS) you have to open the PV project in PanelBuilder. It's looks slightly different if you're using PanelBuilder for the original 1200 models versus PanelBuilder E for the 1400E models.
    As I don't have the software loaded at the moment I can't direct you to the exact location in PanelBuilder, but I think you'll find it quickly looking under comms or RIO where you should find a Block Transfer button or listing.
    Hope this helps,
    Shawn Tierney, TheAutomationBlog.com

2 Old Comments:

  1. Thank for your effort,
    Recently I am working on migration from PV1400 to PV+1250.
    Is there any chance we can try the run time using rs emulate?

  2. Good morning Bin,

    If you were doing DH+ this would be possible, but I do not believe Emulate 5 will emulate RIO.

    So, one option would be to borrow a PLC-5 from your local Rockwell representative.

    Thanks,

    Shawn Tierney

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

  3. Morning…it’s 5:17 am here now
    another question…
    Currently the existing PV1400 using RIO, a new one will have a choice between DH+ or RIO. I would like to choose DH+, but then I am sure I have to do lot of changing in PLC5 program ( I have done once with ethernet).

    In my case, I don’t want to do a changing in PLC5 since it will take more times and beside I don’t have a good backup file with description on it.

    My question, if I choose RIO and following the steps you explain above, Is there any changing in PLC5 tobe done?(related to tag/address)

    thank you

  4. Good morning Bin,

    There is a very good chance that you will not have to edit the PLC-5 code.

    When you import the old PanelView project into ViewStudio you will get an import error report which will detail features that were not converted – if you can address all those errors in ViewStudio then the PLC-5 code will need no edits.

    PS – You’ll need a PVPlus 5.1 to use remote I/O. The newer PVPlus 6 and 7 don’t support it. More info here:

    http://www.theautomationblog.com/panelview-plus-with-remote-io-support/

    Hope this helps,

    Shawn Tierney

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

  5. Hello !

    Please help me . I want to connect Panelview Plus 1250 to PLC compactlogix L35E by DF1 . When I add driver in Communication setup (FTV Studio) i don’t see PLC compactlogix . In there has PLC 5, SLC and Logix Platform . So this job can do it ?

    Thanks for your help.

  6. Good afternoon mindon2k8,

    Here’s what I do which works everytime.

    1) in RSLinx Enterprise, under the Target/Runtime tab, right click and add Serial DF1 Point to Point driver

    2) Only change Baud rate, Error checking, parity, and stop bits to match L35E

    3) Do not change type or check autoconfigure

    4) Right click on serial DF1 driver and add L35E via serial DF1 and apply your shortcut to this L35E.

    This is all you should need to – please let me know how you make out,

    Shawn Tierney

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

  7. Hi Shawn Tierney .

    The first i want to say thank you so much .
    Follow your guide . I have do it . I have a same question . If change Compaclogix by PLC5 then the system can work ??
    PLC5 is type PLC 5/60

    I hope recieve your answer .

  8. Good morning mindon2k8,

    I believe you’re asking if you can connect your PVPlus 1250 to the serial port of a PLC-5?

    If that is your question, the answer is yes. In place of adding the L35E in RSLinx Enterprise, you would add the PLC-5, but keep in mind the tag addresses are different.

    Note: In the below video I show how to import PLC-5 tags:

    http://www.theautomationminute.com/flashback-episode-7-factorytalk-view-importing-plc-5-slc-500-tags/

    Hope this helps,

    Shawn Tierney

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

  9. it’s 23:21 now….
    i am following your tutorial….
    i should test them tomorrow, i hope it works.
    one question, should i click “copy from design to runtime” when i finish doing “device shortcut”?(step 15)

    thanks

  10. Good morning Bin,

    Because we have no way to test the RIO setup on our PC, I don’t bother setting up the Local/Design tab in RSLinx Enterprise.

    That said, because all the setup we’ve done is in the Target/Runtime tab, we would not want to erase that by copying the empty Local/Design config.

    The only time I would press the “copy from design to runtime” is when we set everything up in the Local/Design tab and want to duplicate that in the Target/Runtime tab.

    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.