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.
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:
Step 1: Open your imported PanelView project in FactoryTalk View Studio and double click on RSLinx Enterprise Communications Setup:
Step 2: When prompted, choose “Create a new configuration:”
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.
Step 4: Open the “HMI Tag Database” and select a device tag as shown below:
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.”
Step 6: Close the HMI Tag Database and return to RSLinx Enterprise. Now click on the “Add” shortcut button:
Step 7: Name your new shortcut “PVRIO”
Step 8: Now select the Runtime (Target) tab. In this tab, right click on “RSLinx Enterprise” and select “Add Driver”
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.
NOTE: For a complete list of PanelView Plus models which are still available and support RIO check out the below article:
Step 10: Change the “Baud Rate” to match your RIO network speed, and leave “Jumper ID” at zero.
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”
Step 12: Right click on “RIO” and select “Import”
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:
Step 14: Once done, you should see something like the below configuration. Press “Save” and “OK.”
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.”
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.
- 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