® DPC/TRACK ™ Software Users Manual PN 602599 November 1996 Rev.2, 4/98 © 1996, 1997, 1998 Fluke Corporation, All rights reserved. Printed in U.S.A. All product names are trademarks of their respective companies.
Table of Contents Chapter Title Page 1 Overview............................................................................................. Introduction...................................................................................................... Conventions ..................................................................................................... The Fundamentals............................................................................................
DPC/TRACK Users Manual Creating Records......................................................................................... Deleting Records......................................................................................... Changing Data................................................................................................. With Respect to Tag IDs and Serial Numbers................................................. About the Interface......................................................
Contents (continued) Testing with Calibrators................................................................................... Unloading .................................................................................................... Loading........................................................................................................ Testers Input .................................................................................................... As-Found and As-Left Tests...................
DPC/TRACK Users Manual Editing Procedures ...................................................................................... Editing a Procedure for a Specific Tag ID.............................................. Editing a Procedure for All Tag IDs....................................................... Other Procedure Fields ............................................................................... Field Types.........................................................................................
List of Tables Table Title Page 1-1. 1-2. 3-1. 8-1. 8-2. Simple Test Results Database...................................................................... Terminology ................................................................................................ Data Order ................................................................................................... Importable Tag ID Database Fields.............................................................
DPC/TRACK Users Manual vi
List of Figures Figure Title Page 2-1. B-1. B-2. B-3. DPC/TRACK Main Menu........................................................................... Connecting the Calibrator ........................................................................... 743 Calibrator.............................................................................................. Test Setup ....................................................................................................
DPC/TRACK Users Manual viii
Chapter 1 Overview Contents Introduction ............................................................................................... Conventions............................................................................................... The Fundamentals ..................................................................................... Databases, Records, Fields, and Forms................................................. Terminology.................................................................
DPC/TRACK Users Manual 1-2
Overview Introduction 1 Introduction Dependable instrument maintenance ensures the quality of your product as well as the well-being of the process and those who maintain it. With the advent of database requirements by ISO, OSHA, EPA, FDA, and other regulatory agencies, the collection and validity of instrumentation data is even more critical than before. As-Found and As-Left tests, multiple instrument types, test scheduling, data analysis... You need more than just a database. You need DPC/TRACK.
DPC/TRACK Users Manual Conventions The conventions used in this manual are: • Bold text indicates a button title, a screen or dialog box title, a keystroke, a field name, a form name, a page name, or a tab name. • Italic text is used within notes. Italics are also used for emphasis to help convey a concept. • CAPITAL letters are used for directory names and file names. • Actions requiring a combination of multiple keys are indicated with a + symbol; e.g.
Overview The Fundamentals 1 Table 1-1. Simple Test Results Database Tag ID TT-100 TT-200 PT-101 Test Date 12-1-94 12-7-94 8-4-93 Final Status Passed Passed Failed Tester Bob Elizabeth Hank Comments The valve... I noticed... It follows then that a record is a collection of fields related through some common element, such as the Tag ID field. This common element is referred to as the primary field.
DPC/TRACK Users Manual Terminology Certain terminology is used throughout DPC/TRACK to describe different elements of the program. These common terms are informally defined below: Table 1-2. Terminology Term 1-6 Description Arrayed Field An arrayed field tracks multiple entries (elements) relative to the specific field type. An example of an arrayed field is the Testpoints field in the Tag ID database.
Overview The Fundamentals 1 Table 1-2. Terminology (continued) Term Description Page A page is the area that displays fields relative to a particular tab on a form. Primary Field The primary field is the key field that uniquely identifies each record within a given database. Record A record is a collection of fields that are related through the primary field.
DPC/TRACK Users Manual In a Nutshell DPC/TRACK is comprised of four distinct yet related databases. They are: Tag ID The Tag ID database contains information pertaining to a device in your plant, such as the Tag ID, Serial Number, and Manufacturer. Each Tag ID record may be associated with multiple Test Results records. This way, you may compile a testing history for each and every instrument in your plant.
Overview Tag ID Breakdown 1 Tag ID Breakdown A Tag ID represents a functional specification and location of a device within a process. The designated Tag ID for a device often contains this information (its function and location), following standard Instrument Society of America (ISA) instrument identification designations. Consider the Tag ID value of PT-100. Per ISA, the first letter represents the process variable of the Tag ID, which in this case is “P” for “Pressure”.
DPC/TRACK Users Manual Requirements Successful installation and operation of DPC/TRACK requires the following software and hardware. • IBM® compatible 486- based computer (586 or higher recommended) • 8MB RAM required (16MB or more recommended) • Microsoft® Windows™ Version 3.1 or later (or Windows 95) • MS-Windows compatible pointing device • MS-DOS® Version 5.
Overview Installation 1 Installation 1. If a demo version of DPC/TRACK is already installed on your system and you are reinstalling the software, you must delete the DPCTRACK.INI file in the Windows directory where DPC/TRACK is installed, and all additional files in that directory. 2. If a previous version of DPC/TRACK is installed on your system, and you are installing the new version, you must delete the DPCTRACK.INI file in the Windows directory.
DPC/TRACK Users Manual Note If a message appears stating that there is not enough disk space, select the Cancel button to abort installation, delete enough files to free up at least 20 MB of disk space, and start over. 4. As the installation progresses, you will be asked to insert the remaining disks. All languages share the same remaining disks. The status bar dynamically indicates the installation progress of the entire installation procedure. You can now start your DPC/TRACK program.
Overview Installation 1 (Select the OK button to activate your command.
DPC/TRACK Users Manual Pentium Floating Point Correction DPC/TRACK is carefully designed to provide you with complete and accurate information. Since some of this information involves numeric calculations, and since DPC/TRACK performs these calculations quickly by making use of your computer's floating point processor, it unfortunately is affected by the Pentium floating point calculation problem.
Overview Getting Support 1 Getting Support To access technical support for DPC/TRACK, contact your local Fluke representative How to Contact Fluke To reach Fluke by mail, use either address below: Fluke Corporation PO Box 9090 Everett, WA 98206-9090 USA Fluke Europe B.V. PO Box 1186 5602 B.D.
DPC/TRACK Users Manual 1-16
Chapter 2 DPC/TRACK Essentials Contents Introduction ............................................................................................... Starting the Program.................................................................................. Logging In................................................................................................. Security ..................................................................................................... The Main Menu..........................
DPC/TRACK Users Manual 2-2
DPC/TRACK Essentials Introduction 2 Introduction This chapter is broken down into the following sections: • Starting the Program • The Main Menu • Tutorial: Learning the Basics • About the Interface Starting the Program To start DPC/TRACK, double-click on the DPC/TRACK icon located in the DPC/TRACK Group. (Multiple instances of DPC/TRACK may not be run concurrently on the same machine.) Logging In Upon starting DPC/TRACK, you will receive a login screen (after viewing the About DPC/TRACK screen).
DPC/TRACK Users Manual Tester The access rights of the Tester are further restricted than those of the Key User in that existing data may not be deleted or edited (for the most part). However, Testers may load and unload calibrators for the purpose of generating Test Results records. The User ID and default password for the Tester is Tester. Visitor The access rights of the Visitor are further restricted than those of the Tester in that data may not be added, deleted, or edited in any way.
DPC/TRACK Essentials Security 2 Admin • Search for records within all databases • Interpret data • Perform calibrator communications and diagnostics • Create and exclude records, and change data within the test results database • Create records and change comments within the tag id, test equipment, and procedure databases • Import and export data • Delete records within the test equipment and tag id databases • Perform system maintenance tasks, such as backing up data, rebuilding indexes, p
DPC/TRACK Users Manual The Main Menu All of DPC/TRACK’s features may be accessed via the Main Menu (Figure 2-1). (The Main Menu serves as the primary reference point for all examples within this manual.) Depending upon your security rights (based on your User ID) not all of the buttons shown in Figure 2-1 may be accessible. The tutorial presented later in this chapter addresses all basic aspects of this screen. Additional information may be found in subsequent chapters. ED001S.BMP Figure 2-1.
DPC/TRACK Essentials Main Menu Buttons 2 Main Menu Buttons This section provides basic information about the various buttons that appear on the Main Menu. As appropriate, reference is made to the specific chapters and examples that address the tasks with which each object is associated. Schedule Upon selecting this button, the Scheduler screen appears, from which you may search for overdue, due, and untested Tag IDs based on a date range. Chapter 5, “Testing,” discusses the Scheduler screen in detail.
DPC/TRACK Users Manual Import/Export Clicking on this button accesses DPC/TRACK’s Import/Export facilities. See Chapter 8, “Importing & Exporting.” Exit Upon selecting the Exit button, the DPC/TRACK program is terminated and you will be returned to Windows’ Program Manager. Login Clicking on the Login button accesses the Login screen. Help Upon selecting the Help button, the DPC/TRACK on-line help system presents itself. The help system is an electronic representation of this manual.
DPC/TRACK Essentials Searching for Records 2 with the examples presented here. (See Chapter 6, “Creating & Deleting,” for instructions.) Searching for Records DPC/TRACK includes a Quick Search tool that enables you to locate records matching specific criteria. (For more information on searching, see Chapter 3, “Searching for Records.”) Example 2.1: Searching If you’re looking for specific data, then you’ll probably want to use DPC/TRACK’s Quick Search tool.
DPC/TRACK Users Manual Example 2.2: Sorting Suppose you wish to change the order in which the records are displayed. The following examples will demonstrate a few different sorting steps so that you can obtain an understanding of how the data can be sorted. 1. To sort the records according to the Area field, perform the following: a. In the Instument View screen, select the Sort... button. b. On the Instrument Sort page, click in the Area field.
DPC/TRACK Essentials Interpreting Data 2 before taking any action. Somewhere in the middle is a safe and efficient environment for both your personnel and your process. Drift Plots help you find this middle ground. Per device, a Drift Plot illustrates the maximum As-Found deviation relative to the test dates for all associated Test Results records.
DPC/TRACK Users Manual Printing Reports Friday, 4:30 p.m. Your supervisor needs that weekly Test Results report by 5:00 p.m. No need to panic—here’s a sampling of the reports at your fingertips: • Calibration Cert • Test History • Instrument Detail • Last Test Done • Test Equipment • Pass / Fail List • Pass / Fail by Category • Reverse Traceability Here’s what you do: 1. Select the Reports button on the Main Menu to access the Report Selection screen. 2. Choose the desired report. 3.
DPC/TRACK Essentials Creating & Deleting Records 2 Creating & Deleting Records Creating Records Adding records to your Tag ID database is simple. We’ll also take a look at creating Test Results records in Examples 2.4 and 2.5. See also Chapter 6, “Creating & Deleting.” The procedure for adding records via import is discussed in Chapter 8, “Importing & Exporting.” Example 2.4: Creating a Tag ID Record Note Key User or Admin security rights are required in order to work through this example.
DPC/TRACK Users Manual Note Two records cannot be created with the same serial number. However, two or more Tag Ids can be imported with identical serial numbers (see Chapter 8 for importing information.). Example 2.5: Creating a Test Results Record (Using a Calibrator) Note Tester, Key User, or Admin security rights are required in order to work through this example. Test Results records are automatically created when information is unloaded from a calibrator.
DPC/TRACK Essentials Creating & Deleting Records 2 7. Assuming the calibrator is attached to the appropriate serial port and ready to communicate, select the Load button on the Calibrator Manager screen. Depending upon DPC/TRACK’s setup options, you may be given the chance of printing a report during the loading process. If results were found on the calibrator, they will be unloaded before your load occurs.
DPC/TRACK Users Manual Example 2.6: Creating a Test Results Record (Manually) Note Tester, Key User, or Admin security rights are required in order to work through this example. Manual tests are sometimes necessary for devices that cannot be tested using a calibrator. DPC/TRACK recognizes this need and allows test data to be directly entered for such devices. In this example, we walk through the steps necessary to enter the results of a manual analog test for SAMPLETAG5.
DPC/TRACK Essentials Creating & Deleting Records 2 9. Choose the Select... button to access the Test Equipment Manufacturer and Test Equipment Serial Number suggestion lists. We will use these lists to choose from our existing Test Equipment records. (We could also select the New... button to add a new Test Equipment record.) Select “Fluke” from the Test Equipment Manufacturer field. In so doing, our list of Test Equipment Serial Number values will now pertain to Fluke Test Equipment records only.
DPC/TRACK Users Manual Example 2.7: Deleting a Tag ID Record In this example, we’ll learn how to delete a record by using the Tag ID record we created in Example 2.3 (MYTAGID1). 1. Select the Tags/Instruments button on the Main Menu to access the Instrument Search screen. 2. Enter “MYTAGID1” in the Tag ID field. 3. Select the Search button. The Instrument View screen for MYTAGID1 appears. 4. Select the Change... button. 5. Ensure that “MYTAGID1” is entered in the Tag ID field and click on the Delete...
DPC/TRACK Essentials Changing Data 2 Example 2.8: Editing Data in Fields Note Key User or Admin security rights are required in order to work through this example. In this example, we’re going to change data within a few fields for the SAMPLETAG8 sample Tag ID record. The purpose of this example is to introduce you to a few of the nuances related to Pick fields. DPC/TRACK also includes Number, Date, and Text fields. Further information may be found in Chapter 7, “Changing Data.
DPC/TRACK Users Manual 11. We won’t edit any more data for right now. We just wanted to illustrate some of the nuances you may experience when editing data. Select the Main Menu button to return to the Main Menu. To edit data within most of the fields within your databases, simply click within the field box, and type in the value of your choice. There are, of course, a few special exceptions to this, which we leave to Chapter 7, “Changing Data.
DPC/TRACK Essentials With Respect to Tag IDs and Serial Numbers 2 Example 2.10: Renaming a Serial Number Note Key User or Admin security rights are required in order to work through this example. Let’s say that for one reason or another we must replace a device in our plant. In this example, we will be installing a new device (Serial Number) into the same location (Tag ID) from which we removed the old device.
DPC/TRACK Users Manual About the Interface Main Menu Note As do all Windows-based applications, DPC/TRACK competes against other concurrently running programs for system resources. When system resources are low, you may notice a decrease in program speed. Also, you may notice some cosmetic difficulties in displaying buttons on the Main Menu. For best results, we recommend limiting the number of concurrent applications when running DPC/TRACK.
Chapter 3 Searching for Records Contents Introduction ............................................................................................... Quick Search ............................................................................................. Searching for Procedures ...................................................................... Related Concepts .................................................................................. Wildcard Searching ......................................
DPC/TRACK Users Manual 3-2
Searching for Records Introduction 3 Introduction This chapter contains the following sections: • Quick Search • Wildcard Searching • Search Operators & Field Types • Data Order The examples in this chapter incorporate the sample records included with DPC/TRACK. For information on creating sample records see Chapter 6, “Creating & Deleting.” Quick Search DPC/TRACK’s Quick Search tool enables you to quickly find records based on combinations of even the most detailed search criteria.
DPC/TRACK Users Manual Example 3.1: Searching for Test Results In this example, we will search the Test Results database for all 702 Analog tests that failed between 6/15/95 and 11/19/95. 1. Click on the Results button on the Main Menu. The History Record Search form appears. 2. On the History page, select “702 Analog” from the Record Type Pick list. 3. Enter “6/15/95” in the Test Date Start field. To specify the “on or after” portion of our date criteria, select the >= radio button. 4.
Searching for Records Quick Search 3 Example 3.2: Searching for an Instrument Let’s say we need to find all instruments whose Function value is “Transmitter” and whose Due Date is later than 3/15/96. (This example employs the sample records that came with DPC/TRACK. It is assumed that the sample records are in their original state. You may ensure that your sample records are in their original state by rebuilding them, as described in Chapter 6, “Creating & Deleting.”) 1.
DPC/TRACK Users Manual Example 3.3: Searching for Test Equipment Let’s search through our Test Equipment database for those records pertaining to Fluke calibrators. 1. Select the Test Equipment button on the Main Menu to access the Test Equipment screen. 2. Type “Flu” (excluding the quotes) within the Manufacturer field. Note that the Approx operator is selected by default.
Searching for Records Quick Search 3 From this point, you may • Click on the Select button to incorporate the currently viewed Procedure into the Test Procedure page of the Tag ID record(s) that resulted from your Quick Search. • Rename or edit a Procedure. (For information on renaming and editing Procedure records, see Chapter 7, “Changing Data”.) • Use the New... button to create a new Procedure record. (For information on creating new Procedure records, see Chapter 6, “Creating & Deleting”.
DPC/TRACK Users Manual Related Concepts 3-8 • If you specify criteria within a field on a Quick Search screen, then wish to “undo” that criteria, simply click in the field and perform a Ctrl+Bksp key combination twice in a row. This process returns the first field to its original (gray) state. • By performing a Ctrl+Bksp key combination once after clicking within a field, the “C:Clear” field status message will appear.
Searching for Records Wildcard Searching 3 Wildcard Searching A wildcard search employs symbols that essentially act as placeholders for criteria when you either don’t know or don’t care about some element of your search criteria. Wildcard searches may be applied within any Quick Search screen for any Text field, so long as the Approx operator is used.
DPC/TRACK Users Manual Search Operators & Field Types This section provides information on data comparison operators (used in Quick Searches) and how they relate to field types. The first subsection relates to nonarrayed fields; the second subsection relates to arrayed fields. Finally, a list of characters and their corresponding relative “orders” is presented. (Further information on the field types may be found in Chapter 7, “Changing Data.
Searching for Records Wildcard Searching 3 Date For all operators except Approx, search criteria and field data are compared as dates on a time line. The display format is ignored. Blank data is less than any Date value. For Approx, search criteria and field data are compared by the rule “is the field data within +2 weeks of the search criteria?” Pick For all operators, search criteria and field data are compared in the order they appear within the list.
DPC/TRACK Users Manual Arrayed Fields As discussed earlier, arrayed fields contain multiple values. Listed below are the different arrayed field types and the rules that govern operators within those arrayed field types. Text For all operators except Approx, each of the specified field data elements must meet the search criteria when compared against each of the search criteria elements.
Searching for Records Wildcard Searching 3 Number For all operators except Approx, each of the specified field data elements must meet the search criteria when compared against each of the search criteria elements (by numerical value). The first field data element must meet the search criteria when compared against the first element of the search criteria, the second field data element must meet the search criteria when compared against the second element of the search criteria, etc.
DPC/TRACK Users Manual There is no Approx feature for Pick fields. The Approx is treated as an equals operator (=). (Within DPC/TRACK, arrayed Pick fields typically appear as a collection of checkboxes.) Data Order Table 3-1 lists different characters and their corresponding order within DPC/TRACK with regard to searching and sorting. (The blank entry following C:Clear represents blank data, such as multiple Spacebar entries.
Searching for Records Data Order 3 Table 3-1. Data Order Order Data Order Data Order Data undef. V: Bad Value 27 8 53 R undef. C:Clear 28 9 54 S 29 : 55 T 3 4 ! 30 ; 56 U 5 “ 31 < 57 V 6 # 32 = 58 W 7 $ 33 > 59 X 8 % 34 ? 60 Y 9 & 35 @ 61 Z 10 ‘ 36 A 62 [ 11 ( 37 B 63 \ 12 ) 38 C 64 ] 13 * 39 D 65 ^ 14 + 40 E 66 _ 15 , 41 F 67 ` 16 - 42 G 68 { 17 .
DPC/TRACK Users Manual 3-16
Chapter 4 Graphs & Reports Contents Introduction ............................................................................................... Generating Graphs..................................................................................... Printing Reports ........................................................................................ Calibration Cert..................................................................................... Test Detail...........................................
DPC/TRACK Users Manual 4-2
Graphs & Reports Introduction 4 Introduction This chapter includes the following sections: • Generating Graphs • Printing Reports • Printing Records • Calibration Sheets Obviously, having the information is important. But it is your ability to efficiently organize and effectively present your information that really counts—regulatory and plant strategy directives depend on it. To this end, DPC/TRACK provides a number of customized graphs and reports.
DPC/TRACK Users Manual Example 4.1: Generating a Graph Let’s say we need a quick graph of the test that was performed on SAMPLETAG2 on 11/18/95. 1. Select the Results button on the Main Menu to display the History Record Search screen. 2. On the History page, type “11/18/95” (excluding the quotes) in the Test Date Start field. 3. Select the = operator, then select the Search button. The Instrument History screen is displayed. 4. Click on the Results tab. 5.
Graphs & Reports Printing Reports 4 Printing Reports The otherwise complex and time-consuming task of report generation is made easy with DPC/TRACK. The following reports are available to you: • Calibration Cert • Test Detail • Instrument Detail • Last Test Done • Test Equipment • Pass / Fail List • Pass / Fail by Category • Reverse Traceability • Scheduler The procedure for generating a report is simple. Here’s what you do (except for the Scheduler report): 1.
DPC/TRACK Users Manual Calibration Cert This report provides documented proof that your instrumentation is calibrated. For Tag ID records meeting your criteria, test information for the last (most recent in time) Test Results record (whose Final Status is “Passed”) is printed. Note that the last Test Results record must reference the corresponding Tag ID and Serial Number values. Each printed report is assigned a unique certification reference number.
Graphs & Reports Printing Reports 4 Reverse Traceability This report enables you to quickly locate and print out all Test Results records that employed certain pieces of Test Equipment. You may specify whatever criteria you like with respect to Test Equipment. Also, you may limit the report to only include Test Results records that were entered during a certain date range. See Example 4.2. Scheduler You may generate a Scheduler report via the Test Scheduler.
DPC/TRACK Users Manual Example 4.3: Pass / Fail by Category Follow these steps to generate a Pass / Fail by Category report: 1. Select the Reports button on the Main Menu to access the Report Selection screen. 2. Select the Pass / Fail by Category... button to access a Quick Search screen. 3. Specify the search criteria of your choice and select the Search button. 4. Select the OK button in response to the system message in order to continue. 5. Click on the field by which you wish to categorize your data.
Chapter 5 Testing Contents Introduction ............................................................................................... Test Scheduling ......................................................................................... Scheduled Testing................................................................................. Unscheduled Testing............................................................................. The Test Scheduler .....................................................
DPC/TRACK Users Manual 5-2
Testing Introduction 5 Introduction This chapter discusses the following topics: • Test Scheduling • The Calibrator Manager • Setup vs. Test Procedure • Testing with Calibrators • As-Found and As-Left Tests • Switch testing vs. Instrument Testing • Manual Testing • Tag ID vs. SN History • Troubleshooting Test Scheduling Scheduled Testing With respect to device testing, scheduled maintenance falls into two general categories: preventative and predictive.
DPC/TRACK Users Manual As other tests are done for this device, the results will be saved and sorted according to their test dates, with the most recent test appearing first, followed by the next most recent test as you scroll through the Test Results records. The Due Date field will be updated automatically (if the test passed) by adding the testing interval to the Test Date of the most recent test.
Testing Test Scheduling 5 The Test Scheduler The Test Scheduler provides a means for you to quickly categorize your devices according to their respective Due Date values. The Test Scheduler may be accessed two different ways: via the Schedule button on the Main Menu, and via the Test Scheduler... button in the Calibrator Manager screen. Let’s take a look. Example 5.1: The Test Scheduler In this example, we will determine the scheduling status of the sample records that came with DPC/TRACK.
DPC/TRACK Users Manual The other buttons on the Scheduler screen are: Mark Selecting the Mark button selects (marks) the Mark for Load field for the corresponding records. (See Example 5.3.) Add to List Selecting the Add to List button adds the corresponding records to the Load List on the Calibrator Manager screen. (See Example 5.2.) Clear all marks in database The Clear all marks in database button unmarks all records in the database, not just those referenced on the Scheduler screen.
Testing Test Scheduling 5 The “Mark for Load” Concept On the Instrument View page of the Instrument View screen there is a Mark for Load checkbox within the Scheduling information. Selecting this checkbox designates the given Tag ID record as one to be loaded to the calibrator. You may then easily review your marked Tag ID records via the Calibrator Manager screen before actually doing a load.
DPC/TRACK Users Manual The Calibrator Manager The Calibrator Manager screen may be accessed via the Load/Unload button on the Main Menu. Before you load a calibrator, you must specify what it is you wish to load. This information (the Tag ID) needs to be entered into the Load List field. There are a few ways to go about doing this. One way is to simply enter the Tag ID into the array as you would enter data into any other array.
Testing The Calibrator Manager • 5 If the Load List contains Tag IDs for different calibrators (based on the Test Type field), then when a load is attempted, DPC/TRACK will load the appropriate Tag IDs on the attached calibrator. Only those Tag IDs within the Load List that match your selection will then be loaded. (This interaction helps alleviate potential communication errors.) There’s a lot of information to digest here.
DPC/TRACK Users Manual Example 5.3: Calibrator Manager, Test Scheduler, Mark for Load This example employs the Test Scheduler tool and the Mark for Load field together with the Calibrator Manager screen. It is assumed that the sample records have not been altered. (You may ensure this by rebuilding the sample records as described in Chapter 6, “Creating & Deleting.”) 1. Select the Load/Unload button on the Main Menu to access the Calibrator Manager screen. 2.
Testing Setup vs Test Procedure 5 Setup vs Test Procedure So far, we’ve discussed the Test Scheduler tool, the “Mark for Load” concept, and the Calibrator Manager screen. We’ve shown how these elements work together to address your scheduling and calibrator management needs. Before moving on with the fundamentals of loading and unloading, it is appropriate to discuss the nuances of setting up your testing information. (Obviously, you must properly define your test before you can do it.
DPC/TRACK Users Manual Also notice on the Test Procedure page that there is a Procedure... button. When you select this button, a Quick Search screen is presented whereby you may specify search criteria. After specifying your search criteria, select the Search button to display all Procedure records matching your search criteria. Records are displayed via the Procedure Selection screen.
Testing Testing with Calibrators 5 Testing with Calibrators “Loading” is the process of transferring test information for one or more devices from DPC/TRACK to the calibrator. The loading of test information for a device is sometimes referred to as loading records, loading test parameters, or loading Tag IDs, etc. “Unloading” is the process of transferring test results from the calibrator back to DPC/TRACK.
DPC/TRACK Users Manual If you like, you may select the View... button to take a look at your new Test Results record. After selecting the Done button, you may be given the choice of printing an unload report, depending upon your setup options. Respond as you like to continue. The three ways of initiating an unload are: • Select the Unload button on the Calibrator Manager screen. • Select the Load button on the Calibrator Manager screen. • Select the Test...
Testing As-Found and As-Left Tests 5 As-Found and As-Left Tests An As-Found test result indicates the operating status of a device the first time you test it. Immediately subsequent tests of the device are then recorded as As-Left tests (unless the definition of the test is altered between tests, in which case a different As-Found result will be saved). Thus, it is possible to have multiple AsFound and As-Left Test Results for a single device.
DPC/TRACK Users Manual Note A “Manual Event” record may be appropriate for very simple tests, such as for inspection requirements. Troubleshooting This section discusses the most prevalent causes of problems you might encounter when attempting to use the calibrator in conjunction with DPC/TRACK. If you are experiencing problems related to calibrator communications, please read this section in its entirety before calling Fluke for assistance.
Testing Troubleshooting 5 There are many different error messages that could appear for a variety of reasons when attempting to load a Tag IDs to the calibrator. The majority of these messages are self-explanatory (although they may require a little investigation on your part). Calibrator Diagnostics There may be occasions where a little clean-up work might be necessary with respect to calibrator operations.
DPC/TRACK Users Manual 5-18
Chapter 6 Creating & Deleting Contents Introduction ............................................................................................... Creating Records ....................................................................................... Primary Fields....................................................................................... Creating Tag ID Records ...................................................................... Creating Test Results Records ..............................
DPC/TRACK Users Manual 6-2
Creating & Deleting Introduction 6 Introduction This chapter provides the following sections: • Creating Records • Deleting Records • Rebuilding & Deleting Sample Records Creating Records Up to this point within the manual, we’ve covered how to search through your database to find records, how to use graphs and reports towards interpreting your data, and how to use DPC/TRACK with a calibrator towards generating test results.
DPC/TRACK Users Manual Example 6.1: Creating Tag ID Records In this example, we will use the Add... button on the Change screen to create three new Tag ID records.. 1. Via a Quick Search (see Example 2.1) or some other means, access the Instrument View screen. 2. Click on the Change... button. 3. On the subsequent screen, select the Add... button to access the Add Tag IDs screen.
Creating & Deleting Creating Records 6 14. In the same manner as described earlier, enter “Ex 6.1 Tag3” and “Ex 6.1 SN3” (excluding the quotes) into the Tag IDs to Add and Serial Numbers to Add arrays, respectively. 15 Select the Create button, select OK on the subsequent screen, then select the Done button. On the subsequent screen, once again, select the Done button. The three records we just specified are appended to the record(s) currently displayed on the Instrument View screen.
DPC/TRACK Users Manual Creating Test Results Records Test Results records may be added via a calibrator unload or via a manual test entry. These two methods are discussed at length in Chapter 5, “Testing.” We also recommend that you work through Example 2.4 and Example 2.5. You’ll also find helpful calibrator-specific information in Appendix B at the back of this manual. There are a few nuances associated with the creation of Test Results that are worth mentioning here.
Creating & Deleting Creating Records 6 During Manual Testing Before saving the Test Results record, select the Equipment tab to enter your Test Equipment information. Select the Select... button and use the qualified suggestion lists to choose the desired Test Equipment, then choose Add to add the equipment to your array.) You may create new Test Equipment records on the spot via the New... button on this screen. See Example 2.5.
DPC/TRACK Users Manual To create a Procedure record: 1. Access the Instrument View page for any Tag ID record. 2. Select the Test Procedure tab to display the Test Procedure page. 3. Click on the Procedure... button. Enter search criteria on the subsequent Quick Search screen and select the Search button. The Procedure Selection screen appears, displaying all records matching your search criteria. 4. Select the New... button. The Add Procedure screen appears. 5.
Creating & Deleting Creating Records 6 Example 6.2: Creating a Procedure Record In this example, we will create a Procedure record by employing the New... button on the Procedure Selection screen. Specifically, we will create a new Procedure record that will provide test procedure information for a customized “3 up/down” test strategy. After working through this example, you may want to have the Admin rebuild the sample records to ensure that other personnel have access to the correct sample records. 1.
DPC/TRACK Users Manual Now let’s add our setup message. 12. Click inside the Setup Messages field box. Three buttons (+, -, and Edit) appear at the bottom of the field. 13. Select the Edit button. The Setup Messages screen appears. 14. Enter a simple setup message. 15. Select the OK button to return to the Add Procedure screen. 16. Add a wrapup message by performing the same steps as just described for the setup message. Our Procedure record is now ready to add to the Procedure database. 17.
Creating & Deleting Deleting Records 6 Deleting Records DPC/TRACK allows the deletion of records from your database to help you keep up-to-date with changes in your plant. If you’re not absolutely positive that a record should be deleted, don’t delete it. Record deletion is a nonrecoverable process. Also keep in mind that what seems to be unneeded today, may in fact be required at a later date for audit purposes.
DPC/TRACK Users Manual Deleting Test Results Records The deletion of Test Results is not allowed. Instead, you may “exclude” a Test Results record, thus removing it from your graphs and reports. Excluding Test Results For the purposes of quality assurance and data integrity, the deletion of Test Results records is not allowed within DPC/TRACK. The only Test Results records that may be deleted are the sample records that came with your program.
Creating & Deleting Deleting Records 6 Deleting Test Equipment Records With your ability to edit Test Equipment data, you probably won’t have too many occasions where you actually need to delete a Test Equipment record. Nonetheless, DPC/TRACK allows you to do so. Example 6.4: Deleting a Test Equipment Record In this example, we will walk through the procedure of deleting the “Fluke” sample Test Equipment record.
DPC/TRACK Users Manual Deleting Procedure Records There is generally no need to delete Procedure records from the database since Procedure records may be edited and renamed as necessary. With this in mind, a mechanism for deleting Procedure records does not exist within the DPC/TRACK product. Rebuilding & Deleting Sample Records DPC/TRACK includes a handful of sample records to help you learn the program.
Chapter 7 Changing Data Contents Introduction ............................................................................................... Overview ................................................................................................... Data in the Tag ID Database ..................................................................... Primary Tag ID Database Field ............................................................ Other Tag ID Database Fields..........................................
DPC/TRACK Users Manual 7-2
Changing Data Introduction 7 Introduction This chapter contains the following sections: • Overview • Data in the Tag ID Database • Data in the Test Results Database • Data in the Test Equipment Database • Data in the Procedure Database • Field Types • Field Status Messages Overview There are a number of issues surrounding the editing of data. For organizational purposes, we have broken down these issues into their respective databases.
DPC/TRACK Users Manual Data in the Tag ID Database Primary Tag ID Database Field The primary field in the Tag ID database is Tag ID. The Tag ID field is also used to manage relationships across the different databases. A given Tag ID record may be associated with many records in the Test Results database. Because of the above considerations, DPC/TRACK disallows the direct editing of data within the Tag ID and Serial Number fields at every level.
Changing Data Data in the Tag ID Database 7 Other Tag ID Database Fields Action(s) taken When this checkbox is selected, during the test, the system will prompt the tester to provide additional “human factor” information as to what actions were taken to resolve a given problem. This checkbox would most likely be used in conjunction with the Problem(s) checkbox, although you may select none, any, or all of the checkboxes in this area of the Setup Cal. page.
DPC/TRACK Users Manual Interval Value and Interval Units These fields work in conjunction with the Test Date of the most recent “Passed” Test Results record corresponding to the Tag ID record so that the Due Date value is properly updated. The Due Date field will not be updated unless both of these fields are specified. The Key User or Admin User ID may edit these fields. Instrument Type The choices available within this Pick field are dependent upon the current selection within the Function field.
Changing Data Data in the Tag ID Database 7 Test Type This Pick field contains the choices that dictate which calibrator and type of test is to be used. (See the Test Procedure page.) In particular, the fields that appear on the Setup Cal. page are controlled by the Test Type field. Within the Setup Cal. page there are certain cases where additional fields may appear or disappear based on the value of a Pick field. The Key User or Admin User ID may edit this field.
DPC/TRACK Users Manual Data in the Test Results Database For data integrity purposes, DPC/TRACK disallows the editing of Test Results information. The one allowable exception to this is the Comments field, which you may need to edit to correct typographical errors, or to note some post-test information that you had forgotten to enter during the unload process.
Changing Data Reconciliation of “Orphan” Test Results 7 Reconciliation of “Orphan” Test Results The calibrator allows you to perform a test and save results without first having performed a download from DPC/TRACK. When unloaded back to DPC/TRACK, it is possible for such Test Results to not have an associated Tag ID record, in which case they’re referred to as orphans. (Orphan Test Results may be accessed by performing a search via the Results button on the Main Menu.
DPC/TRACK Users Manual Last Cert. Date The value within this Date field reflects the most recent certification date for the Test Equipment. You are not allowed to edit this field directly. You may initialize the value of this field only upon creating the Test Equipment record; either during the unload process, or via the New... button. When the equipment is recertified (via the Recertify... button), the value within the Last Cert. Date field will be updated. Cert. Interval The Cert.
Changing Data Data in the Test Equipment Database 7 Check Due Date The value within this Date field is determined by adding the Check Interval to the Last Check Date. This field is automatically updated when Test Equipment is rechecked, or the Check Interval is changed. You are not allowed to directly edit the Check Due Date field. Cal. Status # This field is automatically incremented to reflect the number of times a calibration sequence was performed on any of the functions of the calibrator. Example 7.
DPC/TRACK Users Manual Data in the Procedure Database The concept of changing data within the Procedure database may be broken down into two categories: renaming Procedures and editing Procedures. The following subsections discuss these two methods of changing data within the Procedure database. Renaming Procedures To rename a Procedure is to change the value within the Procedure Name field.
Changing Data Data in the Procedure Database 7 Example 7.3: Renaming a Procedure In this example, we will rename the Procedure record (MYPROCEDURE1) we created in Example 6.2. 1. Access the Instrument View page for any Tag ID record. 2. Select the Test Procedure tab to display the Test Procedure page. 3. Click on the Procedure... button. Enter search criteria on the subsequent Quick Search screen and select the Search button.
DPC/TRACK Users Manual Editing Procedures Exactly what it means to edit a Procedure may be interpreted at least three different ways: • Changing a procedure assigned to a Tag ID. • Editing the characteristics of a Procedure as it is applied to a specific Tag ID. (This will be referred to as a local edit.) • Editing the characteristics of a Procedure as it is applied to all Tag IDs. (This will be referred to as a global edit.
Changing Data Data in the Procedure Database 7 Example 7.4: Editing a Procedure (Local) In this example, we will change the characteristics of the Procedure employed within the test setup information of the SAMPLETAG6 Tag ID record. (This example assumes you have worked through Example 2.4 and that you have associated the SAMPLEPROC1 with the SAMPLETAG6 Tag ID record. If you have yet done so, see Example 2.4 and select the SAMPLEPROC1 to be associated with the SAMPLETAG6 Tag ID record.
DPC/TRACK Users Manual Example 7.5: Editing a Procedure (Global) In this example, we will change the Procedure we created in Example 6.2 (MYPROCEDURE1). The change will be reflected in all Tag IDs that employ that Procedure. You need to be logged in as the Key User or Admin User ID to work through this example. 1. Perform a Quick Search to access the Instrument View screen for any Tag ID record. 2. Select the Test Procedure tab within the Instrument View screen. 3. Select the Procedure... button. 4.
Changing Data Data in the Procedure Database 7 Procedure Type This Pick field appears on the Test Procedure page and contains two choices, “Custom” and “Standard”. When a Procedure is selected (via the Procedure... button), the parameters associated with that Procedure appear on the Test Procedure page and the Procedure Type value is set to “Standard”. In order to customize these parameters for the specific Tag ID, you must change the Procedure Type value to “Custom”.
DPC/TRACK Users Manual Field Types DPC/TRACK provides several different field types to help manage the different types of data associated with instrumentation. The different field types are: • Text • Number • Date • Pick • YesNo A field’s type defines the kind of information that is stored in that field, the appearance of the data, and how the data in the field may be edited.
Changing Data Field Types 7 After selecting a Text field, you may move the cursor within the field using the left and right arrow keys on the keyboard. When data is entered at a particular position within the field, all data to the right of that position shifts to the right as necessary; data is not overwritten. To overwrite data, drag over the desired characters before entering new data. The Home and End keys move the cursor to the beginning and end of the data, respectively.
DPC/TRACK Users Manual Notice that the “0” following the insertion point was simply shifted to the right two spaces since we entered two characters. Upon leaving the field, the display format reflects the new value and returns the % symbol to our view. Tolerance 2.003% So what happened to the “8” we entered? This question leads us to another important concept for Number fields—resolution.
Changing Data Field Types 7 Dates are entered using a Month/Day/Year numerical input (such as 12/31/95, or 12.31.95, or 12-31-95, etc.) regardless of the date’s display format, which might be totally different than the field’s editing format. (This default editing format may be changed via the DPCTRACK.INI file, see Appendix A, “The DPCTRACK.INI File.”) The date as of seven days from today may be entered by simply typing +7 in the field box.
DPC/TRACK Users Manual Arrays There are certain instances where it’s helpful for a particular field to contain multiple entries. For example, perhaps you wish to record the testpoints associated with a particular Tag ID. Depending upon the test to be performed, the actual number of testpoints may vary, making it inconvenient to use several nonarrayed Number fields. In this case, an arrayed Number field is appropriate.
Changing Data Field Types 7 Other “Arrays” Sometimes, reference is made to a collection of radio buttons as being an array of radio buttons. An example of this is the Interval Units field on the Instrument View page. In this context, the term “array” simply implies that there are several choices available. In fact, an array of radio buttons is a cosmetic variation of a Pick field. Only one radio button may be selected within the group, which is analogous to choosing a value from a drop-down list.
DPC/TRACK Users Manual Field Status Messages Most of the time, your fields will contain real data, which you may review, search for, edit, delete, etc. There are occasions, however, when a field may contain a system message. DPC/TRACK is unique amongst database programs in that it recognizes the difference between blank data (such as multiple Spacebar entries) and no data at all. The C:Clear value within a field indicates that there is no data whatsoever within that field.
Changing Data Field Types 7 Cut, Copy, Paste The standard Windows procedures for Cut, Copy and Paste are supported by DPC/TRACK. Because different field types are governed by different rules and have different limitations, you typically won’t be able to copy a value from, say, a Pick field to a Date field. Even so, there are still practical situations where these operations are convenient, such as perhaps copying multiple lines of data from a Text field to your favorite word processor.
DPC/TRACK Users Manual 7-26
Chapter 8 Importing & Exporting Contents Introduction ............................................................................................... Overview ................................................................................................... Exporting Test Results .............................................................................. Exporting Instrument Data ........................................................................ Exporting Procedure Data .........................
DPC/TRACK Users Manual 8-2
Importing & Exporting Introduction 8 Introduction This chapter provides the following sections: • Overview • Exporting Test Results • Exporting Instrument Data • Exporting Procedure Data • ASCII Files • Importing Instrument Data • Importing Procedure Data Overview Many programs store their data in unique or proprietary file formats. In order to communicate this data to other programs, some sort of import, export, or conversion utility is usually required.
DPC/TRACK Users Manual You also have the opportunity to exclude records from the exported file by selecting the Exclude button while viewing a particular record, as we’ll see in our first example. Example 8.1: Exporting Test Results In this example, we’ll export some of the Test Results records associated with SAMPLETAG2. 1. Select the Import/Export button on the Main Menu to access the Import/Export Selection screen. 2. Select the Export History... button to access the Quick Search screen. 3.
Importing & Exporting Exporting Instrument Data 8 Exporting Instrument Data When Tag ID records are exported, an INST_OUT.ASC file will be created (or appended) within the directory containing your database files. The INST_OUT.ASC file is an ASCII text file with the data organized in tab-delimited columns. The first row of this file contains the headers that identify the data listed within each column. Subsequent rows contain the exported Tag ID data.
DPC/TRACK Users Manual Example 8.2: Exporting Tag ID Records In this example, we’ll export those sample Tag ID records that are located in Area1. 1. Select the Import/Export button on the Main Menu to access the Import/Export Selection screen. 2. Select the Export Instrument... button to access the Quick Search screen. 3. Enter “Area1” (excluding the quotes) in the Area field. 4. Select the Search button. 5. Select the Proceed button. Respond to any subsequent dialog box as appropriate. An INST_OUT.
Importing & Exporting Exporting Procedure Data 8 Exporting Procedure Data Your Procedure data may be exported to an ASCII file using DPC/TRACK’s export tool. The process of exporting a Procedure is simple: • On the Main Menu, select the Import/Export button. The Import/Export Selection screen appears. • Select the Export Procedure... button. The Procedure Export screen appears, providing you the opportunity to search for the Procedures of your choice.
DPC/TRACK Users Manual Example 8.3: Exporting a Procedure In this example, we will export the sample Procedure record, SAMPLEPROC1, to the designated output file (PROC_OUT.ASC). 1. On the Main Menu, select the Import/Export button. The Import/Export Selection screen appears. 2. Select the Export Procedure button. The Procedure Export screen appears, providing you the opportunity to search for the Procedures of your choice. 3.
Importing & Exporting ASCII Files 8 ASCII Files ASCII files contain plain text only, free of any formatting codes that control the layout and appearance of text. Features such as bold, italics, underline, bullets, etc., do not exist within an ASCII file. Neither can you control the font size, font type, font color, paragraph format, or line spacing within an ASCII file. When you convert a formatted document to an ASCII file, all of these characteristics are stripped from the file leaving only the text.
DPC/TRACK Users Manual 4. Now enter the next row of Tag ID information: FT-1001, 67890, and Building B. Again, be sure to separate these entries with Tab keys, and end the row with an Enter. In order to eventually import this information, the next step would be to save this file as INST_IN.ASC within the directory containing your database files. Note that the ASCII file we created contains only three database fields and two Tag ID records.
Importing & Exporting Importing Tag ID Data 8 In order to be imported properly, the INST_IN.ASC ASCII file must meet the following criteria: • Data is arranged in columns and rows, similar to a spreadsheet. An entry in a given column and row corresponds to a specific field for a particular Tag ID record. The order of the columns does not matter. • The first row contains the headers that identify the data listed within each column.
DPC/TRACK Users Manual Example 8.5: Importing Instrument Data DPC/TRACK includes an INST_IN.ASC file to help you learn the ins and outs of importing. This file is located within the directory containing your database files. (The directory containing your database files is designated by the LccPath variable within your DPCTRACK.INI file.) Note If you do not have an INST_IN.ASC file, then you may either create one (see Example 8.4), or perform an export, then rename the INST_OUT.ASC file to be INST_IN.ASC.
Importing & Exporting Importing & Pick Fields 8 Base Output Units V, mV, mA, Ohms, Hz, C, F, PSI, mmHG, inH2O, ftH2O, mmH2O, Bar, kPa, g/cm2, inH2O60F Current Mode Source, Regulate Function Controller, Converter, Indicator, Other, Receiver, Sensor, Switch, Transmitter (Note that the selection made within this field determines the available choices within the Instrument Type field. See also Chapter 7, “Changing Data.
DPC/TRACK Users Manual Temperature Indicator, Temperature Sensor, Temperature Switch, Temperature Transmitter, Thermometer, Thermowell, Transmitter, Timer, Trip Amplifier, Turbine Flow Meter, U/F Converter, U/U Converter, Ultrasonic Sensor, Ultrasonic Transmitter, V/I Converter, Vibration Indicator, Vibration Sensor, Vibration Switch, Vortex Transmitter, W/I Converter, Wedge Flow Meter, Weight Controller, Weight Indicator, Weight Sensor, Weight Transmitter If the Function selection of “Controller” is made,
Importing & Exporting Importing & Pick Fields 8 If the Function selection of “Sensor” is made, then the available choices within the Instrument Type field are: Flow Element, Gamma Detector, Gamma Source, Level Sensor, Load Cell, Mass Flow Sensor, Moisture Sensor, Orifice Plate, pH Sensor, Pressure Sensor, Restriction Orifice, RTD Sensor, Speed Sensor, Static Probe, TC Sensor, Temperature Sensor, Ultrasonic Sensor, Vibration Sensor, Weight Sensor If the Function selection of “Switch” is made, then the avai
DPC/TRACK Users Manual RTD Wires 2, 3, 4 Sensor Type RTD, Thermocouple, Other Setpoint 1 Direction High, Low Setpoint 1 State Normally Open, Normally Closed Setpoint 2 Direction High, Low Setpoint 2 State Normally Open, Normally Closed Source Mode Automatic, User Entered TC Type Type B, Type C, Type E, Type J, Type K, Type R, Type S, Type T, Type N, Type L, Type U Test Type 702 Analog, 743 Analog, 743 Binary Waveform Sine Wave, Square Wave 8-16
Importing & Exporting Importing Procedure Data 8 Importing Procedure Data In order to import Procedure records, you must already have an ASCII file that contains your Procedure data (named PROC_IN.ASC); otherwise, you must create one. You may create the ASCII file in the same manner as you would an ASCII file containing Tag ID data, with the exception of field names (see Example 8.4 for an illustration). Your ASCII file may contain any or all of the following fields: Table 8-2.
DPC/TRACK Users Manual You may import Procedure records by following these steps: 8-18 • On the Main Menu, select the Import/Export button. The Import/Export Selection screen appears. • Select the Import Procedure... button. The system checks to ensure that there is a PROC_IN.ASC file located in the database directory. If there is no PROC_IN.ASC file present in the database directory, you will receive an error message.
Importing & Exporting Importing Procedure Data 8 Example 8.6: Importing a Procedure In this example, we will import a Procedure record by using the PROC_OUT.ASC file we created via an export in Example 8.3. 1. Using a text editor (such as the Windows Notepad application), open the PROC_OUT.ASC file. (Assuming you worked through the export in Example 8.3, the PROC_OUT.ASC file will be located in the directory containing your database files.
DPC/TRACK Users Manual 8-20
Chapter 9 System Maintenance Contents Introduction ............................................................................................... Overview ................................................................................................... Passwords .................................................................................................. Setup Options ............................................................................................ Database Maintenance..................
DPC/TRACK Users Manual 9-2
System Maintenance Introduction 9 Introduction Contained in this chapter are the following sections: • Overview • Passwords • Setup Options • Database Maintenance Note This chapter is primarily intended for those with Admin security rights only. Overview Be it by choice or decree, you have been given Admin security rights. You play an important role in the success of DPC/TRACK at your plant in that all password and database maintenance tasks are your responsibility.
DPC/TRACK Users Manual Passwords Passwords help protect the integrity of your system. Each of the defined User IDs within DPC/TRACK must have a password. You (as the Admin) have the ability to edit the User ID password. (This is particularly helpful when users forget their User ID password.) While on the topic of passwords, you probably should change the default password for the included Admin User ID. Otherwise, anyone who reads this manual will be able to log into DPC/TRACK with Admin security rights.
System Maintenance Setup Options 9 Setup Options Access the Setup Options screen by selecting the System Setup button on the Main Menu, then selecting the Setup Options... button. On the General page, you may define the format for Certification information. Select the Load tab to access the Load page.
DPC/TRACK Users Manual screen to insert the Tag ID values for previously “failed” tests into the Load List. (This checkbox only applies to Tag IDs unloaded from the calibrator.) Set marks for untested Tag IDs This checkbox is provided as a further means of managing the Mark for Load checkbox. Selecting the Set marks for untested Tag IDs checkbox automatically selects the Mark for Load checkbox for any unloaded “untested” Tag IDs.
System Maintenance Database Maintenance 9 Database Maintenance Let’s be honest. Computers and software aren’t bullet proof. Somewhere, somehow, somebody will find a way to “crash” a program—intentionally or not, no matter how robust or advanced the system claims to be. To not at least mention the possibility of having to fix things, somewhat implies that there is no chance of ever having to fix things. To not provide a few simple tools to help you fix things would be careless.
DPC/TRACK Users Manual Rebuilding Indexes There may be occasions where certain files have been corrupted, such as if a power failure were to occur while adding records. You may notice that after starting up DPC/TRACK again, a given search routine doesn’t find the records it found prior to the power failure. In such cases, you may be able to fix the problem yourself by simply rebuilding the index files. To rebuild your index files, do the following: 1. Select the System Setup button on the Main Menu. 2.
System Maintenance Database Maintenance 9 Note If you backed up your database files directly to a floppy disk, then you may have to first copy the .ZIP file to your hard drive (or network) in order to successfully restore the file. Note If you restore your database files from a backup you must rename the HLCSTAT.BAK file to HLCSTAT.CFG. Otherwise, you will not be able to get into the program.
DPC/TRACK Users Manual 9-10
Appendices Appendix A B C Title Page The DPCTRACK.INI File .................................................................... A-1 Fluke Calibrators................................................................................... B-1 List of Known Bugs ..............................................................................
DPC/TRACK Users Manual
Appendix A The DPCTRACK.INI File Introduction This appendix contains the following sections: • Overview • Variables Overview Many Windows-based applications employ an initialization file to determine the proper startup settings. For DPC/TRACK, startup settings are defined in the DPCTRACK.INI file located in the directory containing your Windows program files (typically, but not necessarily C:\WINDOWS). This appendix describes the different variables and statements that may appear within the DPCTRACK.
DPC/TRACK Users Manual Variables The variables that may appear in the DPCTRACK.INI file are: BackupPath This variable determines the default path and file name for backups of your database files. The initial default is C:\DPCDATA.ZIP. See Chapter 9, “System Maintenance,” for more information on backups. BufferPath This optional setting specifies the directory located on a RAM disk (such as C:\TEMP), which is used to speed up access to frequently used data.
The DPCTRACK.INI File Variables A DateEditFormat Date fields have a MM/DD/YYYY default editing format that is displayed when the focus is in the field. If specified, the setting of this variable will override the default editing format. This setting does not change how the date is displayed when the focus is not in the field. So, if you specified a DDMonth:YY format, then the date of October 26, 1995, would appear as 26October:95.
DPC/TRACK Users Manual NonRadix This variable determines which non-numeric characters will be ignored when numbers are input. Multiple non-numeric characters may be specified (within quotes) to be ignored. The default value is “,”. (For example, if you are accustomed to typing in place holders (such as the “,” within “1,000”), DPC/TRACK will not attempt to interpret the “,” as part of the input.) NumberFormat The specified format determines the editing format for Number fields.
Appendix B Fluke Calibrators Introduction This appendix is divided into the following sections: • Record Types • Connecting the Calibrator • Performing a Test on the Calibrator • Calibrator Diagnostics Record Types For a given Test Results record, the value within the Record Type field reflects the operation mode of the calibrator when the results were saved.
DPC/TRACK Users Manual While the aforementioned record types may share certain characteristics, they often differ in the data that needs to be stored. To accommodate these differences, DPC/TRACK displays only that data relative to the record type. So, when a Logged Data test is unloaded, DPC/TRACK creates a Test Results record that reflects the data pertinent to that type of test.
Fluke Calibrators Connecting the Calibrator B Binary A binary test determines the status of an on/off condition, such as a switch or an alarm. The 743 calibrator manual includes instructions for calibrating a limit switch. (This feature is not supported by the 702 calibrator.) See Chapter 5, "Testing," for more information. Manual See Chapter 5, “Testing,” for information on manual tests.
DPC/TRACK Users Manual Performing a Test on the Calibrator To aid in the discussion of performing our test, we have provided a diagram of the front of the Fluke 743 Documenting Calibrator (Figure B-2). You should refer to this diagram as necessary when instructed to push a particular button while performing the test. Soft Key 3 Soft Key 2 Soft Key 1 Soft Key 4 Power Key MEAS SOURCE V RTD mA V Hz V TC RTD 7 8 9 4 5 6 1 2 3 0 .
Fluke Calibrators Performing a Test on the Calibrator B Note This example employs the sample SAMPLETAG6 record that came with DPC/TRACK. Assuming no data has been changed for this record, the test should proceed as follows. Specific instructions on loading the calibrator may be found in Example 2.4. Also refer to Chapter 5, “Testing.” 1. If necessary, select the Power Key to turn on the calibrator. 2. Repeatedly select Softkey #4 until the word “Tasks” appears above Softkey #1. 3.
DPC/TRACK Users Manual V RTD mA mA V RTD SOURCE 30V MAX MEAS 300V MAX TC Jumper Wire ED004F.EPS Figure B-3. Test Setup 9. You can confirm that the jumper wires are properly attached if the “Source” and “Measure” values are nearly identical; they should both be exactly (or very nearly) 1 Volt. 10. To begin the automated test, select Softkey #2.
Fluke Calibrators Fluke Calibrator Diagnostics B Fluke Calibrator Diagnostics Note These instructions apply to both the 702 and the 743 calibrators. Before running diagnostics, be sure to attach your calibrator to the appropriate communications port and turn it on. (This port is specified in your DPCTRACK.INI file by the ComPort variable.) 1. Select the System Setup button. 2. Select the Calibrator Diag... button. 3.
DPC/TRACK Users Manual B-8
Appendix C List of Known Bugs Fluke Bug Number Bug Description Comments 8066 Test Equipment Report (TER) is incomplete. TER does not print all existing results. 7890 Incorrect Base Values when results are unloaded from the calibrator. 7894 Base Input/Output Values do not appear in test report. 7907 Failure to check for availability of disk space before installation begins. Fails to install when there is less than 20 MB of available space.
DPC/TRACK Users Manual C-2
