PanelBuilder to FactoryTalk RIO Conversion Remote I/O PanelView to PanelView Plus Conversion
Remote I/O PV to PVP Conversion Agenda Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean Up and Implementation
Remote I/O PV to PVP Conversion Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean up and Implementation
Remote I/O PV to PVP Conversion Importing Project into Studio Close and Save the PBA or PVA Open up FactoryTalk View Studio Enter Name of Application Select the Import Button
Remote I/O PV to PVP Conversion Importing Project into Studio Specify the file to import Select PVA or PBA Click Next to continue
Remote I/O PV to PVP Conversion Importing Project into Studio You can select Use existing window size Convert to new window size Click Finish to Continue
Remote I/O PV to PVP Conversion Review Conversion Log Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean Up and Implementation
Remote I/O PV to PVP Conversion Review Conversion Log View the conversion log at the end of the conversion
Remote I/O PV to PVP Conversion Review Conversion Log Conversion log can also be found at : C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI projects\The Name of your project
Remote I/O PV to PVP Conversion Import Communication XML / Setup Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean Up and Implementation
Remote I/O PV to PVP Conversion Import Communication XML / Setup Open the RSLinx Enterprise and Select Communication Setup Expand the Communication setup window to full view Select Design Local Tab Add the Shortcut called PVRIO PVRIO may or may not be present Right click RSLinx Enterprise Icon to add RIO Driver There are two selections 2711P-RN6 or 2711P-RN1 PVP 400/600 use 2711P-RN1 PVP 700-1500 use 2711P-RN6
Remote I/O PV to PVP Conversion Import Communication XML / Setup On The Design Local tab Expand the Remote I/O, RIO Driver and select the RIOdata Right click RIO data and select the Configure RIO Verify that the RIO Module is the correct Scanner type Right click the module and select properties Import the Communication xml file from the HMI Project Right click the module and select Import
Remote I/O PV to PVP Conversion Import Communication XML / Setup After archiving the project, only the Runtime Target tab will be saved with the project. If current RIO project is closed and a new Machine Edition project is created, the Design local configuration could be lost. The configuration on The Runtime Target tab can be copied to the Design Local.
Remote I/O PV to PVP Conversion Import Communication XML / Setup Some of the common problems during import are block transfer size The block size, group, and slot number may need to be adjusted to support the PanelView Plus
Remote I/O PV to PVP Conversion Import Communication XML / Setup After the import there were two problems that were discovered in the blocktransfer. The alias tags used in BT1 did not have adequate word spacing to accommodate for 32bit word length of floating Point files. The group and slot number were missing from BT2.
Remote I/O PV to PVP Conversion Import Communication XML / Setup Alias tags will need to be created for tags that use data type bit array and floats.
Remote I/O PV to PVP Conversion Import Communication XML / Setup The PanelBuilder block transfer starts at F160:10, the Speed1tag will use F160:11. After the conversion, the alias tags takes on word 1 of the block transfer.
Remote I/O PV to PVP Conversion Import Communication XML / Setup The import does not compensate for the 32-bit word size of floating point files. The imported file sets the files in consecutive order. The programmer must manually adjust each alias tag for two-word offset.
Remote I/O PV to PVP Conversion Object and Screen Adjustment Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean Up and Implementation
Remote I/O PV to PVP Conversion Object and Screen Adjustment When using existing window size selection, PanelView 600 Standard screens Will covert to 320x234 custom size in ME.
Remote I/O PV to PVP Conversion Object and Screen Adjustment For better results, adjust the screen size after the project has been imported. The screen on the right shows the PanelBuilder screen and the screen on the right shows the converted FactoryTalk View screen.
Remote I/O PV to PVP Conversion Clean Up and Implementation Importing Project into Studio Review Conversion Log Import Communication XML / Setup Object and Screen Adjustment Clean Up and Implementation
Remote I/O PV to PVP Conversion Clean Up and Implementation Once all the screens have ben adjusted and the communications are set, the project is ready to be compiled and downloaded. Remember it is important to select the Replace Communications in the Transfer Utility. Once the download is complete the 2711P-RN6 module should have a solid green LED light showing that communications has been established
Remote I/O PV to PVP Conversion Conversion Tips Changing alarm trigger (Choose edit to replace trigger tag) When possible, choose direct or alias vs HMI tags Relationship between B1 5 of ME to N19:5 of the PLC (Cross Reference)
Remote I/O PV to PVP Conversion Related Answers Reference the standard PanelView Application migration documents below: Migrating PanelView Standard Applications How to copy the Target Tab configuration to the Local Tab https://rockwellautomation.custhelp.com/app/answers/detail/a_id/29204 PanelView Plus Remote I/O program examples using block transfers https://rockwellautomation.custhelp.com/app/answers/detail/a_id/26611 Tips on maximizing block transfer performance for PV+ over RIO https://rockwellautomation.custhelp.com/app/answers/detail/a_id/28888 1756-DHRIO with Remote IO and Block Transfers https://rockwellautomation.custhelp.com/app/answers/detail/a_id/21762