1.1 Test Types

ProCalV5 allows for the addition of different “Test Types” to the database that may be applied to any item master record whose required calibration does not fit perfectly into the typical ProCal template.   Test Types may be used to provide specific testing in addition to or instead of a standard calibration with target set points and as found/as left readings.  Examples of some calibration Test Types that ProCalV5 normally could not accommodate efficiently are Extreme Values, Linearity and Standard Deviation tests.


1.1.1 Set Up Test Type Packages Screen

The Set Up Test Type Packages screen (shown in Figure 1) is used to add, modify and if necessary delete test type packages from the database.  This screen is invoked by selecting the “Set Up Test Type Packages…” option on the File menu when the System Options and Defaults screen is open.



                                                                                                                            Figure 1



1.1.2 Adding New Test Types

To add a new test type to your database you must first copy the required library file “StopWatch_TimerTest.bpl” into the folder labeled “bin” under the ProCalV5 directory (typically “C:\Program Files\Prime Technologies\ProCalV5\bin”) in Windows Explorer.  The “StopWatch_TimerTest.bpl” file contains all the information necessary for the test type’s automatic and proper setup in ProCal.  Once the file has been copied into the correct folder you may launch the Set Up Test Type Packages screen.   Once the screen is open you may click the Add New Record button or select “New Record” from the screen’s File menu.  This will invoke a browser screen titled Choose New Package File that automatically directs you to the “bin” folder in which all the “.bpl” files reside. Select the required file “StopWatch_TimerTest.bpl” and click the Open button or double-click the file name.


Once the correct file has been selected you will be returned to the new test type record which will already be set up for you.   In this instance you can save the record, making it available for application to all types of item master records in the system (i.e. Instruments, Loops, Systems, Test Instruments, in addition to any PM records that may require a calibration).  Once a test type has been saved to the database, as long as it is marked as “Active”, it will be available for selection on the Test Type field’s drop-down list on the Calibration Points tab in all screens where that tab exists.  


Although you will have no ability to change the test type’s calibration requirements, you do have the ability to make some customizations to it in terms of field label changes and also giving users the ability to edit target setpoints and such when entering calibrations using that test type.  Please reference section 8 of the user manual for information on modifying test type packages once they have been imported into the database.


1.1.3 Distributing Test Types

Test Types only need to be installed in the System Option and Defaults screen once, but for all Client, Administrator, or Mobile Workstations, the “StopWatch_TimerTest.bpl” file must be present in the “bin” directory one level down from the ProCalV5 installation directory.


1.1.4 Entering Item Records Using The Stopwatch Timer Test Test Type Package

When creating a new master record that uses the Stopwatch Timer Test Test Type, the test type must be applied to the record through the Calibration Points tab on the master record screen.  Once a new group has been added to the record, click the Test Type drop-down list and select Stopwatch Timer Test from the available test types, as shown in Figure 2:


                                                                                                                               Figure 2                                                                                                                                     


Once the test type has been selected, the inputs will change according to the settings defined by the library file. This new Test Type Package for ProCalV5 will be available to the user to capture and calculate time measurements to be compared with a target time on a Calibration record.  During Calibration entry, the limits are calculated automatically. The master record interface is shown in Figure 3.


                                                                                                                                                                                                                                                                   Figure 3


On the main screen, the resolution can be set for the “UUT Resolution” (Unit Under Test) and the “Standard Resolution”. Each can be set to a maximum of eight (8) decimal places. (100 millionth of a second) The test type inputs used in this test should be entered through the Show Group Options box, which can be accessed by clicking the Show Group Options button on the right side of the screen. This interface is shown in Figure 3.1 on next page.


The Test inputs are as follows:


The inputs appear for configuration on master record items, and some variables can be edited for entry on the calibration screen during calibration entry.

  • CTL in Seconds – Calibration Tolerance Limit: This describes the standard limit of passing or failing each section of the test. A measurement or calculation is considered to be failed if it is outside of this limit.
  • Capacity – This setting is for information purpose only. No warnings or restrictions will be generated if this capacity is exceeded.
  • Minimum Test Period – This setting is for information purpose only. No warnings or restrictions will be generated if a reading is below the minimum setting.
  • PCTL in Seconds – Process Calibration Tolerance Limit: This tolerance is similar to Control Limits. Refer to the ‘Calibration Codes’ section in this Manual for more information.


Note – It is recommended to set your ‘Standard Resolution’ to a value that reflects your settings for the CTL & PCTL values. [Example – Standard Resolution = 0.0001, CTL = 0.0005, PCTL = 0.0009]

                                                                                                                                    Figure 3.1





1.1.5 Entering Calibration Records For Items That Use The Stopwatch Timer Test Test Type

Once the calibration points have been created for a master record that uses the Stopwatch Timer Test Test Type, the calibration data can be entered on the Test Results tab. The Calibration screen is shown in Figure 4 below. 


                                                                                                                          Figure 4


Data for the test points can be entered by clicking the View/ Enter Data button on the left side of the screen. This interface is shown in Figure 5


All values will be converted to a seconds total. In the example below, 11 hours is converted to 39,600 seconds, 20 minutes is converted to 1,200 seconds plus 45 seconds for a total of 40,845 seconds. All values (except ‘+ Days’) must be entered in the time format “HH:MM:SS” and the software will not convert values such as 80 seconds. This value would have to be entered as follows: 00:01:20. The maximum value for MM & SS is 59.


Figure 5


1.1.6 As Found and As Left Values

The Stopwatch / Timer Verification screen allows you to enter either only As Found or As Found and As Left. If the “As Left Entered” checkbox is not checked, the As Found values and As Left values will be the same. If you need to record separate As Left values, checking the “As Left Entered” check box will allow for data entry for As Left values



The form also contains 2 buttons:


  • Apply – Sets all outputs on the calibration record. (Note this does not save the data to the database.  Hitting the “Save” button on the calibration is required for this)
  • Close – Closes the input form.  If there have been modifications the user will be prompted if they want to “Apply” before closing.


1.1.7 Calibration Codes


A = all tests: As Found and As Left passed

            B = any As Found failure (out of CTL), all As Left tests passed

            C = any As Found failure (out of PCTL), all As Left tests passed

            D = any As Found failure (out of CTL) + any As Left failure (out of CTL)