![Fluke 754 [168/176] Analog as found as left](/img/pdf.png)
Fluke 754 [168/176] Analog as found as left
![Fluke 754 [168/176] Analog as found as left](/views2/1436074/page168/bga8.png)
DPC/TRACK
Users Manual
B-2
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. Since an As-Found test contains
different data than a Logged Data test, DPC/TRACK presents As-Found data
using a different set of fields.
Analog (As-Found & As-Left)
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 As-
Found and As-Left Test Results for a single device. Typically, an As-Left test
reflects the operating status of a device after you’ve made any necessary
adjustments so that it will pass the test. (If multiple As-Left tests are performed,
only the last As-Left test will be saved and unloaded.) See Chapter 5, "Testing,"
for more information.
Logged Data
You can use the calibrator to simply take periodic measurements over some time
interval and save the measurements as logged data. Since this sort of operation
typically isn’t associated with any particular Tag ID, a set of unloaded logged data
will often be saved as a stand-alone Test Results record; that is, a Test Results
record with no associated Tag ID record.
Measure, Source, Measure Source, and Saved State
As-Found and As-Left test results are automatically saved at the end of each test
routine. You may also save data on the calibrator’s display while within the
Measure, Source, or Measure Source modes. If you do so, then a separate test
result will be saved reflecting that mode. These operation modes are discussed at
length in the documentation that accompanied your calibrator.
Min Max
You can use the calibrator to record and save the maximum and minimum values
associated with taking measurement readings. When this information is unloaded
to DPC/TRACK, the minimum and maximum values will be stored in separate
fields.
Содержание
- Dpc track 1
- Dpc track users manual 1
- Table of contents 3
- List of tables 7
- Dpc track 8
- List of figures 9
- Dpc track 10
- Chapter 1 11
- Overview 11
- Introduction 13
- Conventions 14
- Databases records fields and forms 14
- The fundamentals 14
- Certain terminology is used throughout dpc track to describe different elements of the program these common terms are informally defined below 16
- Dpc track 16
- Terminology 16
- Overview the fundamental 17
- In a nutshell 18
- Tag id breakdown 19
- Requirements 20
- Floppy disk installation instructions 21
- Installation 21
- Cd rom installation instructions 22
- Compuserve 24
- Pentium floating point correction 24
- Getting support 25
- How to contact fluke 25
- Chapter 2 27
- Dpc track essentials 27
- Introduction 29
- Logging in 29
- Starting the program 29
- Security 30
- The main menu 32
- Main menu buttons 33
- About the sample records 34
- Tutorial learning the basics 34
- Example 2 searching 35
- Searching for records 35
- Sorting records 35
- Example 2 generating a drift plot 36
- Example 2 sorting 36
- Interpreting data 36
- Printing reports 38
- Creating deleting records 39
- Creating records 39
- Example 2 creating a tag id record 39
- Example 2 creating a test results record using a calibrator 40
- Example 2 creating a test results record manually 42
- Deleting records 43
- Changing data 44
- Example 2 deleting a tag id record 44
- Example 2 editing data in fields 45
- Example 2 renaming a tag id 46
- With respect to tag ids and serial numbers 46
- Example 2 0 renaming a serial number 47
- About the interface 48
- Main menu 48
- Chapter 3 49
- Searching for records 49
- Introduction 51
- Quick search 51
- Example 3 searching for test results 52
- Example 3 searching for an instrument 53
- Example 3 searching for test equipment 54
- Searching for procedures 54
- Related concepts 56
- Wildcard searching 57
- Scalar fields 58
- Search operators field types 58
- Arrayed fields 60
- Data order 62
- Searching for records data orde 63
- Chapter 4 65
- Graphs reports 65
- Generating graphs 67
- Introduction 67
- Example 4 generating a graph 68
- Printing reports 69
- Calibration cert 70
- Instrument detail 70
- Last test done 70
- Pass fail by category 70
- Pass fail list 70
- Test detail 70
- Test equipment 70
- Example 4 reverse traceability 71
- Reverse traceability 71
- Scheduler 71
- Calibration sheets 72
- Example 4 pass fail by category 72
- Printing records 72
- Chapter 5 73
- Testing 73
- Introduction 75
- Scheduled testing 75
- Test scheduling 75
- Unscheduled testing 76
- Example 5 the test scheduler 77
- The test scheduler 77
- The mark for load concept 79
- The calibrator manager 80
- Example 5 calibrator manager test scheduler add to list 81
- Example 5 calibrator manager test scheduler mark for load 82
- Setup vs test procedure 83
- Testing with calibrators 85
- Unloading 85
- Loading 86
- Testers input 86
- As found and as left tests 87
- Manual testing 87
- Switch testing vs instrument testing 87
- Qualifier errors 88
- Troubleshooting 88
- Calibrator diagnostics 89
- 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 89
- There may be occasions where a little clean up work might be necessary with respect to calibrator operations instructions on how to perform diagnostics on the supported calibrators are provided within appendix b at the end of this manual 89
- Chapter 6 91
- Creating deleting 91
- Creating records 93
- Creating tag id records 93
- Introduction 93
- Primary fields 93
- Example 6 creating tag id records 94
- Creating test equipment records 96
- Creating test results records 96
- During an unload 96
- Creating procedure records 97
- During manual testing 97
- Within the test equipment database 97
- Example 6 creating a procedure record 99
- Deleting records 101
- Deleting tag id records 101
- Example 6 deleting a tag id record 101
- Deleting test results records 102
- Excluding test results 102
- Deleting test equipment records 103
- Example 6 deleting a test equipment record 103
- Deleting 104
- Deleting procedure records 104
- Rebuilding 104
- Rebuilding deleting sample records 104
- Changing data 105
- Chapter 7 105
- Introduction 107
- Overview 107
- Data in the tag id database 108
- Example 7 changing a tag id record 108
- Primary tag id database field 108
- Other tag id database fields 109
- Data in the test results database 112
- Data in the test equipment database 113
- Reconciliation of orphan test results 113
- Example 7 recertifying test equipment 115
- Data in the procedure database 116
- Renaming procedures 116
- Example 7 renaming a procedure 117
- Editing a procedure for a specific tag id 118
- Editing procedures 118
- Editing a procedure for all tag ids 119
- Example 7 editing a procedure local 119
- Example 7 editing a procedure global 120
- Other procedure fields 120
- Field types 122
- Arrays 126
- Other arrays 127
- Related nuances 127
- Field status messages 128
- Cut copy paste 129
- Chapter 8 131
- Importing exporting 131
- Exporting test results 133
- Introduction 133
- Overview 133
- Example 8 exporting test results 134
- Exporting instrument data 135
- Example 8 exporting tag id records 136
- Exporting procedure data 137
- Example 8 exporting a procedure 138
- Ascii files 139
- Example 8 creating an inst_in asc file 139
- Dpc track 140
- For a given tag id record there are 42 fields into which you may import data from an ascii file these fields are listed in table 8 1 140
- Importing tag id data 140
- 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 in actuality you may specify up to 42 fields for your tag id records the 42 headers you may use are listed in table 8 1 the inst_in asc file that came with dpc track already has all of these headers entered along with some sample data for one tag id record 140
- 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 140
- Example 8 importing instrument data 142
- Importing pick fields 142
- Importing procedure data 147
- Example 8 importing a procedure 149
- Chapter 9 151
- System maintenance 151
- Introduction 153
- Overview 153
- Passwords 154
- Setup options 155
- Database diagnostics 157
- Database maintenance 157
- Backing up your data 158
- Rebuilding indexes 158
- 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 159
- 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 159
- Appendices 161
- A the dpctrack ini file 163
- Appendix a 163
- Introduction 163
- Overview 163
- The dpctrack ini file 163
- Variables 164
- Appendix b 167
- B fluke calibrators 167
- Fluke calibrators 167
- Introduction 167
- Record types 167
- Analog as found as left 168
- Logged data 168
- Measure source measure source and saved state 168
- Min max 168
- Binary 169
- Connecting the calibrator 169
- Manual 169
- A sketch of the bottom portion of the calibrator where jumper wires will be attached to perform our test is shown in figure b 3 the documentation that accompanied your calibrator includes diagrams for other types of tests 170
- Dpc track 170
- Figure b 2 743 calibrator 170
- Meas source 170
- Performing a test on the calibrator 170
- Setup ma 170
- Source 170
- Tc rtd 170
- The test we will perform is of the measure source variety basically we are going to have the calibrator test a pair of wires 170
- 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 170
- Users manual 170
- Fluke calibrator diagnostics 173
- If communications are not properly established 173
- If communications are properly established 173
- Appendix c 175
- C list of known bugs 175
- List of known bugs 175
Похожие устройства
- Fluke 754 Pressure Calibration APPLICATIONS AND SOLUTIONS
- Fluke 754 Приложение к Руководству по эксплуатации
- Fluke 754 Начало работы
- Fluke 754 DPCTrack2 _ Руководство по эксплуатации
- Fluke 754 Руководство по калибровке
- Fluke 753 DPC TRACK _ Руководство по установке
- Fluke 753 Приложение к руководству по калибровке
- Fluke 753 Calibration and documentation for process manufacturing_ Costs, benefits and feasibility
- Fluke 753 DPCTrack2 _ Начало работы
- Fluke 753 Начало работы
- Fluke 753 Положение об энергозависимости памяти
- Fluke 753 Руководство по калибровке
- Fluke 753 750 Series Brochure
- Fluke 753 DPCTrack2 _ Руководство по эксплуатации
- Fluke 753 Pressure Calibration APPLICATIONS AND SOLUTIONS
- Fluke 726 Precision Multifunction Process Calibrator
- Fluke 726 Приложение к Руководству по эксплуатации
- Fluke 726 Паспорт безопасности
- Fluke 726 Руководство по калибровке
- Fluke 719 Паспорт безопасности
Скачать
Случайные обсуждения