Best Practices - Version Control

To keep track of what version is loaded on a display some form of version control is necessary in both the file naming convention and in the config itself.

There are a few methods to accomplish this as described herein.

Download the Example created in 2.9.23044 for a PV780

Simple Method

Use the "title" entry to record the revision  of the configuration (ex. Rev 1.2.3.4) and perhaps a short marketing name of the project. Display this on the screen using a text widget with and override string assigned to the System Manager string "Version.ConfigTool.Title" which will automatically be updated with the contents of the title entry block.

Use the "Identifier" entry block to name the project. This should remain unchanged throughout any version changes. This is used for your reference only.

Additional Revision Information

If greater detail is needed the following System Manager Strings are available for display

• Version.ConfigTool.CreationTime - this will display the time stamp with the date and time of when the Firmware was created.
• Version.ConfigTool.FileName - this will display the .murphyconfig file name this was created from. This can be displayed in a systems menu or other out of the way location. It is important to include revision or date information in the file name so a configuration can always be traced back to the correct source file.
• Version.ConfigTool.Version - this will display the version of Powervision the Firmware was created with.

The System Manager has additional numeric variables that can be displayed for further granularity of the versions of OS, App, Loader, and Config. All of these will be populated by the current version of Powervision in use with the exception of the Config variables. These must be manually hardcoded each time a new revision is created.