storing config files

Discuss issues and ideas you have to configuring displays with PowerVision
verschuren
Posts: 79
Joined: Wed Oct 28, 2015 8:40 am

storing config files

Post by verschuren » Tue Feb 23, 2016 2:27 pm

Hi,

We are wondering what the best approach is of storing config files. We have finished our new configuration with PowerVision 2.8.10366 and we are not sure how to handle it the best and we want to be sure this will work in the future as well.

There are several storing options I have in mind:

1) .murphyConfig
2) .murphyConfig & update.tar.gz
3) .murphyConfig & update-full.tar.gz

We are wondering if we store a update.tar.gz file and use it again in the future, it will gives issues with a display that has a newer OS for example. One way to avoid it to use the .murphyConfig only and create a new package (update.tar.gz) when needed. Or maybe it's better to use a full installation package (update-full.tar.gz)?

Maybe somebody can give me some insight on how to deal with this? Thanks!
Mario Verschuren
Controls Integration
stalley
Enovation Controls Development
Enovation Controls Development
Posts: 618
Joined: Tue Mar 18, 2014 12:57 pm

Re: storing config files

Post by stalley » Thu Feb 25, 2016 7:44 am

Hello verschuren,

For production purposes and field updates, you will want to use the update-full.tar.gz. This file contains the applications that are compatible with the configuration, in addition to the configuration. Whatever part number you are ordering from Enovation Controls, as time goes on, it will be possible that the applications shipped will not be compatible with the configuration if your production uses the just the configuration file, update.tar.gz.

That is my wisdom for you today. ;-)
Sara Talley
Software Engineer
Enovation Controls
verschuren
Posts: 79
Joined: Wed Oct 28, 2015 8:40 am

Re: storing config files

Post by verschuren » Thu Feb 25, 2016 7:46 am

Thank you for your wisdom of the day!
Mario Verschuren
Controls Integration