A valued client has engaged us to rebuild and upgrade four machines, each equipped with a Compact Logix PLC and a PanelView Plus HMI. Last year, we successfully completed the upgrades on two of these machines, which involved updating the firmware on the HMIs to support the .mer files generated by Factory Talk Studio version 8.2. Recently, we received the next two machines; however, when attempting to upgrade the firmware on the PanelView units, we discovered that the firmware only supports version 6 of the PV Plus units. Unfortunately, both of these units are version 5. Is there a solution to modify the PanelView units so we can download the .mer file from Factory Talk Studio version 8.2? Additionally, I have an older installation CD for Factory Talk version 5.1. Will the license associated with Factory Talk Studio version 8.2 work for this installation? If needed, I can provide the specific part numbers for the PanelView units as well as the version details from Factory Talk Studio.
Steve Bailey mentioned, "I can provide the specific part numbers for the PanelView units along with the version details from FactoryTalk Studio if needed." Expanding on this would certainly be beneficial, Steve. Additionally, it's important to know the current firmware revision of the terminals (typically found on the factory label). It's worth noting that FactoryTalk Studio version 8.20 is capable of creating runtimes as low as version 5.0, so terminals with firmware version 5.0 should function appropriately.
The most effective approach to creating runtime files for older firmware terminals is to utilize FTView Studio ME. When setting up the Runtime, simply select an option from the drop-down menu that allows you to revert to version 3.2. As long as your applications do not include ActiveX components or features exclusive to the Operating System and firmware of PV+6 and later, the Runtime should operate seamlessly on older terminals without issues. I encountered a similar challenge with a batch of machines; initially, we deployed eight units with PV+ version 5.10 terminals, and later added four more when the PV+6 became available. We had to manage the project meticulously, as we relied on several ActiveX controls. Itâs important to note that "downgrading" FTView ME Studio is not an option, and I strongly advise against performing upgrades on the same machine. The best practice is to conduct fresh installations on virtual machines (VMs) to better manage FTView processes.
FTV Studio version 8.20 has the capability to generate Runtimes as low as 5.0. Recently, I decided to review my FTView Studio ME installation. The last project I worked on was designed for a PV+7 Standard model, which only permits the creation of runtimes for versions 8.20, 8.10, and 8.0. However, when I initiated a new project and selected the hardware as "PV+700-1500," I discovered that the runtime options expanded significantly, allowing me to create Runtimes as low as 5.0. It seems that, likely after the release of FTView Studio ME version 7.0, support for earlier versions 3.x and 4.x was discontinued. This highlights the importance of using the latest software versions for optimal performance and compatibility with hardware. If youâre working on projects involving FTView Studio and FTView ME, be sure to check hardware compatibility and supported runtime versions to avoid any potential issues.
The current project files for the machines we worked on last year pertain to a PV + 6 configuration. Is it possible to revert these files to their previous version? Alternatively, will we need to retrieve the runtime data from this year's machines' HMI and replicate the enhancements we implemented in last year's machines?
Steve Bailey inquired: "Can the project files from last year's machines, which are compatible with PV + 6, be saved as an earlier version?" To clarify, yes! If the HMI terminals for the machines being upgraded this year are equipped with firmware version 5.0, then FactoryTalk View Studio ME v8.20 can generate terminal Runtime (.mer) files (version 5.0) that will be compatible with the terminals used this year. Steve Bailey further asked: "Will we need to extract the runtime data from the HMI of this year's machines and replicate the modifications made to last year's models?" This is indeed a viable option; however, it will entail a significantly longer conversion process. By utilizing appropriate phrases like âFactoryTalk View Studio,â âHMI terminals,â and âruntime extraction,â this text aims to enhance visibility for search engines while preserving the original message.
â Work Order Management
â Asset Tracking
â Preventive Maintenance
â Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Unfortunately, PanelView Plus version 5 units cannot be upgraded to support .mer files generated by Factory Talk Studio version 8.2. These units are limited by their firmware capabilities, which only support up to version 6 of the PanelView Plus firmware. You may need to consider upgrading the hardware to a compatible version.
Answer: - A potential workaround is to recreate the application in an older version of Factory Talk Studio that is compatible with the PanelView Plus version 5 firmware. This may involve significant effort, especially if the application uses features exclusive to version 8.2.
Answer: - Typically, Rockwell Automation licenses are backward compatible, meaning that a license for a newer version (such as 8.2) should work with older versions like 5.1. However, it's always a good idea to confirm this with Rockwell Automation support or consult
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.