I tried to open a PV350 standard configuration downloaded from this forum with my PowerVision 2.7, but it did not open because the file was made with Ver.2.6 beta and needs to be updated to the non-beta version. Please let me know how to do it.

Thanks,

Dai Uematsu

Hi!

You need to get a later version of the 2.6 PowerVision, you will find the installer here. Use this to "import", open and save the config.

You should then be able to again "import", open and save the config using your 2.7 version of PowerVision.

I encourage you to use the 2.7 patch 1 release of PowerVision, if you have not done that yet. You will find it on this forum under the Software and Documentation near where you found the 2.6 patch 3 release.

Hello,

Thank you very much for your instruction. I confirmed that my PowerVisions 2.6 and 2.7 are the latest ones. I imported the sample standard configuration PV350 from this forum, open and save it on the 2.6 first. Then, I copied the configuration from the DB of 2.6 and put it in the DB of 2.7. Is that a correct process?

Thanks,

Dai

Hi Dai Uematsu,

Copying the .murphyConfig file will not convert the configuration to a new or updated version of the PowerVision Configuration Studio. The Import button lets you search for a configuration.

The important part is that you use the Import MurphyConfig file button, found at the bottom of the Open a device configuration window. Do this the first time you open the configuration using an updated version of the PowerVision Configuration Studio. After you do the Import, you will see a file in your \db folder, for example, MSTD (PV350) 2.6.20202 - Imported. This is the configuration that has been updated to the 2.6 or 2.7.

So, in your latest version of PowerVision 2.6, you Import the configuration, then open the * - Imported configuration, then save it.
In PowerVision 2.7, you Import the configuration you saved with the 2.6, open the * - Imported configuration, then save it.
This last saved version of your configuration should have all of the beta version features updated properly. There may be some minor things that you will need to edit individually, but it shouldn't be very much.

Without the Import... process, some features that have changed will not work in the new version of the PowerVision.