PGR software and firmware version numbering scheme / standards.
All PGR software and firmware follow a standardized version-naming scheme that allows users to quickly and easily determine the latest software versions. All software and firmware version numbers consist of 4 numbers separated by periods e.g. firmware version 22.214.171.124. This follows the general pattern of:
where Type of Release is always ‘0’ for an Alpha version, ‘1’ for Beta, ‘2’ for Release Candidate, and ‘3’ for Release. All future firmware and software versions posted on our download site will follow this scheme. To determine the latest version of a particular family of software, look first at Major Revision, then Minor Revision and finally Build Number. The Build Number does not increase indefinitely, but instead resets after each increase of either the Minor or Major Revision Number.
Version 126.96.36.199 is a later version than 188.8.131.52, and is also Beta class software. However, version 184.108.40.206 is a later version than 220.127.116.11, as this product has undergone a minor revision.
Version 18.104.22.168 is a later version than 22.214.171.124, even though it is Alpha class software.
Software that meets the PGR Alpha standard is not required to satisfy a large percentage of the full software release process. This classification has been instituted for quick bug fixes and new functionality. As such, a user of an Alpha release has very few guarantees outside from the software version number being correct. As a general rule, Alpha releases will not be made public. Upon request, they can and will be emailed to knowledgeable users.
The requirements for a piece of software to meet the Beta standard are substantially stricter than those of the Alpha standard. A release that meets the Beta requirements will be functionally complete. It will have been tested internally and by Alpha users, source code documentation will be complete and memory leaks and other similar problems will be solved. These releases will be made public. They will be posted to the web pages in a category separate from Release Candidates and Releases. Again, software that meets the Beta standard is designed for knowledgeable users.
The only difference between software that meets the Release Candidate standard and software that meets the Release standard will be the amount of testing and the delivery mechanism. Release Candidates will be fully supported and posted to the web pages but not burned to CDs - they will be designed for use by new users.
Software will only meet the Release standard when it is burned to CD and shipped with new camera systems. Similar to Release Candidate users, users of Release software can expect fully functional libraries, examples and installation scripts.
1.) Upgrading Digiclops firmware
2.) Determining the firmware version used by a PGR camera.
3.) Using Windows Device Manager to determine PGR software and driver versions.
4.) Performing a clean installation of PGR camera software and drivers.
5.) Should I upgrade my camera firmware or software?
|4/30/2012 3:23:42 PM