Release Notes/Installation

From RadiWiki
Revision as of 09:01, 3 November 2015 by Dikr (talk | contribs) (→‎Installation)
Jump to navigation Jump to search

Installation[edit]

Backup[edit]

Before you install the latest version of RadiMation®, please make sure to saveguard all your critical data.

Make a back up of (at least) the following files:

  • Correction files
  • TSF files
  • Sequence files
  • Device driver configuration files

Multi version installation[edit]

Since the release of RadiMation® version 4.3.67 it has become possible to run different RadiMation® versions (4.3.67 and higher) on the same PC.

This functionality can be used to verify the correct functioning of the software before it is used for EMC testing. Simply put, the functioning of the new version can be checked by comparing it with the older version. This verification can for example be required by internal quality assurance standards. During this verification process, the installation of the older RadiMation® version can still be used for all EMC tests.


Be advised that:

  • It is not possible to run two (or more) different versions at the same time without risking a software crash. Close RadiMation® before starting another version!
  • DARE!! Instruments cannot be held accountable if information is lost because two different versions of RadiMation® are used at the same time.
  • The user needs to have the rights as described in User rights and installation.

Installation[edit]

Installing software updates[edit]

Software updates can be distributed on CD or downloaded from the RadiMation® Download page.

To install the RadiMation® update from a CD, please execute the ‘SETUP.EXE’ startup program. The setup program will install the new RadiMation® version at the same location as the previous version, but in a separate installation folder. This will allow you to use the previously installed RadiMation® version, as well as the new one.

The setup program will detect that a previous version of RadiMation® has already been installed on your PC. A back up of this older version will automatically be copied to the backup directory. All the settings of the older version will also be used for the newly installed RadiMation®. If any problems should occur with the new software, the older version can be recovered.

Installing from a network directory[edit]

If the already installed RadiMation® version was installed from a network directory, the new setup file can be copied to the <Setup> sub-directory of the <NetworkDir>.

The new RadiMation® version can then be installed on each computer from this directory.

Updating device drivers[edit]

After the new RadiMation® version is installed, we strongly recommend that you install the latest device drivers as well. These device drivers can be installed by starting the ‘DRIVERS.EXE’ program that is located on the delivered CD.

The ‘DRIVERS.EXE’ program will detect the different RadiMation® versions installed on your PC. A dialog will start, asking you to select the RadiMation® version that needs updated device drivers. Select the latest version of RadiMation® that was just installed.

You have successfully obtained the latest released version of RadiMation® when both the software and device drivers have been updated.

Verification[edit]

Every new RadiMation® version is tested extensively before it is released. DARE!! validates these new versions on three ‘levels’. The fourth level of the validation is to be done by the end-user.

This quality management system follows the ISO/IEC 17025 standard (“General requirements for the competence of testing and calibration laboratories”).

Automatic knob pushing program[edit]

The ‘automatic knob pushing program’ simulates an end-user and is run on each RadiMation® version. The program performs all the actions that a user could do, such as entering information, executing tests, reviewing test results and generating reports.

Performing the first validation level is a responsibility of DARE!! Instruments.

Validation and usage in a test lab[edit]

Ones the new RadiMation® version has passed the first validation level, it progresses to the second validation level performed by DARE!! Instruments.

This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.

If the new software version passes the first stage, it progresses to the second stage where it is installed and used in the DARE!! Instruments test laboratory. Any issues that are reported during use are investigated. An updated version of RadiMation® is created if needed.

Performing the second validation level is a responsibility of DARE!! Instruments.

Validation and usage in a test house[edit]

Ones the new RadiMation® version has passed the second validation level, it progresses to the third validation level performed by DARE!! Measurements.

This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.

If the new software version passes the first stage, it progresses to the second stage where it is installed and used by DARE!! Measurements. Any issues that are reported during use are investigated. An updated version of RadiMation® is created if needed.

Performing the third validation level is a responsibility of DARE!! Instruments.

Validation by end-users[edit]

Ones the new RadiMation® version has passed the third validation level, it progresses to the fourth (and last) validation level performed by the end-users.

When end-users receives a new RadiMation® version they should perform a validation of the software. The parts that should be validated by the end-user are:

  • Correct control of the used equipment
  • Validation of the software according to internal quality standards
  • Possible verification and comparison of measurements on a 'known' EUT

Performing the fourth validation level is a responsibility of the end-user.