You can move an .mer or an .apa file between computers. The .mer is the compiled file that the PVP uses to run the application, the .apa is the archived file that you use to save project files between PC's. So yes, an .apa is arguably what is "intended" to be used to move files between PC's, but you can just as easily use an .mer. You just have to select "restore runtime application" instead of "restore application" when loading the project back into FTView Studio.The .mer file that I have, I uploaded from the HMI a couple of months back and in between my mother board died. I lost it all. I had the .mer file on our network but my understanding is that you can't move from computer to computer unless it is an .apa.
Correct. v6.0 should be able to restore your v5.1 .mer or .apa file, and will convert it to v6. Then, you have the option to create your new .mer file as a v5.1 file.I just used the landing zone software. It's showing the project was created for FT View Studio ME 5.1. I'm thinking I should be okay with version 6.0.
I did see the revision last week. Someone suggested that I right click on the panel and explore the revision. It was around 3.??. I'm hesitant to flash forward though because we just bought the machine and the builder is being very protective of information. I.E. the wont give us the PLC program ????, we had to ask for the levels of logins for the HMI (and he still didn't give us all of them). If something happened to the machine and we had to have them work on it for whatever reason, I get the impression that they wouldn't appreciate the upgrade.
Is it typical to program a PVP1250 with a 32bit computer at level 5.1 if you're a builder? Am I crazy to think it's time for them to spend some money on hardware and software?